SCMM software updates scan fails on DPM servers


This is a whole System center post :-). A colleague of mine (Stefano Sberveglieri) fought against a strange issue in software updates. The scan process kept failing on DPM servers with the following error message SyncUpdates failure, error = 0x8024400E, soap client error = 7, soap error code = 400, HTTP status code = 200. He got this error just on DPM servers, this is what he found:

  1. the issue was on 4 on 5 DPM servers patched by SCCM SP2 + WSUS SP2
  2. the issue was on IIS 6 and IIS 7 hosted WSUS Sites
  3. the issue was just on DPM servers on more than 250 servers pacthed
  4. the issue was reproducible only when the windows update agent was called by SCCM, a manual scan locally or on Windows Update was always successful

The evidence of the issue can be tracked via standard SCCM reports:

image

Stefano nailed down the problem using the agent logs (SCCM is rich in logs and troubleshooting is usually a snap reading these ones)

WUAHandler.log (%systemroot%\SysWOW64\ccm\logs)

Its a WSUS Update Source type ({21D7A168-B6DF-48CD-9156-D177AA118348}), adding it.             WUAHandler     5/3/2010 6:31:20 PM          7976 (0x1F28)

Existing WUA Managed server was already set (http://SCCMServer:8530), skipping Group Policy registration.                WUAHandler     5/3/2010 6:31:20 PM       7976 (0x1F28)

Added Update Source ({21D7A168-B6DF-48CD-9156-D177AA118348}) of content type: 2               WUAHandler     5/3/2010 6:31:20 PM          7976 (0x1F28)

Async searching of updates using WUAgent started.       WUAHandler     5/3/2010 6:31:20 PM       7976 (0x1F28)

Async searching completed.       WUAHandler     5/3/2010 6:31:43 PM       3788 (0x0ECC)

Received ‘SucceededWithErrors’ code from WUA during search. Check WindowsUpdate.log in Windows directory.                WUAHandler     5/3/2010 6:31:43 PM       7976 (0x1F28)

WU Agent reported the following 1 warning messages: WUAHandler     5/3/2010 6:31:43 PM       7976 (0x1F28)

HResult: 0x8024400e Context: uecWindowsDriver Msg: (null).   WUAHandler     5/3/2010 6:31:43 PM       7976 (0x1F28)

Successfully completed scan.     WUAHandler     5/3/2010 6:31:43 PM       7976 (0x1F28)

WindowsUpdate.log (%systemroot%)

2010-05-06          11:35:58:447       348        1254       PT             + ServiceId = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}, Server URL = http://SCCMServer:8530/ClientWebService/client.asmx

2010-05-06          11:36:03:666       348        1254       PT           WARNING: SyncUpdates failure, error = 0x8024400E, soap client error = 7, soap error code = 400, HTTP status code = 200

2010-05-06          11:36:03:667       348        1254       PT           WARNING: SOAP Fault: 0×000190

2010-05-06          11:36:03:667       348        1254       PT           WARNING:     faultstring:There was an exception running the extensions specified in the config file. —> Maximum request length exceeded.

2010-05-06          11:36:03:667       348        1254       PT           WARNING:     ErrorCode:(null)(0)

2010-05-06          11:36:03:667       348        1254       PT           WARNING:     Message:(null)

2010-05-06          11:36:03:667       348        1254       PT           WARNING:     Method:(null)

2010-05-06          11:36:03:667       348        1254       PT           WARNING:     ID:(null)

2010-05-06          11:36:03:667       348        1254       PT           WARNING: PTError: 0x8024400e

2010-05-06          11:36:03:667       348        1254       PT           WARNING: SyncUpdates_WithRecovery failed.: 0x8024400e

2010-05-06          11:36:03:667       348        1254       PT           WARNING: Sync of Drivers failed (Software succeeded): 0x8024400e

The first though was about the numerb of volumes, as many of you know DPM uses extensively dynamic volumes and this is a big difference between DPM and non DPM servers (btw this is one of the most important thing to watch out in a DPM implementation, if the number of volumes grows toward the 1,000 threshold you are sure to have tons of problems), but the working DPM Server (DPM1) was one of the highest in number of volumes:

Name

OS

SCCM Agent version

WUA Version

Volumi

DPM-0

Windows Server 2008 Standard Edition SP2 64-bit

4.00.6487.2700

7.4.7600.226

136

DPM1

Windows Server 2008 Standard Edition SP2 64-bit

4.00.6487.2811

7.4.7600.226

394

DPM2

Windows Server 2008 Standard Edition SP2 64-bit

4.00.6487.2811

7.2.6001.788

352

DPM3

Windows Server 2008 Standard Edition SP2 64-bit

4.00.6487.2700

7.4.7600.226

169

DPM4

Windows Server 2008 Standard Edition SP2 64-bit

4.00.6487.2700

7.4.7600.226

493

The error message server side (There was an exception running the extensions specified in the config file. —> Maximum request length exceeded.) and a search on support.microsoft.com drived us on the right way: we incremented the value of the input stream buffering (maxRequestLength)in the Web.Config for ClientWebService (C:\Program Files\Update Services\WebServices\clientwebservice).

After a few try and error steps Stefano set the value to 3000 KB (the default was 600) and now our DPM servers are correctly reporting the scan results to SCCM.

– Daniele

This posting is provided "AS IS" with no warranties, and confers no rights.

About these ads
  1. Leave a comment

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

Follow

Get every new post delivered to your Inbox.

Join 277 other followers

%d bloggers like this: