The configuration file could not be loaded

Microsoft.SQLServer.2012.The_configuration_file_could_not_be_loaded_5_Rule (Rule)

Knowledge Base article:

Summary

The configuration file is stored in an XML-like format. Analysis Services uses this file to load server configuration parameters. This error occurs when Analysis Services is unable to load the configuration file during startup.

Causes

The configuration file is corrupted.

The configuration file is saved in an incorrect format.

The configuration file is opened or locked by another application.

Resolutions

On startup, Analysis Services will first try to use the configuration file. If this fails, default server property values are used. If the configuration file is absent, a new configuration file is created

The file is saved in an incorrect format

To recover the original server settings, restore the configuration file from backup

Close the application that has opened or locked the configuration file

Overrideable Parameters

Name

Description

Default Value

Enabled

Enables or disables the workflow.

Yes

Priority

Defines Alert Priority.

1

Severity

Defines Alert Severity.

2

Element properties:

TargetMicrosoft.SQLServer.2012.AnalysisServices
CategoryEventCollection
EnabledTrue
Event_ID21
Event Source$Target/Property[Type="SQL!Microsoft.SQLServer.AnalysisServices"]/ServiceName$
Alert GenerateTrue
Alert SeverityError
Alert PriorityNormal
RemotableTrue
Alert Message
The configuration file could not be loaded
{0}
Event LogApplication
CommentMom2012ID='{28FEFAD7-86AE-4F8A-BEC4-BA1FA6EAFE28}';MOM2012GroupID={467ECC75-C5DA-42BD-955C-A73BBB51AF74}

Member Modules:

ID Module Type TypeId RunAs 
_F6DA1507_12AF_11D3_AB21_00A0C98620CE_ DataSource Microsoft.Windows.EventProvider Microsoft.SQLServer.SQLDefaultAccount
GenerateAlert WriteAction System.Health.GenerateAlert Default

Source Code:

<Rule ID="Microsoft.SQLServer.2012.The_configuration_file_could_not_be_loaded_5_Rule" Target="SQL2012Core!Microsoft.SQLServer.2012.AnalysisServices" Enabled="true" ConfirmDelivery="true" Remotable="true" Comment="Mom2012ID='{28FEFAD7-86AE-4F8A-BEC4-BA1FA6EAFE28}';MOM2012GroupID={467ECC75-C5DA-42BD-955C-A73BBB51AF74}">
<Category>EventCollection</Category>
<DataSources>
<DataSource ID="_F6DA1507_12AF_11D3_AB21_00A0C98620CE_" Comment="{F6DA1507-12AF-11D3-AB21-00A0C98620CE}" TypeID="Windows!Microsoft.Windows.EventProvider" RunAs="SQL!Microsoft.SQLServer.SQLDefaultAccount">
<ComputerName>$Target/Host/Property[Type="Windows!Microsoft.Windows.Computer"]/NetworkName$</ComputerName>
<LogName>Application</LogName>
<Expression>
<And>
<Expression>
<SimpleExpression>
<ValueExpression>
<XPathQuery>EventDisplayNumber</XPathQuery>
</ValueExpression>
<Operator>Equal</Operator>
<ValueExpression>
<Value>21</Value>
</ValueExpression>
</SimpleExpression>
</Expression>
<Expression>
<SimpleExpression>
<ValueExpression>
<XPathQuery>PublisherName</XPathQuery>
</ValueExpression>
<Operator>Equal</Operator>
<ValueExpression>
<Value>$Target/Property[Type="SQL!Microsoft.SQLServer.AnalysisServices"]/ServiceName$</Value>
</ValueExpression>
</SimpleExpression>
</Expression>
</And>
</Expression>
</DataSource>
</DataSources>
<WriteActions>
<WriteAction ID="GenerateAlert" TypeID="SystemHealth!System.Health.GenerateAlert">
<Priority>1</Priority>
<Severity>2</Severity>
<AlertMessageId>$MPElement[Name="Microsoft.SQLServer.2012.The_configuration_file_could_not_be_loaded_5_Rule.AlertMessage"]$</AlertMessageId>
<AlertParameters>
<AlertParameter1>Event ID: $Data/EventDisplayNumber$. $Data/EventDescription$</AlertParameter1>
</AlertParameters>
<Suppression>
<SuppressionValue/>
</Suppression>
</WriteAction>
</WriteActions>
</Rule>