May 28 2020 05:43 AM - edited May 28 2020 05:46 AM
Hi,
After upgrading from version 1910 to 2002, I faced an issue in MP only on primary site server (No issues on other MP servers):
MP Control Manager detected User Service is not responding to HTTP requests. The http error is 404.
Message ID: 5491
I tried to verify MP by accessing the below URL:
http://sccmserver.domain.com/sms_mp/.sms_aut?mplist
I received the following error:
HTTP Error 404. The requested resource is not found
In addition I found the following on IIS bindings:
1- https with port 443
2- https with port 80
I think the problem with port 80 because the protocol type suppose to be http instead of https, I could delete it and create a new one with http and port 80 and stopped the error but after a while the settings is back to https and error occur again.
I'm not using SSL and no issue with other MP servers, last change I made was to upgrade from SCCM 1910 to 2002 after the update become a globally available for all customers.
So why this change occur on only one MP which is installed on the primary stand-alone site server?
Jun 03 2020 08:50 PM
I have exactly the same scenario but we haven't upgraded to 2002 yet. We wanted to use HTTPS instead HTTP on MP But PXE Points fails to provision OSD. So we had to rollback to HTTP, Now it's fine again with HTTP. Not sure if it's a known issue.
Jun 04 2020 11:42 AM - edited Jun 04 2020 11:43 AM
Jun 04 2020 11:42 AM - edited Jun 04 2020 11:43 AM
SolutionI didn't configure HTTPS, I just upgrade to Configuration Manager 2002, issue solved by configure enhance HTTP as described in the following article:
https://docs.microsoft.com/en-us/mem/configmgr/core/plan-design/hierarchy/enhanced-http
It suppose to work even without it but I'm okay now because the above improvement solved my issue and enhanced the clients communicate with site systems.
Jun 04 2020 11:42 AM - edited Jun 04 2020 11:43 AM
Jun 04 2020 11:42 AM - edited Jun 04 2020 11:43 AM
SolutionI didn't configure HTTPS, I just upgrade to Configuration Manager 2002, issue solved by configure enhance HTTP as described in the following article:
https://docs.microsoft.com/en-us/mem/configmgr/core/plan-design/hierarchy/enhanced-http
It suppose to work even without it but I'm okay now because the above improvement solved my issue and enhanced the clients communicate with site systems.