MP Error 5420 5415 5414
PaulMama
We have upgraded our SMS2003 servers from SP2 to SP3 following microsofts
instructions. ON the main server i am unable to push any software and get a
massive amount of Management Point errors. I have reinstalled the MP\IIS\BITS
and the errors have not been fixed.
Any ideas or has anyone had this before?
thanks in advance
Most recent errors are :
Severity Type Site code Date / Time System Component Message ID Description
Error Milestone S00 25/09/2009
18:16:26 STRSMS01 SMS_MP_CONTROL_MANAGER 5420 SMS Management Point
encountered an error when connecting to its Database SMS_S00 on SQL Server
STRSMS01. The OLEDB error code was 0x80040E14. 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.
Followed by 5415
Severity Type Site code Date / Time System Component Message ID Description
Warning Milestone S00 25/09/2009
18:16:30 STRSMS01 SMS_MP_CONTROL_MANAGER 5415 MP cannot load the hardware
inventory class mapping table when processing Hardware inventory. Possible
cause: MP cannot communicate with the SQL data base. Solution: Check the
network connection between MP and the machine hosting the SQL data base
(likely the PSS). Possible cause: The SQL data base not initialized
properly or corrupted. Solution: Check the data for consistency. Recreate
the hardware definition tables if necessary.
and 5414
Severity Type Site code Date / Time System Component Message ID Description
Error Milestone S00 25/09/2009
18:16:30 STRSMS01 SMS_MP_CONTROL_MANAGER 5414 MP could not complete a task
when processing Hinv. Check the logs for clues. Possible cause: Out of
disk space. Solution: Increase the disk space, remove unprocessable files.