Microsoft KB Archive/890740

= An SMS 2003 site server does not immediately receive the status of an advertisement when you send the advertisement to Advanced Client computers that are running SMS 2003 with SP1 =

Article ID: 890740

Article Last Modified on 10/27/2006

-

APPLIES TO


 * Microsoft Systems Management Server 2003 Service Pack 1

-





SYMPTOMS
When you send an advertisement to Advanced Client computers that are running Microsoft Systems Management Server (SMS) 2003 with Service Pack 1 (SP1), the SMS 2003 site server does not immediately receive the status of the advertisement. This problem occurs because the Advanced Client computers cannot connect to the management point.

When this problem occurs, the following event may be logged in the System log: Source: W3SVC

Type: Warning

Event ID: 1010

Description: A process serving application pool 'CCM Server Framework Pool' failed to respond to a ping. The process id was '3488'.

Additionally, entries that are similar to the following may be logged in the Httperr.log file:

2004-10-27 06:46:57 10.12.251.170 3972 10.1.181.25 80 HTTP/1.1 CCM_POST /ccm_system/request 503 1 QueueFull

2004-10-27 06:46:57 10.14.50.119 1767 10.1.181.25 80 HTTP/1.1 CCM_POST /ccm_system/request 503 1 QueueFull

2004-10-27 06:46:57 10.12.233.66 1105 10.1.181.25 80 HTTP/1.1 CCM_POST /ccm_system/request 503 1 QueueFull



HTTP ERROR: URL=http:///ccm_system/request, Port=80, Code=12030, Text=ERROR_WINHTTP_CONNECTION_ERROR

Request failed: 503 Service Unavailable.

This problem also occurs when you try to deploy a widespread software delivery. For example, this problem may occur when you run the Security Update Inventory tool. Or, this problem may occur when you run the Microsoft Office Inventory Tool for Updates.



CAUSE
This problem may occur because of a bottleneck on the management point. Although the status messages are temporarily rejected, the status messages are eventually processed. Because all the status messages arrive in an acceptable timeframe without loss, you can safely ignore the events and entries that are described in the &quot;Symptoms&quot; section.



RESOLUTION
To resolve this problem, improve the CPU performance and the disk performance of the management point server. We also recommend that you implement load-balanced management points on the sites that experience this problem. For more information about how to implement load balanced management points, click the following article numbers to view the articles in the Microsoft Knowledge Base:

240997 Configuring Network Load Balancing

303608 How to configure Network Load Balancing parameters in Windows 2000

303765 How to perform advanced Network Load Balancing procedures in Windows 2000

323437 How to configure Network Load Balancing parameters in Windows Server 2003

820752 How to configure Network Load Balancing to work with IPsec

Keywords: kberrmsg kbtshoot kbprb KB890740

-

[mailto:TECHNET@MICROSOFT.COM Send feedback to Microsoft]

© Microsoft Corporation. All rights reserved.