Failed to get information for MP: http://site. 80090006.

After upgrading a ConfigMgr site from 1511 to 1602, you may be unable to image any systems.  The error message shown on the screen will be “An error occurred while retrieving policy for this computer (0x80004005)”.   The Smsts.log file will have a message of “Failed to get information for MP: http://site. 80090006”.

The Smsts.log file may look something like this:

CryptVerifySignature (hHash, pSignature, dwSizeSignature, hKey, NULL, 0), HRESULT=80090006 (e:\nts_sccm_release\sms\framework\osdmessaging\libcrypt.cpp,642) TSMBootstrap 4/6/2016 12:32:10 PM 1176 (0x0498)

CryptVerifySignature failed, 80090006 TSMBootstrap 4/6/2016 12:32:10 PM 1176 (0x0498)

VerifySignedString (sAnsiCert.getBuffer(), m_sMPCertificateSignature.c_str(), szTrustedRootKey, 32780 ), HRESULT=80090006 (e:\nts_sccm_release\sms\framework\osdmessaging\libsmsmessaging.cpp,5387) TSMBootstrap 4/6/2016 12:32:10 PM 1176 (0x0498)

untrusted certificate:
{cert string} 
TSMBootstrap 4/6/2016 12:32:10 PM 1176 (0x0498)

MPKeyInformation.RequestMPKeyInformationForMedia(szTrustedRootKey), HRESULT=80090006 (e:\nts_sccm_release\sms\framework\osdmessaging\libsmsmessaging.cpp,9599) TSMBootstrap 4/6/2016 12:32:10 PM 1176 (0x0498)

Failed to get information for MP: http://site. 80090006. TSMBootstrap 4/6/2016 12:32:10 PM 1176 (0x0498)

There are 2 ways to fix this, through the ConfigMgr console or through SQL.

Solution 1:
-Browse to Site Status  , select any component running on the same site server and then select “Configuration manager ”

-Select component

-Right click on Hierarchy Manager and select query.
-The Hierarchy manager component thread should be running
-Right click and select stop

-Now right client and start the thread again.

Solution 2:
-Log into  SQL Server Management Studio hosting your ConfigMgr database.
-Open a new query.
-Execute this query: Exec spDrsSendSubscriptionInvalid{site code}','{site code}','configuration data'

2 responses to “Failed to get information for MP: http://site. 80090006.

  1. Thank you Sir, that did the trick perfectly!

  2. Thanks! Helped me having this issue after installing KB4339794

Leave a Reply

Your email address will not be published. Required fields are marked *