Call to HttpSendRequestSync failed for port 80 with status code 500, text: Internal Server Error……..again!

As ConfigMgr admins, we are used to this pesky message appearing in the mpcontrol.log and there are many blogs out there, including mine, that give you some tips on how to resolve the problem.

This time I had just removed the WSUS role from the ConfigMgr site server a few hours earlier and then noticed this error in the mpcontrol.log.

Call to HttpSendRequestSync failed for port 80 with status code 500, text: Internal Server Error

I ran the MPLIST command, http://<MPServername>/SMS_MP/.sms_aut?MPLIST, in a browser and received the following:

2017-06-28 00_35_04-IIS 8.5 Detailed Error - 500.19 - Internal Server Error.jpg

A quick Google on the error message, 0x8007007e, and I was led to the following MSDN blog on troubleshooting HTTP 500.19 Errors in IIS 7.

Error Code 0x8007007e is: ERROR_MOD_NOT_FOUND – The specified module could not be found.

So my applicationhost.config or web.config file referenced a module that no longer existed after the WSUS removal. The error in the screenshot mentions the  DynamicCompressionModule module.

I checked the applicationhost.config, located in C:\Windows\system32\inetsrv\config and, indeed, the module details were still in there:

<scheme name=”xpress” doStaticCompression=”false” doDynamicCompression=”true”
dll=”C:\Windows\system32\inetsrv\suscomp.dll” staticCompressionLevel=”10″
dynamicCompressionLevel=”0″ />

2017-06-28 00_52_32-applicationHost.config - Notepad.jpg

The fix is to run the following command:

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

I recommend that you back up the config file prior to executing the command.

Once the command was run, the MP sprang back into life.





  1. ERROR ( message:Malformed collection indexer; format is [@position,name=’value’,name2=’value2′,…]. The @position specifier is optional, and be ‘@start’, ‘@end’, or ‘@N’ where N is a numeric index into the collection. )

  2. I had this issue, and it was after I removed the WSUS role from the server. I ended up having to add the role again and it resolved the issue. I am looking more into this to see if the cause you show above is related.

  3. This saved my day! have had problems now for a couple of days and tryed all the fixes for the MP , reinstall, installing PREQs again ect… And this worked perfect thank you!

  4. Paul, thank you for this great solution! This is again an incredibly valuable post! You saved my day!!

  5. Worked for me too, thanks bro, this issue appears right when I removed the SUP role from my primary site. Do you have any clue why this happens? Maybe some av application blocking the update on IIS .config files or a bug in the SCCM?

Leave a Reply

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

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

Facebook photo

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

Connecting to %s