error on MP control
-
08-14-2007 10:39 AM
|
|
-
Abhishek Joshi



- Joined on 12-19-2006
- India
- Posts 273
- Points 3,590
|
HI Guys,
I am getting the error on one of my sec site
|
SMS Management Point encountered an error when connecting to its Database SMS_HOU on SQL Server CR1NTPSMS1. The OLEDB error code was 0x80004005. |
|
|
|
Possible cause: The SQL server site system is turned off, not connected to the network, or not functioning properly. |
|
Solution: Verify that the SQL server site system is turned on, connected to the network, and functioning properly. |
|
|
|
Possible cause: SMS Management Point does not have sufficient access rights to the SQL server site system. |
|
Solution: Verify that the SQL server is properly configured to allow Management Point access. If using a standard SQL security account, verify that the SQL Server is configured to allow standard SQL Security; or configure the Management Point to use an NT integrated security account, with appropriate access. If using integrated security, verify the account used by the MP to connect to the SQL server is a member of the SMS_SiteSystemToSQLConnection_<sitecode > group on the SQL server, that the account is not locked out, and that the account password is not expired. (In standard security, the default account is SMS_SQL_RX_<sitecode>.) |
|
|
|
Possible cause: Network problems are preventing SMS 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. |
|
SMS Management Point encountered an error when connecting to its Database SMS_HOU on SQL Server CR1NTPSMS1. The OLEDB error code was 0x80004005. |
|
|
|
Possible cause: The SQL server site system is turned off, not connected to the network, or not functioning properly. |
|
Solution: Verify that the SQL server site system is turned on, connected to the network, and functioning properly. |
|
|
|
Possible cause: SMS Management Point does not have sufficient access rights to the SQL server site system. |
|
Solution: Verify that the SQL server is properly configured to allow Management Point access. If using a standard SQL security account, verify that the SQL Server is configured to allow standard SQL Security; or configure the Management Point to use an NT integrated security account, with appropriate access. If using integrated security, verify the account used by the MP to connect to the SQL server is a member of the SMS_SiteSystemToSQLConnection_<sitecode > group on the SQL server, that the account is not locked out, and that the account password is not expired. (In standard security, the default account is SMS_SQL_RX_<sitecode>.) |
|
|
|
Possible cause: Network problems are preventing SMS 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. |
All pri and sec site are installed with SMS 2003 SP1 and SQL 2003 SP3 a
Any one has idea about this?
Thanks and Regards Abhishek Joshi | SMS 2003/SCCM2007 certified,ITIL Foundation http://blogcastrepository.com/blogs/abi/default.aspx
|
|
-
-
-
Abhishek Joshi



- Joined on 12-19-2006
- India
- Posts 273
- Points 3,590
|
Thanks for the reply. yes, I check the system through suggested steps and I noticed the same as u mention (Network issue)
Thanks and Regards Abhishek Joshi | SMS 2003/SCCM2007 certified,ITIL Foundation http://blogcastrepository.com/blogs/abi/default.aspx
|
|
Page 1 of 1 (3 items)
|
|