Management Point encountered an error when connecting to the database %3 on SQL Server %2. The OLEDB error code was %4. %12 ...

%11Management Point encountered an error when connecting to the database %3 on SQL Server %2. The OLEDB error code was %4. %12

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 (msdbrole_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.%0