Tabular Model processing SQL Agent Job failure

[Anonymous]

I have set up a SQL Agent job to process my tabular model db, but I am getting the following non-descript error.

The tabular model processes fine processing it manually, but when I do it via SQL Agent job it fails almost instantly. We have done all the checks on credentials, logins, rights.

Any ideas/suggestions?

Executed as user: svcAccStmSQLAgentAcc. Microsoft.AnalysisServices.Xmla.XmlaException: OLE DB or ODBC error: Exception from HRESULT: 0x80040E4E.   at Microsoft.AnalysisServices.Xmla.XmlaClient.CheckForSoapFault(XmlReader reader, XmlaResult xmlaResult, Boolean throwIfError)   at Microsoft.AnalysisServices.Xmla.XmlaClient.CheckForError(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.ExecuteStatement(String statement, String properties, String& result, Boolean skipResult, Boolean propertiesXmlIsComplete)   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.

[Anonymous · Accepted solution]

I have found an issue in my SQL view where I combine multiple columns of which the nature is the same, but the columns are not the same data type eg varchar and int.

Casting them to be the same solved my problem

[v-shex-msft]

Hi @Anonymous,

AFAIK, XMLA write operations on datasets authored in Power BI Desktop and published to a Premium workspace require enhanced metadata, did you enabed this on your dataset?

Using enhanced dataset metadata in Power BI Desktop - Power BI | Microsoft Learn

Regards,

Xiaoxin Sheng