Your browser (Internet Explorer 6) is out of date. It has known security flaws and may not display all features of this and other websites. Learn how to update your browser.

HTTP 500 Error with Large Reports in SCCM 2007

Phil Schwan has a new post up talking about how to raise the ASP buffer limit to show “large” reports.

As an FYI, another solution to this issue is to use SQL Reporting Services as the 10k row limit and the ASP buffer issue don’t apply when using SRS.

Read the full post here.

If you have more than a couple thousand clients in your SCCM 2007 site and have ever tried to run a large report (like “Hardware 01A – Summary of computers in a specific collection” against the All Systems collection, for example), you’ve probably encountered this HTTP 500 error:


This problem and resolution are pretty well documented for Windows Server 2003 and IIS6, but in this particular case we’re running Windows Server 2008 SP2, so we’re using IIS7.  The underlying cause is the same (default ASP Buffering Limit is set too low to handle the size of the report) and the fix is the same (increase the limit), but the steps to fix are just a little different for IIS7



Configuration Manager MPCERT and MPLIST Returning HTTP Error 500–Internal Server Error

I recently had an issue with my hyper-v lab where my MP quit working.  It’s a test lab so I’m making changes all the time.  So no big surprise there. However, uninstalling the MP and even uninstalling/installing IIS didn’t resolve the issue.  I kept getting a failed attempt when running the MP Troubleshooter and when trying to browse to the web page to verify the MP.  Again, thanks to a colleague for pointing me in the right direction. 



You can use these links to test your MP:



What ended up resolving the issue was running the following command and then restarting IIS.

cscript.exe %SYSTEMDRIVE%\inetpub\adminscripts\adsutil.vbs SET W3SVC/AppPools/Enable32bitAppOnWin64 0

Be sure to add the scripting tools in order for this command to work.  I think it’s a good idea to add both the IIS 7 and the IIS 6 tools for your lab environment.



W3SVC Won’t Start Without WAS Error

Reinstalled IIS on a site server and couldn’t get my services to start.  Thanks to a co-worker for helping me get this resolved quickly, I’d still be trying to figure this out without his help!

My event log looked like this, showing Event ID’s 5005, 5188 over and over:


And I had a ton of these errors:


The description for Event ID 5005 from source Microsoft-Windows-WAS cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.

If the event originated on another computer, the display information had to be saved with the event.

The following information was included with the event:

The description for Event ID 5188 from source Microsoft-Windows-WAS cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.

If the event originated on another computer, the display information had to be saved with the event.

The following information was included with the event:

Resolving the Errors

Turned out that my “apppools” folder was missing from the Inetpub\Temp folder.  After I created that folder, I was able to start all the services successfully. 



Error “The WebDAV server extension is either not installed or not configured properly” in Configuration Manager 2007

In addition the the following article:

TechNet post here.

It looks like if you see this in your logs:

401 WebDav Authorization OSD MDT GetDirectoryListing

Then the webdav_schema.xml is also the culprit. Use the fix below to resolve it.  


The SMS Site Component Manager fails to install the SMS_MP_CONTROL_MANAGER component on a Windows Server 2008 based computer.  The error is as follows:

The WebDAV server extension is either not installed or not configured properly.
Solution: Make sure WebDAV is installed and enabled. Make sure there is an authoring rule that allow “All users” read access to “All content”. Make sure the WebDAV settings “Allow anonymous property queries” and “Allow property queries with infinite depth” are set to “true” and “Allow Custom Properties” is set to false.

If you go to the IIS management console, connect to the local server and open the “WebDAV Authoring Rules” option you will find everything enabled but it still doesn’t seem to recognize it.


This can occur if the settings for the WebDAV Authoring Rules become out of sync with the WebDAV_schema.xml file.


We need to go the location of the configuration file of Webdav which isC:\Windows\System32\inetsrv\config\schema\WebDAV_schema.xml. After opening this file you may notice that the settings in this file were different from the settings that were configured in the IIS Manager.  The settings were configured as:

<attribute name=”allowAnonymousPropfind” type=”bool” defaultValue=”false” /> 
<attribute name=”allowInfinitePropfindDepth” type=”bool” defaultValue=”false” /> 
<attribute name=”allowCustomProperties” type=”bool” defaultValue=”true” />

However they should be:

<attribute name=”allowAnonymousPropfind” type=”bool” defaultValue=”true” /> 
<attribute name=”allowInfinitePropfindDepth” type=”bool” defaultValue=”true” /> 
<attribute name=”allowCustomProperties” type=”bool” defaultValue=”false” />

After correcting these settings (remember we have to take ownership of the file to be able to change it) and restarting the World Wide Web Publishing Service and the SMS_SITE_COMPONENT_MANAGER the Management Point should install correctly. You can check if the installation is successful in the log fileMPSetup.log in your SCCM\Logs directory. If successful the log should have entries similar to this:

<04-01-2010 13:15:58>         ======== Completed Installion of Pre Reqs for Role SMSMP ======== 
<04-01-2010 13:15:58> Installing the SMSMP 
<04-01-2010 13:15:58> Passed OS version check. 
<04-01-2010 13:15:58> IIS Service is installed. 
<04-01-2010 13:15:58> checking WebDAV configuraitons 
<04-01-2010 13:15:58>  WebDAV is configured 
<04-01-2010 13:15:58> No versions of SMSMP are installed.  Installing new SMSMP. 
<04-01-2010 13:15:58> Enabling MSI logging.  mp.msi will log to E:\SCCM\logs\mpMSI.log 
<04-01-2010 13:16:32> mp.msi exited with return code: 0 
<04-01-2010 13:16:32> Verifying CCM_CLIENT virtual directory. 
<04-01-2010 13:16:32> Website path is IIS://LocalHost/W3SVC/1. 
<04-01-2010 13:16:32> Connecting to IIS. 
<04-01-2010 13:16:32> CCM_CLIENT is currently E:\SCCM\Client. 
<04-01-2010 13:16:32> Installation was successful.

Note:  As you do any time you modify an XML file, please make a backup of WebDAV_schema.xml before making changes to it.

As an alternative resolution you can also run the following commands:

C:\Windows\system32\inetsrv\appcmd.exe set config “Default Web Site/” /section:system.webServer/webdav/authoring /enabled:true /commit:apphost

C:\Windows\system32\inetsrv\appcmd.exe set config “Default Web Site/” /section:system.webServer/webdav/authoringRules /allowNonMimeMapFiles:true /commit:apphost

C:\Windows\system32\inetsrv\appcmd.exe set config “Default Web Site/” /section:system.webServer/webdav/authoringRules /+[users=’*’,path=’*’,access=’Read’] /commit:apphost

C:\Windows\system32\inetsrv\appcmd.exe set config “Default Web Site/” /section:system.webServer/webdav/authoring /fileSystem.allowHiddenFiles:true /properties.allowAnonymousPropfind:true /properties.allowInfinitePropfindDepth:true /properties.allowCustomProperties:false /commit:apphost

Then just restart the World Wide Web Publishing Service and the SMS_SITE_COMPONENT_MANAGER and the Management Point should install correctly.


ConfigMgr and Server 2008 R2 – Trouble installing the MP, WebDav not correctly configured

This post is provided as-is, use at your own risk.

My latest lab is on Server 2008 R2 and I was having a weird issue with the MP not installing.  Even though I had configured WebDav correctly as per the TechNet article here, however my mpsetup.log was still giving me errors about WebDav not being correctly configured.  Upon opening up the webdav_schema.xml I could see that it wasn’t actually set correctly. 

I tried clearing the settings, uninstalling WebDav, restarting the server and reinstalling, reconfiguring, but even that didn’t work.

This post here pointed me in the right direction and credit is due where credit is due!

After manually modifying the webdav_schema.xml, then I was able to successfully install the MP site role. 


Setting up the Deployment Web Service

The information in this post is provided as-is, please use at your own risk and test appropriately.

Been meaning to create a post on this for quite some time.  I just want to cover the basic setup of the Deployment Web Service created by Maik Koster.  The latest download can be located here. (V7 as of this posting)  There is some documentation on the Codeplex site, and i urge you to review that as well.  CodePlex Documentation.  If you are going to be using the MDT functions of the web service, then you need to configure the Stored Procedures as well, and I recommend you read Maik’s blog post on this topic as i won’t be covering that in this post.

This will just be a quick-start guide for Server 2003 and IIS 6. So lets get started!

1) First download the files from the site linked above.

2) Extract out the web service files into a directory of your choosing, I still like to put items in Inetpub if it’s IIS related.  So \Inetpub\DeploymentWebService in my case.

3) Next we need to create a Virtual Directory in IIS.

Right-Click on Default Web-Site and select New – Virtual Directory




Name the Virtual Directory and click Next


Browse to the path of the files you extracted


Select Next


Make sure to check “Read” and “Run Scripts”, then click Next


Click Finish


4) Next we need to setup the Application Pool, I generally like to create a separate pool so you can recycle the pool without effecting anything else you might have running on that IIS server.

Right-click on Applications Pools and select New – Application Pool


Name the Web Pool appropriately, then click OK


Next we want to configure the identity of the web pool, here you can select the account that will run the Web Pool, most people will use a service account and specify those credentials here, this account will be the default account the web service is running under, so it will need rights to perform the web service functions you want to use:


5) Next we need to setup the Web Service to use the new Pool:

Go into the properties of the Virtual Directory you created and change the Application Pool to the web pool you previously created (MDTWebPool in screenshot):


You’ll also want to make sure under the ASP.NET tab that ASP.NET versions 2.0 is selected:


6) Next we need to configure the web service settings in the web.config (this step copied from Maik’s documentation)

On default, the webservice will use the configured application pool user for authentication. It requires only a couple Application Settings to be set:

  • RootServer – The SCCM Root Server
  • SLPServer – One SCCM Server with the SLP Role
  • RootSiteCode – The Root site code

For Access to the MDT Database you need to configure at least

  • MDTDBServer – The MDT Database server (with Instance if necessary)
  • MDTDBName – The MDT Database name
  • MDTDBIntegratedSecurity – Set to "True" if you want to use the application pool account for authentication. If set to "False" you need to supply the following two settings
  • MDTDBUser – Username to access the MDT Database
  • MDTDBPassword – Password to access the MDT Database

For Active Directory access, you can optionally configure the following Application Settings. This is only necessary, if the application pool user account does not have enough permissions to do execute the required functions, and/or if you need to access a different domain as the application pool User is member of:

  • ADDomain – Domain to query (use either "" or "DC=Domain,DC=COM" format)
  • ADUsername – Username for authentication
  • ADPassword – Password for authentication

7) Make sure to recycle the app pool for your web service after you’ve made changes to the web.config

8) You should now be able to use the Web Service. Open your browser and go to the following sites to verify they load correctly:

  • http://YourWebServer/YourWebserviceFolder/ad.asmx – For Active Directory related functions
  • http://YourWebServer/YourWebserviceFolder/mdt.asmx – For MDT related functions
  • http://YourWebServer/YourWebserviceFolder/sccm.asmx – for SCCM related functions.

Test a few functions and make sure it returns the data you expect.


There you go, you should now have a functioning web service to use with your deployments!