PENDING MECM 2111 Management Point breaks daily with IIS 500 errors

[steveo-sccm]

Before everyone starts posting the "here, try this..." links I will let you know I have had 3 MS cases and a couple months of Googling and still no solid solution to this error. The MS offshore tech support leaves a bit to be desired. I believe there is something fundamentally incorrect in my environment OR with MECM. I have gone so far as to totally abandon my old site last month and build an entirely new one from scratch taking none of the old data. I have several completely separate SCCM\MECM environments in which all but this one work flawlessly. I can uninstall the MP and reinstall it and the MP works for some amount of time and will give 200 responses to clients but after a while it just returns to giving 500 errors.

Environment is a single server for SQL and all roles and about 450 clients

Let me give a few answers to questions people will ask:
I use the SCCM computer account name across the board where I can
I extended the AD schema
MP server computer object from AD has rights to AD\System\System Management
The SRV record in DNS has the correct rights
The MP server name is in SQL as SysAdmin and has rights to the CM DB in particular and the SQL server as a whole. There are no errors in the SQL log as to any loginb failures except one, once in a while, from NT AUTHORITY\SYSTEM
The usual test URL's of http://-servername-/sms_mp/.sms_aut?mpcert and http://-servername-/sms_mp/.sms_aut?mplist get 500 errors but after a reinstall show correctly (for some time) then 500 errors again
Boundaries are set with IP address rages and those are in a few different Boundary groups which are assigned to the MP

The IIS errors all look like this:
2022-03-11 14:00:02 192.168.215.90 CCM_POST /ccm_system/request - 80 - 192.168.223.137 ccmhttp - 500 0 0 126 8h

MPControl.log errors are all like this:
Call to HttpSendRequestSync failed for port 80 with status code 500, text: Internal Server Error

Http test request failed, status code is 500, 'Internal Server Error'. SMS_MP_CONTROL_MANAGER 3/11/2022 8:56:01 AM 3096 (0x0C18)

Clients all show these errors
No reply message from Server. Server may be temporarily down or a transient network error.
Post to http://--servername--/ccm_system/request failed with 0x8000000a.

After removal and reinstall of MP the messages all look like this:

MPControl.log
Call to HttpSendRequestSync succeeded for port 80 with status code 200, text: OK
IIS Log
2022-03-11 16:06:58 192.168.215.90 CCM_POST /ccm_system/request - 80 - 192.168.215.218 ccmhttp - 200 0 0 320 12

So far, and I have been researching this for a few months at this point, none of the links from Google have provided the correct long term fix.

Anyone have any idea's? I'll send you a six pack for the answer

Thank you

 

[Prajwal Desai]

Before MP role reinstallation: Call to HttpSendRequestSync failed for port 80 with status code 500, text: Internal Server Error
After MP reinstallation - MPControl.log - Call to HttpSendRequestSync succeeded for port 80 with status code 200, text: OK
Have you kept an eye on the appearance of this internal server following the MP role reinstallation?
When the above error occurs what are the components that turn red in the monitoring?.
Are any firewall rules applied within the LAN and for the comms that happen between the MP and clients?

 

[mohamedgamalfazaa]

When I reinstalled the MP role, It back to work normally. but it is a daily break in the morning with no specific time.
SMS_MP_Controller_Manger is the component appears error on monitoring.

 

[Prajwal Desai]

When I reinstalled the MP role, It back to work normally. but it is a daily break in the morning with no specific time.
SMS_MP_Controller_Manger is the component appears error on monitoring.

And what does MS support say about this issue?

 

[Garth]

When I reinstalled the MP role, It back to work normally. but it is a daily break in the morning with no specific time.
SMS_MP_Controller_Manger is the component appears error on monitoring.

You will need to review the Logs and Event viewer for more details. You need to start by determining when you first get the error then look at log and event viewer to see what exactly happens at that time +/- 10 minutes.