June 6, 2017 at 10:05 am
In the last two weeks, using 2014, we have a backup of an SSAS warehouse that is failing. Failure notification:
Executed as user: <SQLServiceAccount>. Microsoft.AnalysisServices.Xmla.XmlaException: Server: The operation was cancelled because of locking conflicts. at Microsoft.AnalysisServices.Xmla.XmlaClient.CheckForSoapFault(XmlReader reader, XmlaResult xmlaResult, Boolean throwIfError) at Microsoft.AnalysisServices.Xmla.XmlaClient.SendMessage(Boolean endReceivalIfException, Boolean readSession, Boolean readNamespaceCompatibility) at Microsoft.AnalysisServices.Xmla.XmlaClient.SendMessageAndReturnResult(String& result, Boolean skipResult) at Microsoft.AnalysisServices.Xmla.XmlaClient.Execute(String command, String properties, String& result, Boolean skipResult, Boolean propertiesXmlIsComplete) at Microsoft.SqlServer.Management.Smo.Olap.SoapClient.ExecuteStatement(String stmt, StatementType stmtType, Boolean withResults, String properties, String parameters, Boolean restrictionListElement, String discoverType, String catalog) at Microsoft.SqlServer.Management.Smo.Olap.SoapClient.SendCommand(String command, Boolean withResults, String properties) at OlapEvent(SCH_STEP* pStep, SUBSYSTEM* pSubSystem, SUBSYSTEMPARAMS* pSubSystemParams, Boolean fQueryFlag). The step failed.
Everywhere I look I haven't seen a resolution to this issue (outside of restarting the service or rebooting the server). Has anyone created a script to kill active sessions prior to a backup (like we all do when doing a restore of a database) for SSAS?
Any assistance would be appreciated.
Job is running the script below:
</Backup>
June 6, 2017 at 10:40 am
is this what you are after?
however, wouldn't it be wiser to investigate which session is causing the issue, you may find a bigger issue at root cause?
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply