Management point : The OLEDB error code was 0x80004005.

Question

Hello,

SMS_MP_CONTROL_MANAGER component is under Critical Status and below is the status message.

Management Point encountered an error when connecting to the database CM_CO1 on SQL Server london.contoso.com. The OLEDB error code was 0x80004005.

Possible cause: The computer running SQL Server is turned off, not connected to the network, or not functioning properly.

Solution: Verify that the SQL Server is turned on, connected to the network, and functioning properly.

Possible cause: Management point does not have sufficient access rights to the database.

Solution: Verify that management point computer account or the Management Point Database Connection Account is a member of Management Point Role (smsdbrole_MP) in the SQL Server database.

Possible cause: Network problems are preventing the management point from properly accessing the SQL Server.

Solution: Investigate and correct any problems with your network.

Possible cause: The management point having problems is at a secondary site, and SQL access account being used was recently reset by the parent site.

Solution: This can automatically repair itself after one hour, as long as the account in use is not locked out. Check that the account in use is not locked out. Instead of waiting an hour, you can stop and start the SMS_SITE_COMPONENT_MANAGER service to immediately apply the new configuration.

Possible cause: The SQL Server Service Principal Names (SPNs) are not registered correctly in Active Directory

Solution: Ensure SQL Server SPNs are correctly registered. Review Q829868.

I tested below and it works. mpcontrol.log have no errors.

http://london.contoso.com:8530/sms_mp/.sms_aut?mplist

http://london.contoso.com:8530/SMS_MP/.SMS_AUT?MPCERT

Installed Microsoft OLE DB Driver for SQL Server in the management point. But still MP is in Critical.

Please help what else could be done.

Answer 1

Hi,

We could test OLE DB connectivity to SQL Server by using a UDL file:

https://learn.microsoft.com/en-us/troubleshoot/sql/database-engine/connect/test-oledb-connectivity-use-udl-file

Answer 2

To troubleshoot the issue with the SMS_MP_CONTROL_MANAGER component being in a critical state, follow these steps:

1. Verify SQL Server Accessibility:
   • Ensure the SQL Server is online and accessible from the management point (MP). Use tools like ping or telnet to check connectivity.
   • Confirm that the SQL Server is running and that there are no network issues affecting connectivity.
2. Check Permissions:
   • Verify that the MP computer account or the Management Point Database Connection Account has the necessary permissions. It should be a member of the smsdbrole_MP role in the SQL Server database.
3. Test Database Connection:
   • Use SQL Server Management Studio (SSMS) from the MP server to connect to the SQL database and verify connectivity.
   • Ensure that the account used to connect to SQL Server is not locked or disabled.
4. Network Configuration:
   • Check for any network issues that might prevent the MP from accessing the SQL Server. This includes firewall settings, DNS resolution, and routing issues.
5. Review Logs:
   • Examine the mpcontrol.log for any additional errors or warnings that might provide more context.
   • Check other relevant logs such as mpmsi.log and mpfdm.log for further details.
6. Restart Services:
   • Restart the SMS_SITE_COMPONENT_MANAGER service to apply any new configurations immediately.
   • Consider restarting the SQL Server services as well.