I’ve seen a few customers come across the following issue when installing the Application Catalog Web Service Point role.
When trying to access the CMApplicationCatalog website, you'll see the following:
Cannot connect to the application server.
The website cannot communicate with the server. This might be temporary problem. Try again later to see if the problem has been corrected.If the problem continues, contact your help desk.
You’ll see the following errors in system status: ====================================================================Component: SMS_AWEBSVC_CONTROL_MANAGER Message ID: 1016 Site Component Manager failed to install this component on this site system
Component: SMS_AWEBSVC_CONTROL_MANAGER Message ID: 4971Site Component Manager failed to install component SMS_AWEBSVC_CONTROL_MANAGER on server SiteServer.domain.com. The WCF is not activated. Solution: Make sure WCF is activated.====================================================================
SMSAWEBSVCSetup.log will show: ====================================================================WCF is not activatedInstallation Failed. Error Code: 123====================================================================
The error is due to a missing prerequisite.
They are documented here: Supported Configurations for Configuration Managerhttp://technet.microsoft.com/en-us/library/gg682077.aspx
On the above document, you’ll find that the Application Catalog web service point role requires the following:http://technet.microsoft.com/en-us/library/gg682077.aspx#BKMK_Win2k12SiteSystemPrereqs
*Note that there are slight differences for pre-2012 site servers as noted here.
Once you have the appropriate components installed in add roles and features, the role will install fine.
If you are installing the role on the same site server, you might need to reinstall the Application Catalog Website Point role after correcting your App Catalog Web Service Point.
Hope this helps!
Excellent Post. Also visit www.msnetframework.com
Great post. Works like a charm! Too bad the initial setup of SCCM or the prerequisites checker didn't give an error or warning or enabled it during setup. Your post is a big time-saver for me. Thanks!