| Event Id | 1010 |
| Source | w3svc |
| 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 <Client errors from affected sites in CCMExec.exe> HTTP ERROR: URL=http://<MPServername>/ccm_system/request, Port=80, Code=12030, Text=ERROR_WINHTTP_CONNECTION_ERROR Request failed: 503 Service Unavailable. |
| Event Information | "According To Microsoft" 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 "Symptoms" 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. |
| Reference Links | 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 |
Catch threats immediately
We work side-by-side with you to rapidly detect cyberthreats
and thwart attacks before they cause damage.