SCCM 2012 – Application Catalog HTTPS Error

Rate this post

Hi All,

recently i was at a customer site and that has a single primary site (with all roles on it). They have installed the Application Catalog but it was not working.

the SMS_AWEBSVC_CONTROL_MANAGER component was generating the error “Application Web Service Control Manager detected AWEBSVC is not responding to HTTP requests. The http status code and text is 500, Internal Server Error. Possible cause: Internet Information Services (IIS) isn’t configured to listen on the ports over which AWEBSVC is configured to communicate. Solution: Verify that the designated Web Site is configured to use the same ports which AWEBSVC is configured to use. Possible cause: The designated Web Site is disabled in IIS. Solution: Verify that the designated Web Site is enabled, and functioning properly. For more information, refer to Microsoft Knowledge Base.” every hour.

Looking the logs, the installation happen without any problem, however, the awebsctl.log was giving me the error:

SSL is enabled.
Call to HttpSendRequestSync failed for port 443 with status code 500, text: Internal Server Error
AWEBSVCs http check returned hr=0, bFailed=1
AWEBSVC’s previous status was 4 (0 = Online, 1 = Failed, 4 = Undefined)
Health check request failed, status code is 500, ‘Internal Server Error’.

accessing the https:///CMApplicationCatalogSvc/ApplicationOfferService.svc was giving me the error:
This collection already contains an address with scheme http. There can be at most one address per scheme in this collection.

Looking at the IIS Bindings i saw that there was multiple bindings there as the customer was using custom ports for the MP and the default ports for the Application Catalog.

Trying to use same ports as the MP was using did not fix the problem.

Searching the internet, i found a good blog post called Tips and Tricks for Deploying the Application Catalog in System Center 2012 Configuration Manager did not even had the answer (of course!!) but gave me a bit of an idea what could be the problem. the certificate.

I created a new certificate only for Application Catalog and assigned it for the port 443, re-installed the Web Service role and…nothing…problem was still there.

Because the Web service point is based on WCF, i decided to check the WCF log that can be found under c:\Microsoft\SMS\ServicePortalWebService.svclog and i noticed


wow…did not help and i was going to call Microsoft Support, but decided to do a bit more troubleshooting, i found that the WCF has a known limitation with multiple bindings for the same protocol (http or https) and this was the case. they had the http set to port 80 as well as another http set to a new port (the http mp) and for https only the new port (the mp https port)..

in this case, i cannot remove the bindings, but what can be done is to create a new website under IIS (I called it AppCatalog), set the folder to c:\inetpub\wwroot (yes, the same as the default as SCCM will create a virtual folder pointing to the correct place), set the port to 443 and selected the certificate and done.

re-installed the Web service point and used AppCatalog as the IIS Website.

Once i’ve done it, everything started working. added the Web site point and app catalog started working. 🙂

%d bloggers like this: