Cannot Connect to the Application Server

I was working on deploying applications to the users when I came across an error Cannot connect to the application server. This error was a surprise to me as there were no changes done on Configuration Manager server (as far as i knew). I had no idea why this error came up. When the user launched the software center, and clicked on find additional applications from the Application Catalog, there was an error. “Cannot connect to the application server. The website cannot communicate with the server. This might be a temporary problem. Try again later to see if the problem has been corrected. If this problem continues, contact your help desk”.

Fix Cannot Connect to the Application Server Error

Anyone looking to troubleshoot this issue should start looking at component status first. I checked Monitoring > System Status > Component Status to see if there were any errors on SMS_PORTALWEB_CONTROL_MANAGER and SMS_AWEBSVC_CONTROL_MANAGER. I found that SMS_AWEBSVC_CONTROL_MANAGER had errors. Upon checking status message details, the error description was

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.

Next, I checked the log file SMSAWEBSVCSetup.log and found no errors. In most of the cases status code 500 for the Application Catalog web service role is seen when there are problems with IIS or .NET configuration.

Cannot Connect to the Application Server

When I opened the Application Catalog I found the error cannot connect to the application server.

Cannot Connect to the Application Server

In most of the forums, it is suggested to remove the Application Catalog website point and Application Catalog web service point and reinstall them. For me the below solution fixed the issue and removing the roles was not required.

To fix this you need to enable or activate .NET 4.0. On a 64-bit computer that runs the .NET Framework version 4.0.30319, launch the command prompt as administrator and run the following command :

%windir%/Microsoft.NET/Framework64/v4.0.30319/aspnet_regiis.exe /i –enable

You could also change the path to the folder v4.0.30319 and run the command aspnet_regiis.exe /i –enable

Cannot Connect to the Application Server

After executing the above command, restart the IIS using iisreset command.

Cannot Connect to the Application Server
Now open the Application Catalog, there should be no errors.

Cannot Connect to the Application Server

If the above steps did not fix the issue and if something else worked, please post it in the comments section. If you face similar issues then you need not worry, you are just one step away from the Community Forums :).


  1. thanks

  2. Avatar photo Bruce Hethcote says:

    Look in your SMSAWEBSECSetup.log for lines like this towards the end:
     ======== Completed Installation of Pre Reqs for Role SMSAWEBSVC ========
     Installing the SMSAWEBSVC
     Passed OS version check.
     IIS Service is installed.
     Checking whether IIS ASP.NET component is installed
     IIS component ASP.NET is installed
     Checking whether WCF 40 is activated
     WCF 40 is not activated
     Installation Failed. Error Code: 123

    If you see that:
    Uninstall the catalog roles
    Add the TCP Activation feature under Features\.NET Framework 4.x Features\WCF Services\
    Reinstall the catalog roles

  3. Avatar photo De'Antae Davis says:

    This didn’t work for me. Any more suggestions?

    1. Along with the solution mentioned in the post, did you try uninstalling Application Catalog website point and Application Catalog web service point and reinstall them ?.

  4. Avatar photo rob mulder says:

    I got this error aftrenewing the SCCM Web ervice Certificate.

  5. Thanks so much, fixed my SCCM Catalogue after upgrading to 1806.

  6. Hi Prajwal, am still getting the error like Application Web Service Control manager detected AWEVSVC is not responding to to HTTP request http status code text is 404,

    can you please help me to resolve this issue am completely new to SCCM.

  7. still can not solve it tried the above solution and used dism also no avail
    tried to remove the roles and add them again but failed to remove with error
    cannot delete the site system because it is set as the default software catalog web site point in the default client settings
    checked the client setting not there and computer agent is blank
    any ideas

  8. After giving iisreset command it showing error “The service did not respond to the start or control request ina timely fashion ”
    Any solution please?

  9. Prajwal,

    Will this also work with later versions of the .Net framework, like say 4.5?

  10. First Prajwal, let me say thank you. Anytime I am doing a new deployment, setting up a roll or having an issue. I look at your posts first, for going on 5 year. Thank You.
    I was getting the same error in my application catalog however I had no errors in any of the logs or in the component status. I tried the .net fix and that didn’t work. I had recently created and imported cert, and enable https. So I know it had something to do with that change. After lots of searching and reading. I finally went to “Application Catalog website point properties” and deleted the NetBIOS name from the box. Refreshed the application catalog website and I was in. I still have no idea why this worked.

  11. Avatar photo Anthony Cruz says:

    Thank you for this fix, I have 2012 R2 OS and running 1706 and my MP’s were locked up with this error and weren’t serving. After applying your fix it got everything working OSD is back up and running. Great work!!

  12. Avatar photo Joakim Tomren says:

    Hi i just wanted to add a comment to the “Cannot Connect to the Application Server Error”. After i tried to set “specifiy an fqdn for this site system on the internet” on the site system role i got the error trying to open applciation catalog. I tried to remove the check but it did not resolve the problem. What it looks like is that when I checked the button the “site system identification” certificate was removed from the “trusted people” and Trusted root Certification authorities” on the application catalog server. By coping it back from SMS certificate store to trusted people and trusted root certificate authroitties store the application catalog started working again.

  13. Avatar photo steve lozano says:

    Thank you Kind Sir I was having the same issue and it would just stop working and Had to keep reinstalling the components then tried your solution BUT that Command line did not work for me on Server 2012 R2 I used “aspnet_regiis.exe -i” then restarted the IIS services
    Thanks again

  14. Hi, first of all big thanks to you because I basically followed your blog to get my standalone SCCM up and running.
    I have the same problem you’re presenting in the post, and I did the suggested solution, did not work.. is there another reason why this happens? It was working for a while — WITH THE HELP OF THIS POST. then it went back to what it was..

  15. Avatar photo Wayne Boyles says:

    I think you either got lucky or I’m just very unlucky (which is usually the case). Even in your screenshot it clearly states that the aspnet_regiis command isn’t supported / doesn’t work on the newer operating systems and you have to Turn Windows Features On or Off to enable / disable.

    In either case, I still haven’t been able to get this working 🙁 Role installed on W2K R2 tested on Windows 10 and Windows 7 all with the same error.

Comments are closed.