IIS Troubleshooting Tips for SCCM Admins|MP DP IIS Error Codes

0
IIS Troubleshooting Tips

Really quick one to segregate the IIS HTTP Error Codes which will be useful at time of troubleshooting SCCM/ConfigMgr/MEMCM Management Point and Distribution Point – server related communication issues. In this post you will more IIS Troubleshooting Tips.

IIS is integration part of SCCM/Configuration Manager server roles like MP, DP, and SUP. Most of the traditional SCCM client and server communication. Most modern communication is via fast channel and Message Processing Engine (MSP).

Related Posts

1xx Informational

Request received, continuing process.

This class of status code indicates a provisional response, consisting only of the Status-Line and optional headers, and is terminated by an empty line.

Since HTTP/1.0 did not define any 1xx status codes, servers must not send a 1xx response to an HTTP/1.0 client except under experimental conditions.

Altaro Office 365 Backup
Advertisement Altaro Office 365 Backup

2xx Success

This class of status codes indicates the action requested by the client was received, understood, accepted and processed successfully.

Call to HttpSendRequestSync succeeded for port 80 with status code 200, text: OK  $$<SMS_MP_CONTROL_MANAGER>
Http test request succeeded.~  $$<SMS_MP_CONTROL_MANAGER>
CCM_POST /ccm_system/request - 80 - 10.10.10.43 ccmhttp 200 0 0 295 
SCCM IIS Troubleshooting Tips
SCCM IIS Troubleshooting Tips

3xx Redirection

The client must take additional action to complete the request.

This class of status code indicates that further action needs to be taken by the user agent in order to fulfil the request. The action required may be carried out by the user agent without interaction with the user if and only if the method used in the second request is GET or HEAD.

A user agent should not automatically redirect a request more than five times, since such redirections usually indicate an infinate loop.

4xx Client Error

The 4xx class of status code is intended for cases in which the client seems to have erred. Except when responding to a HEAD request, the server should include an entity containing an explanation of the error situation, and whether it is a temporary or permanent condition.

These status codes are applicable to any request method. User agents should display any included entity to the user. These are typically the most common error codes encountered while online.

5xx Server Error

The server failed to fulfill an apparently valid request.

Response status codes beginning with the digit “5” indicate cases in which the server is aware that it has encountered an error or is otherwise incapable of performing the request.

Except when responding to a HEAD request, the server should include an entity containing an explanation of the error situation, and indicate whether it is a temporary or permanent condition. Likewise, user agents should display any included entity to the user. These response codes are applicable to any request method.

Call to HttpSendRequestSync failed for port 80 with status code 500, text: Internal Server Error
BITS_POST /CCM_Incoming/{BC2132F2-8FFF-445D-884B-958EAE0B5C24} - 80 -10.10.10.136 Microsoft+BITS/7.5 500 0 126 236

Resources – IIS Troubleshooting Tips

LEAVE A REPLY

Please enter your comment!
Please enter your name here

This site uses Akismet to reduce spam. Learn how your comment data is processed.