28.1 C
Ahmedabad
Friday, July 4, 2025

Management points stop responding to HTTP requests with error 500.19

Today sharing interesting issue and work around.  Your environment is working as expected and when report to next day office seeing client is not getting policy from management. 

Issue:  Management point error Call to HttpSendRequestSync failed for port 80 with status code 500.

While validate MPControl.log Found status code is 500

Now we have error let discussed more about. To find details on error Open IIS. Open Browser found getting error Management points stop responding to HTTP requests with error 500.19.

For details validate open iis logs which are located in c:\inetpub\logs most of the client responding with error 500.

Now let talk how to fix this issue :

System Center Configuration Manager management points stop responding to client requests.

When you use a web browser to connect to the management point list address (http://<ServerName>/sms_mp/.sms_aut?mplist), you receive the following error message: HTTP Error 500.19 – Internal Server Error

Cause:

if the WSUS server role was previously installed on the management point computer. When the WSUS server role was installed, it installed the XPress compression schema module (suscomp.dll) that loaded in every application pool in IIS. If the 32-bit version of suscomp.dll is loaded in an application pool that runs in 64-bit mode, you experience this issue

To fix follow below Steps:

Step 1:  Locate  %windir%\system32\inetsrv\config.

Note: Take backup of applicaitonHost.config

Step 2: Open the applicationHost.config file in Notepad.

Step 3: Look for an entry that resembles the following:
 
<scheme name=”xpress” doStaticCompression=”false” doDynamicCompression=”true” dll=”C:\Windows\system32\inetsrv\suscomp.dll” staticCompressionLevel=”10″ dynamicCompressionLevel=”0″ />

Step 4: Remove the XPress compression schema by running the following command from an elevated command prompt:

%windir%\system32\inetsrv\appcmd.exe set config -section:system.webServer/httpCompression /-[name=’xpress’]

Step 5: Verify that the compression schema is removed from the applicationHost.config file, and then save the file.

Step 6: Restart IIS OR Open command Prompt from an elevated command prompt Iisreset

Management point will start giving error code 200.

keep watching space @hiraniconfigmgr.com with many experts are here to share solutions.

Many Problem, One Place solutions.

Thanks & Regards,
Haresh Hirani
Email: [email protected]
Follow me: Twitter @hirravi1
linkedin: https://www.linkedin.com/in/hiraniconfigmgr

Author

  • Hi, I Haresh Hirani, I am the person behind this webpage. Welcome to my page, Thank you for visiting the website and my page! My website is all about Microsoft technologies. More about ConfigMgr and all other technologies which are interesting for me. However, larger percentage of my posts are related to SCCM. Normally, like to post the interesting issues which I came across in my day to day tech life. you will find only solutions which comes on my day to day life.

- Advertisement -spot_img

LEAVE A REPLY

Please enter your comment!
Please enter your name here

Latest posts