Forums on Intune, SCCM, and Windows 11

Welcome to the forums. Register a free account today to become a member! Once signed in, you'll be able to participate on this site by adding your topics and posts, as well as connect with other members through your own private inbox!

NEW Management Point encountered an error

  • Thread starter Thread starter JoshuaF1
  • Start date Start date
  • Replies Replies 0
  • Views Views 2K

JoshuaF1

New Member
Messages
1
Reaction score
0
Points
1
Hello everyone, new to posting on this forum but I have been following Prajwal for a while now. Anyways I have ran into an issue and honestly I feel my mastery over my Google Fu is lacking since I cannot find a solution. Would anyone be able to assist me in pointing me in a direction to my error below?
I did run the following command C:\>osql -S azcmspscc192 -d CM_101 -E and it returned a 1>
Thanks!!



Management Point encountered an error when connecting to the database CM_101 on SQL Server AZCMSPSCC192.*********.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.
 
Back
Top