Article ID: 967506 - Last Review: August 16, 2011 - Revision: 3.0

Client push fails when the System Center Configuration Manager 2007 Management Point is installed in Windows Server 2008

View products that this article applies to.

System TipThis article applies to a different operating system than the one you are using. Article content that may not be relevant to you is disabled.

SYMPTOMS

When the System Center Configuration Manager 2007 Management Point (MP) is installed on a Windows Server 2008 based computer, client push installations may fail with an error message that resembles the following:

Failed to correctly receive a WEBDAV HTTP request.

Failed to successfully complete HTTP request. (StatusCode at WinHttpQueryHeaders: 405)

Sending Fallback Status Point message, STATEID='301'.

State message with TopicType 800 and TopicId {44ECCF16-A66D-4FD0-B127-808F39B21380} has been sent to the FSP

Back to the top

CAUSE

This problem occurs because certain information is missing from the ApplicationHost.config file.

Back to the top

RESOLUTION

To resolve this problem, obtain the latest service pack for Microsoft System Center Configuration Manager 2007, available from this Microsoft web site:

http://www.microsoft.com/downloads/details.aspx?FamilyID=3318741a-c038-4ab1-852a-e9c13f8a8140 (http://www.microsoft.com/downloads/details.aspx?FamilyID=3318741a-c038-4ab1-852a-e9c13f8a8140)

For a list of issues resolved in this service pack, click on the following article number in the Microsoft Knowledgebase:

971348 (http://support.microsoft.com/kb/971348/ ) List of hotfixes and updates that are contained in System Center Configuration Manager 2007 Service Pack 2

You can also resolve this problem, by adding the following line to each<handlers xxxx> section of the %windir%\System32\inetsrv\config\applicationHost.config file between OPTIONSverbhandler and StaticFile:

<add name="WebDAV" path="*" verb="PROPFIND,PROPPATCH,MKCOL,PUT,COPY,DELETE,MOVE,LOCK,UNLOCK" modules="WebDAVModule" resourceType="Unspecified" requireAccess="None" />

Note There is a separate handlers section for each virtual directory.

You may also have to verify that the following lines exist in the same file:

Make sure that the following line exists in the <globalModules></globalModules> section:
<add name="WebDAVModule" image="C:\Windows\system32\inetsrv\webdav.dll" />

Make sure that the following line exists in the <modules></modules> section:
<add name="WebDAVModule" />

Here is an example of the corrected section for the SMSMP virtual Directory section:

<location path="Default Web Site/SMSSMP"> 
        <system.webServer> 
            <directoryBrowse enabled="false" showFlags="Date, Time, Size, Extension" /> 
            <handlers accessPolicy="Execute"> 
                <clear /> 
                <add name="ISAPI-dll" path="*.dll" verb="*" modules="IsapiModule" resourceType="File" requireAccess="Execute" allowPathInfo="true" /> 
                <add name="TraceHandler-Integrated" path="trace.axd" verb="GET,HEAD,POST,DEBUG" type="System.Web.Handlers.TraceHandler" preCondition="integratedMode" /> 
                <add name="WebAdminHandler-Integrated" path="WebAdmin.axd" verb="GET,DEBUG" type="System.Web.Handlers.WebAdminHandler" preCondition="integratedMode" /> 
                <add name="AssemblyResourceLoader-Integrated" path="WebResource.axd" verb="GET,DEBUG" type="System.Web.Handlers.AssemblyResourceLoader" preCondition="integratedMode" /> 
                <add name="PageHandlerFactory-Integrated" path="*.aspx" verb="GET,HEAD,POST,DEBUG" type="System.Web.UI.PageHandlerFactory" preCondition="integratedMode" /> 
                <add name="SimpleHandlerFactory-Integrated" path="*.ashx" verb="GET,HEAD,POST,DEBUG" type="System.Web.UI.SimpleHandlerFactory" preCondition="integratedMode" /> 
                <add name="WebServiceHandlerFactory-Integrated" path="*.asmx" verb="GET,HEAD,POST,DEBUG" type="System.Web.Services.Protocols.WebServiceHandlerFactory, System.Web.Services, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a" preCondition="integratedMode" /> 
                <add name="HttpRemotingHandlerFactory-rem-Integrated" path="*.rem" verb="GET,HEAD,POST,DEBUG" type="System.Runtime.Remoting.Channels.Http.HttpRemotingHandlerFactory, System.Runtime.Remoting, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089" preCondition="integratedMode" /> 
                <add name="HttpRemotingHandlerFactory-soap-Integrated" path="*.soap" verb="GET,HEAD,POST,DEBUG" type="System.Runtime.Remoting.Channels.Http.HttpRemotingHandlerFactory, System.Runtime.Remoting, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089" preCondition="integratedMode" /> 
                <add name="AboMapperCustom-51457" path="*.sms_smp" verb="CCM_POST" modules="IsapiModule" scriptProcessor="d:\sms_ccm\smpisapi.dll" responseBufferLimit="0" /> 
                <add name="TRACEVerbHandler" path="*" verb="TRACE" modules="ProtocolSupportModule" requireAccess="None" /> 
                <add name="OPTIONSVerbHandler" path="*" verb="OPTIONS" modules="ProtocolSupportModule" requireAccess="None" /> 
        <add name="WebDAV" path="*" verb="PROPFIND,PROPPATCH,MKCOL,PUT,COPY,DELETE,MOVE,LOCK,UNLOCK" modules="WebDAVModule" resourceType="Unspecified" requireAccess="None" /> 
                <add name="StaticFile" path="*" verb="*" modules="StaticFileModule,DefaultDocumentModule,DirectoryListingModule" resourceType="Either" requireAccess="Read" /> 
            </handlers> 
            <security>

For more information on how to Configure Windows Server 2008 for Site Systems see the following TechNet documentation:

http://technet.microsoft.com/en-us/library/cc431377.aspx (http://technet.microsoft.com/en-us/library/cc431377.aspx)

Back to the top

STATUS

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

Back to the top

DISCLAIMER

MICROSOFT AND/OR ITS RESPECTIVE SUPPLIERS MAKE NO REPRESENTATIONS ABOUT THE SUITABILITY OF THE INFORMATION CONTAINED IN THE DOCUMENTS AND RELATED GRAPHICS PUBLISHED ON THIS WEBSITE FOR ANY PURPOSE. THE DOCUMENTS AND RELATED GRAPHICS PUBLISHED ON THIS WEBSITE COULD INCLUDE TECHNICAL INACCURACIES OR TYPOGRAPHICAL ERRORS. CHANGES ARE PERIODICALLY ADDED TO THE INFORMATION HEREIN. MICROSOFT AND/OR ITS RESPECTIVE SUPPLIERS MAY MAKE IMPROVEMENTS AND/OR CHANGES IN THE PRODUCT(S) AND/OR THE PROGRAM(S) DESCRIBED HEREIN AT ANY TIME.

For more information on the terms of use, click on the link below:
http://support.microsoft.com/tou/ (http://support.microsoft.com/tou/)

Back to the top

Note This is a "FAST PUBLISH" article created directly from within the Microsoft support organization. The information contained herein is provided as-is in response to emerging issues. As a result of the speed in making it available, the materials may include typographical errors and may be revised at any time without notice. See Terms of Use (http://go.microsoft.com/fwlink/?LinkId=151500) for other considerations.

Back to the top