Hi.  I got this error from a sql agent driven cube process yesterday and am wondering where the log of errors is created...

Executed as user: x\servername$. <return xmlns="urn:schemas-microsoft-com:xml-analysis"><results xmlns="<root">http://schemas.microsoft.com/analysisservices/2003/xmla-multipleresults"><root xmlns="urn:schemas-microsoft-com:xml-analysis:empty"><Messages xmlns="urn:schemas-microsoft-com:xml-analysis:exception"><Warning WarningCode="1092354050" Description="Server: Operation completed with 1042 problems logged." Source="Microsoft SQL Server 2008 R2 Analysis Services" HelpFile="" /></Messages></root></results></return>. 
The step failed.

if its a property I can see related to the server in ssms, which property as I see lots of stuff with the word log in the property name.

• Edited by db042190 Thursday, April 30, 2015 1:08 PM more

thx for trying Anuj but there are two problems. 

The original error I posted comes from job history so the query u posted wouldn't help in this situation and ...

the link u provided isn't clear as to which server property name to associate with the various files it discusses. 

I took a chance on msmdsrv.txt in the dir specified as server property "LogDir" and it didn't even have a reference to this problem.  

In the same dir I looked at sqldumper_errorlog and it didn't contain anything useful either. 

Finally I went poking around for a flat file or table named OlapQueryLog which is listed in the Value column next    to  property  "Log \QueryLog\QueryLogTableName" to but I couldn't find such an object.

• Edited by db042190 Thursday, April 30, 2015 3:25 PM spelling

thx Charlie.  why doesn't msmdsrv.log (actually mine was named .txt) contain anything about the error?  See post # 3 . 

I will look at windows event log as time permits.  But suspect the detail dim errors that I think occurred wont be in there. 

IMHO the link is circuitous, perhaps geared to a different audience.  With all due respect to u and Anuj, re processing in VS would give me the errors I seek much faster than getting what I need from that article.

• Edited by db042190 Friday, May 01, 2015 12:50 PM more
• Proposed as answer by Ed Price - MSFTMicrosoft employee, Owner Friday, May 01, 2015 9:04 PM
• Unproposed as answer by db042190 Monday, May 04, 2015 12:28 PM

Hi,

I had exactly the same issue and resolved it by changing the script to include ignore errors section (bolded text below).

<Batch xmlns="...//shorten for better visibility">
  <ErrorConfiguration xmlns:xsd="... //shorten for better visibility">
    <KeyNotFound>IgnoreError</KeyNotFound>
    <NullKeyNotAllowed>IgnoreError</NullKeyNotAllowed>
  </ErrorConfiguration>
  <Parallel>
    <Process xmlns:xsd="... //shorten for better visibility">
      <Object>
        <DatabaseID>Your Database Name</DatabaseID>
      </Object>
      <Type>ProcessFull</Type>
      <WriteBackTableCreation>UseExisting</WriteBackTableCreation>
    </Process>
  </Parallel>
</Batch>

Ignoring the errors is not really a solution. This is not entirely easy to find, but these errors are logged to where ever you configure them to go. If you have not setup a log file then I think they only get output to the trace.

You can configure a log file location by changing the batch settings and going into the dimensions key errors and configuring the log file path.

This will produce XMLA like the following and will send key errors to the specified file

<Batch xmlns="http://schemas.microsoft.com/analysisservices/2003/engine">
  <ErrorConfiguration xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:ddl2="http://schemas.microsoft.com/analysisservices/2003/engine/2" xmlns:ddl2_2="http://schemas.microsoft.com/analysisservices/2003/engine/2/2" xmlns:ddl100_100="http://schemas.microsoft.com/analysisservices/2008/engine/100/100" xmlns:ddl200="http://schemas.microsoft.com/analysisservices/2010/engine/200" xmlns:ddl200_200="http://schemas.microsoft.com/analysisservices/2010/engine/200/200" xmlns:ddl300="http://schemas.microsoft.com/analysisservices/2011/engine/300" xmlns:ddl300_300="http://schemas.microsoft.com/analysisservices/2011/engine/300/300" xmlns:ddl400="http://schemas.microsoft.com/analysisservices/2012/engine/400" xmlns:ddl400_400="http://schemas.microsoft.com/analysisservices/2012/engine/400/400">
    <KeyErrorLogFile>D:\temp\processing_errors.log</KeyErrorLogFile>
  </ErrorConfiguration>
  <Parallel>
    <Process xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:ddl2="http://schemas.microsoft.com/analysisservices/2003/engine/2" xmlns:ddl2_2="http://schemas.microsoft.com/analysisservices/2003/engine/2/2" xmlns:ddl100_100="http://schemas.microsoft.com/analysisservices/2008/engine/100/100" xmlns:ddl200="http://schemas.microsoft.com/analysisservices/2010/engine/200" xmlns:ddl200_200="http://schemas.microsoft.com/analysisservices/2010/engine/200/200" xmlns:ddl300="http://schemas.microsoft.com/analysisservices/2011/engine/300" xmlns:ddl300_300="http://schemas.microsoft.com/analysisservices/2011/engine/300/300" xmlns:ddl400="http://schemas.microsoft.com/analysisservices/2012/engine/400" xmlns:ddl400_400="http://schemas.microsoft.com/analysisservices/2012/engine/400/400">
      <Object>
        <DatabaseID>AdventureWorks</DatabaseID>
      </Object>
      <Type>ProcessFull</Type>
      <WriteBackTableCreation>UseExisting</WriteBackTableCreation>
    </Process>
  </Parallel>
</Batch>