The Configuration Manager management point encountered an error when connecting to its database %3 on SQL Server %2. The OLEDB error code was %4. Configuration Manager status message 5420 was detected.
This condition could occur because:
The SQL Server site system is turned off, not connected to the network, or not functioning properly.
The Configuration Manager management point does not have sufficient access rights to the SQL Server site system.
Network problems are preventing the Configuration Manager management point from properly accessing the SQL Server site system.
The management point that is having problems is at a secondary site, and the SQL access account that is being used was recently reset by the parent site.
The SQL Server Service Principal Names (SPNs) are not registered correctly in Active Directory.
Verify that the SQL Server site system is turned on, connected to the network, and functioning properly.
Verify that the SQL Server is properly configured to allow management point access. If you are using a standard SQL security account, verify that the SQL Server site system is configured to allow standard SQL Security; or configure the management point to use a Windows NT integrated security account, with appropriate access. If you are using integrated security, verify that the account that is used by the management point to connect to the SQL Server site system is a member of the SMS_SiteSystemToSQLConnection_<sitecode > group on the SQL Server site system, 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>.)
Investigate and correct any problems with your network.
This condition can automatically repair itself after one hour if 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.
Ensure that the SQL Server SPNs are correctly registered. Review Q829868.
This alert is best handled by Configuration Manager administrators.
To investigate status messages:
1. In the Configuration Manager console, navigate to System Center Configuration Manager > Site Database > System Status, and then click Status Message Queries.
2. Right-click All Status Messages from a Specific System, and then select Show Messages.
3. In the All Status Messages from a Specific System dialog box, you can either specify the Machine Name and Time, or you can load existing machine names from the database, and then click OK. The status messages for the appropriate selected parameters are displayed.
For more assistance, see a list of additional support options in the support section of the Configuration Manager Web site at Support for Configuration Manager 2007.
| Target | Microsoft.SystemCenter.ConfigurationManager.2007.Microsoft_SMSv4_Site_Database_Servers_Installation |
| Category | EventCollection |
| Enabled | True |
| Alert Generate | False |
| Remotable | True |
| Comment | Mom2005ID='{682EA6A0-98B2-4BEB-8AB4-C27F1CCF0D02}';MOM2005ComputerGroupID={15348338-2E39-4B34-9DFF-4719AE7F1CCE} |
| ID | Module Type | TypeId | RunAs |
|---|---|---|---|
| _F320DA51_13BF_11D3_B2CD_00A0C92A28B4_ | DataSource | System.Mom.BackwardCompatibility.FilteredEvent.DataProvider | Default |
| GenerateAlert | WriteAction | System.Mom.BackwardCompatibility.AlertResponse | Default |
Home
<Rule ID="SMSv4_Status__Management_Point_encountered_a_database_connection_error_1_Rule" Target="Microsoft.SystemCenter.ConfigurationManager.2007.Microsoft_SMSv4_Site_Database_Servers_Installation" Enabled="true" ConfirmDelivery="false" Comment="Mom2005ID='{682EA6A0-98B2-4BEB-8AB4-C27F1CCF0D02}';MOM2005ComputerGroupID={15348338-2E39-4B34-9DFF-4719AE7F1CCE}">
<Category>EventCollection</Category>
<DataSources>
<DataSource ID="_F320DA51_13BF_11D3_B2CD_00A0C92A28B4_" Comment="{F320DA51-13BF-11D3-B2CD-00A0C92A28B4}" TypeID="MomBackwardCompatibility!System.Mom.BackwardCompatibility.FilteredEvent.DataProvider">
<Expression>
<And>
<Expression>
<SimpleExpression>
<ValueExpression>
<XPathQuery Type="Integer">EventDisplayNumber</XPathQuery>
</ValueExpression>
<Operator>Equal</Operator>
<ValueExpression>
<Value>5420</Value>
</ValueExpression>
</SimpleExpression>
</Expression>
<Expression>
<SimpleExpression>
<ValueExpression>
<XPathQuery Type="String">PublisherName</XPathQuery>
</ValueExpression>
<Operator>Equal</Operator>
<ValueExpression>
<Value>ConfigMgr 2007 Monitor SMS Status Messages</Value>
</ValueExpression>
</SimpleExpression>
</Expression>
<Expression>
<SimpleExpression>
<ValueExpression>
<XPathQuery Type="Integer">RepeatCount</XPathQuery>
</ValueExpression>
<Operator>Greater</Operator>
<ValueExpression>
<Value Type="Integer">5</Value>
</ValueExpression>
</SimpleExpression>
</Expression>
</And>
</Expression>
</DataSource>
</DataSources>
<WriteActions>
<WriteAction ID="GenerateAlert" TypeID="System.Mom.BackwardCompatibility.AlertResponse">
<GenerateAlert>true</GenerateAlert>
<Owner/>
<Description>
$Data/Params/Param[1]$
- ConfigMgr 2007 Status: Management Point encountered a database connection error.
$Data/EventDescription$
The status message contains message properties
Machine Name:
$Data/Params/Param[1]$
Module Name:
$Data/Params/Param[2]$
Component:
$Data/Params/Param[3]$
Message ID:
$Data/Params/Param[4]$
Win32 Error:
$Data/Params/Param[5]$
Top Level Site Code:
$Data/Params/Param[6]$
Database Record ID:
$Data/Params/Param[7]$
</Description>
<AlertLevel>40</AlertLevel>
<ResolutionState/>
<Source>
$Data/PublisherName$
</Source>
<Name>ConfigMgr 2007 Status: Management Point encountered a database connection error</Name>
<InvokerType>0</InvokerType>
</WriteAction>
</WriteActions>
</Rule>