Another Reason Why Browsing CompanyWeb May Fail with HTTP Error 503 on SBS 2011 Standard

Another Reason Why Browsing CompanyWeb May Fail with HTTP Error 503 on SBS 2011 Standard

  • Comments 5
  • Likes

[Today's post comes to us courtesy of Justin Crosby and Damian Leibaschoff from Commercial Technical Support]

We have found a second, somewhat less common, issue that can cause the error described previously in “HTTP Error 503 Accessing Company Web on SBS 2011 Standard”. You may experience this problem if you opted in to join the Customer Experience Improvement Program for Exchange 2010 and subsequently installed an Exchange update rollup using automatic updates (WSUS/MU).

In addition to the “HTTP Error 503. The service is unavailable” error in IE, you will also see the following event in the application log (note that some of the path names may be slightly different):

Log Name: Application
Source: Microsoft-Windows-User Profiles General
Event ID: 1509
Level: Warning
User: CONTOSO\spwebapp
Computer: SERVER.contoso.local

Windows cannot copy file C:\Users\Default\AppData\Local\Microsoft\Exchange Server\v14\Configuration14400_100.sqm to location C:\Users\TEMP.CONTOSO.005\AppData\Local\Microsoft\Exchange Server\v14\Configuration14400_100.sqm. This error may be caused by network problems or insufficient security rights.

DETAIL - Access is denied.

In the System log you will also see the following:

Log Name: System
Source: Microsoft-Windows-WAS
Event ID: 5022
Level: Warning
Computer: SERVER.contoso.local
The Windows Process Activation Service failed to create a worker process for the application pool 'SBS Sharepoint AppPool'. The data field contains the error number.

Event Xml:
<Data Name="AppPoolID">SBS Sharepoint AppPool</Data>

Note: The error code 2B010780 is 8007012B in Words.


To recover from this situation:

  1. Use explorer to open the following location C:\Users\Default\AppData\Local\Microsoft\Exchange Server\v14.
  2. For each file in this folder identified in the matching event (Configuration14400_100.sqm in our example), open its Properties.
  3. Select the Security Tab.
  4. Click Advanced.
  5. Click Continue.
  6. Check the “Include inheritable permissions from this object’s parent” checkbox.
  7. Repeatedly click Ok to close all the dialogs.
  8. From an administrative command prompt, run IISRESET /noforce
    Note: you may have to run this command several times until it concludes successfully.

More Information

By default, installations of Exchange 2010 in SBS 2011 standard are not configured to join the program, but this could have been manually changed from the Exchange Management Console or during a manual installation of Exchange.

In order to tell if you have this setting enabled, you can do the following:

  1. Launch an administrative Exchange Management Shell
  2. Run the following command: (Get-OrganizationConfig).customerfeedbackenabled
    If the result is True, then you are joined to the program.

For more information please check:

Your comment has been posted.   Close
Thank you, your comment requires moderation so it may take a while to appear.   Close
Leave a Comment
  • Thank you, this worked.

  • Thank you!!

  • Another reason that this situation can exist is that the administrator responsibly runs the Exchange BPA to ensure its health and consequently is pointed to opt into this customer feedback program.  After going around and around to get an answer on this a couple of weeks back, I am now incentivised to never opt into any such application auto Microsoft 'improvement' reporting.

  • No files in this map it work not app pools stops

  • spwebapp pssword was expired, must fill in in apppool