imageHi everyone, Arvind Kr. Rana here with another support tip for you regarding System Center 2012 Configuration Manager. When attempting to install the Application Catalog website on custom website, you may run into an issue where it fails with the following:

ERROR: Call to HttpSendRequestSync failed for port 80 with status code 404, text: Not Found
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 404, 'Not Found'.

Troubleshooting: 

When I saw this issue, I checked and found that the Application Catalog role was being installed on custom website rather than the default, and that it was using a custom IP address for the server that was configured in the NIC properties but using the default http port 80. In essence, we had two websites on same server using port 80.

Solution:

To resolve this we needed to configure the Application Catalog website point or Application Catalog web service point to use non-default ports. Here are the steps we followed: 

  • Create a new IIS website and specify the bindings (and PKI certificate if using HTTPS) for the non-default port numbers.
  • Verify that the new IIS website is operational. For example, on the computer that is running IIS, type http://localhost:<port> or https://localhost:<port> in the browser and confirm that you see the IIS welcome screen. Also check that the firewall is configured to allow communication via the specified ports.
  • Specify the new IIS website name and the non-default port number when you install the Application Catalog roles. The port numbers cannot be changed after installation so if you get to the point where you need to do this you must remove the Application Catalog roles and re-install them.

Note that Configuration Manager does not configure IIS for the non-default website or port number – you must configure these in IIS before you install the Application Catalog site system roles.

More Information:

This problem can also manifest itself in other ways, so please first make sure that you make the required changes to the website and the NIC card, ensuring that it all works properly before installing the Application Catalog website point or Application Catalog web service point role.

The TechNet article below has more information on this topic:

http://blogs.technet.com/b/configmgrteam/archive/2012/07/05/tips-and-tricks-for-deploying-the-application-catalog-in-system-center-2012-configuration-manager.aspx

Arvind Kumar Rana | Senior Engineer | System Center Team

Get the latest System Center news on Facebook and Twitter:

clip_image001 clip_image002

System Center All Up: http://blogs.technet.com/b/systemcenter/
System Center – Configuration Manager Support Team blog: http://blogs.technet.com/configurationmgr/
System Center – Data Protection Manager Team blog: http://blogs.technet.com/dpm/
System Center – Orchestrator Support Team blog: http://blogs.technet.com/b/orchestrator/
System Center – Operations Manager Team blog: http://blogs.technet.com/momteam/
System Center – Service Manager Team blog: http://blogs.technet.com/b/servicemanager
System Center – Virtual Machine Manager Team blog: http://blogs.technet.com/scvmm

Windows Intune: http://blogs.technet.com/b/windowsintune/
WSUS Support Team blog: http://blogs.technet.com/sus/
The AD RMS blog: http://blogs.technet.com/b/rmssupp/

App-V Team blog: http://blogs.technet.com/appv/
MED-V Team blog: http://blogs.technet.com/medv/
Server App-V Team blog: http://blogs.technet.com/b/serverappv

The Forefront Endpoint Protection blog : http://blogs.technet.com/b/clientsecurity/
The Forefront Identity Manager blog : http://blogs.msdn.com/b/ms-identity-support/
The Forefront TMG blog: http://blogs.technet.com/b/isablog/
The Forefront UAG blog: http://blogs.technet.com/b/edgeaccessblog/