DP sending status message in HTTPS with prot 80

Question

A wired error in smsdpmon.log:

Error sending status message to management point(s) 'https://MP.FQDN' (port 80) from remote DP. Verify management point(s). (code 0x80004005)

i have check the registry HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\SMS\DP, MPPort is set to 80. i manually change it to 443 but it smsdpmon keep using 80, and MPPort is reset to 80 after DP server reboot.

Where should I start to troubleshooting?

Answer 1

Rise a case to Microsoft and found the root cause.

when you found the error message like below, you need to check the certificate you import to your DP:

reply has no message header marker.
Failed to send status message (80004005)
Error sending status message to management point(s) 'https://xxxxxxxxxxxxx' (port 80) from remote DP. Verify management point(s). (code 0x80004005)
CSMSDPMonitoring::ReportStatusMessage failed; 0x80004005

normally retry to import certificate to your DP will solve the problem.

In my case it's more complicated.
All failure DPs are located on secondary site.
After renew the expired cert, import the new cert to DP, the new certificate information being added to secondary site Database, then replicate to primary site database.
primary site database cannot add the new certificate info to target table.

Microsoft support engineer provides a SQL query to fix the issue.
As we don't know which setting should be correct in different environment, suggest to call MS if you get the same issue.

Answer 2

is your DP configured to https? if so, you need to change the IIS edit bindings but not the registry. You should never touch the registry for any manual changes.

Regards,
Eswar
www.eskonr.com
If the response is helpful, please click "Accept Answer" and upvote it.

Answer 3

Hi,

Thanks for posting in TechNet.

After you manually fix this and start the site, please try the following actions:

1. Delete https:443 from default website bindings
2. Close IIS
3. Restart SMS_Executive service
4. Open default website bindings and see that https:443 has populated
5. Reboot the server

Similar thread for your reference:
SCCM Update 2002 Causes IIS Bindings to change and default Website to stop

Hope my answer could help you. Thanks for your time.

Best regards,
Simon
If the response is helpful, please click "Accept Answer" and upvote it.