Hi All,

I am trying to debug this cube issue but unable to figure out the root cause of issue. I am quite new to SSAS. Can someone help me to proceed in right direction? Thanks.

07/16/2015 03:30:00,ecc_Cube_CallCenterAgent,Error,1,SA0SQL114,ecc_Cube_CallCenterAgent,ecc_Cube_CallCenterAgent,,Executed as user: AUTOCLUB\gid00103. ... 10.50.6000.34 for 32-bit  Copyright (C) Microsoft Corporation 2010. All rights reserved.    Started:  3:30:00 AM  Error: 2015-07-16 03:37:49.80     Code: 0xC11F000D     Source: SSAS - CallCenterEmployee Analysis Services Execute DDL Task     Description: Errors in the OLAP storage engine: An error occurred while the 'Error3 Comments' attribute of the 'AO_Audit' dimension from the 'CallCenterPerformance' database was being processed.  End Error  Error: 2015-07-16 03:37:49.80     Code: 0xC1000007     Source: SSAS - CallCenterEmployee Analysis Services Execute DDL Task     Description: Internal error: The operation terminated unsuccessfully.  End Error  Error: 2015-07-16 03:37:49.80     Code: 0xC11C0006     Source: SSAS - CallCenterEmployee Analysis Services Execute DDL Task     Description: Server: The current operation was cancelled because another operation in the transaction failed.  End Error  Error: 2015-07-16 03:37:49.80     Code: 0xC11F000D     Source: SSAS - CallCenterEmployee Analysis Services Execute DDL Task     Description: Errors in the OLAP storage engine: An error occurred while the 'ID' attribute of the 'Time' dimension from the 'CallCenterPerformance' database was being processed.  End Error  Error: 2015-07-16 03:37:49.80     Code: 0xC11F000C     Source: SSAS - CallCenterEmployee Analysis Services Execute DDL Task     Description: Errors in the OLAP storage engine: An error occurred while the dimension<c/> with the ID of 'Status Hours'<c/> Name of 'Status Hours' was being processed.  End Error  Error: 2015-07-16 03:37:49.80     Code: 0xC11F000D     Source: SSAS - CallCenterEmployee Analysis Services Execute DDL Task     Description: Errors in the OLAP storage engine: An error occurred while the 'Status Hrs N' attribute of the 'Status Hours' dimension from the 'CallCenterPerformance' database was being processed.  End Error  Error: 2015-07-16 03:37:49.80     Code: 0xC11F000C     Source: SSAS - CallCenterEmployee Analysis Services Execute DDL Task     Description: Errors in the OLAP storage engine: An error occurred while the dimension<c/> with the ID of 'AceOpoly Goals'<c/> Name of 'AceOpoly Goals' was being processed.  End Error  Error: 2015-07-16 03:37:49.80     Code: 0xC11F000D     Source: SSAS - CallCenterEmployee Analysis Services Execute DDL Task     Description: Errors in the OLAP storage engine: An error occurred while the 'Ace Opoly Key' attribute of the 'AceOpoly Goals' dimension from the 'CallCenterPerformance' database was being processed.  End Error  Error: 2015-07-16 03:37:49.80     Code: 0xC1060000     Source: SSAS - CallCenterEmployee Analysis Services Execute DDL Task     Description: OLE DB error: OLE DB or ODBC error: Operation canceled; HY008.  End Error  Error: 2015-07-16 03:37:49.80     Code: 0xC11F000C     Source: SSAS - CallCenterEmployee Analysis Services Execute DDL Task     Description: Errors in the OLAP storage engine: An error occurred while the dimension<c/> with the ID of 'Driving School'<c/> Name of 'Driving School' was being processed.  End Error  Error: 2015-07-16 03:37:49.80     Code: 0xC11F000D     Source: SSAS - CallCenterEmployee Analysis Services Execute DDL Task     Description: Errors in the OLAP storage engine: An error occurred while the 'Firm Key' attribute of the 'Driving School' dimension from the 'CallCenterPerformance' database was being processed.  End Error  Error: 2015-07-16 03:37:49.80     Code: 0xC11F000C     Source: SSAS - CallCenterEmployee Analysis Services Execute DDL Task     Description: Errors in the OLAP storage engine: An error occurred while the dimension<c/> with the ID of 'Kronos Codes'<c/> Name of 'Kronos Codes' was being processed.  End Error  Error: 2015-07-16 03:37:49.80     Code: 0xC11F000D     Source: SSAS - CallCenterEmployee Analysis Services Execute DDL Task     Description: Errors in the OLAP storage engine: An error occurred while the 'PAYCODEID' attribute of the 'Krono...  The package execution fa...  The step failed.,00:07:51,0,0,,,,0

No, we can't tell from that error message as it's been truncated and the root cause of the error does not appear to have been captured. Analysis Services processes multiple objects in parallel, all we are seeing the message you posted are the warnings raised by the rollback of the other operations that were happening at the same time as the "real" error.

If that's the only log that you have then you will need to manually kick off a process from Management Studio so that you can see the root cause of this failure.

THis is the real issue. I dont know why everytime any one of the measure group fails intermittent with same error message. It is looking for a view that I created to removes duplicate from a table. When I process all the dimensions together, process is successful. It is happening only when I process cube full.

 

• Edited by Dee25 10 hours 45 minutes ago

The error is coming from a measure group, so you should not see this issue when processing dimensions. 

That is an error coming back from the relational source. If you copy the query out from the SQL Query node under the error you *should* get the same error. 

When you say it fails intermittently do you mean that sometimes the processing works and sometimes it doesn't? Or that the error appears on different objects each time? 

Thanks for your reply Darren.

Yes thats correct. If I copy query and run in SSMS it gives me same error. It is because it is inter database query which is calling the same view(the one mentioned in error) from different database. How do I fix this? Is there a way to edit this query? I can add database name in front of view.

By intermittent I meant everytime it occurs on different measure groups.

• Edited by Dee25 8 hours 53 minutes ago

OK, so you need to fix this so the query can run. If you are using a recent version of SQL Server you could maybe create a synonym in you main database and reference that, otherwise you should be able to create a view in your main database using a 3 part name to reference this other view (eg. select ... FROM  MyDatabase.dbo.MyView )

This probably occurs on every measure group that references this view, but because SSAS processes in parallel using multiple threads it just depends which thread catches the error first. 

Can I edit my view(which is shown in error) and give it a 3 part naming convention? Will that work?

Rather than creating a new view on top of existing view I was thinking if editing existing one can help.

Maybe - I can't tell from here as I don't know how you've built your DSV or where this view is being referenced from. But if you have a named query in the DSV then adding the 3 part name should work.

THis is the real issue. I dont know why everytime any one of the measure group fails intermittent with same error message. It is looking for a view that I created to removes duplicate from a table. When I process all the dimensions together, process is successful. It is happening only when I process cube full.

 

• Edited by Dee25 Tuesday, July 28, 2015 8:22 PM

THis is the real issue. I dont know why everytime any one of the measure group fails intermittent with same error message. It is looking for a view that I created to removes duplicate from a table. When I process all the dimensions together, process is successful. It is happening only when I process cube full.

 

• Edited by Dee25 Tuesday, July 28, 2015 8:22 PM

Thanks for your reply Darren.

Yes thats correct. If I copy query and run in SSMS it gives me same error. It is because it is inter database query which is calling the same view(the one mentioned in error) from different database. How do I fix this? Is there a way to edit this query? I can add database name in front of view.

By intermittent I meant everytime it occurs on different measure groups.

• Edited by Dee25 Tuesday, July 28, 2015 10:14 PM

Thanks for your reply Darren.

Yes thats correct. If I copy query and run in SSMS it gives me same error. It is because it is inter database query which is calling the same view(the one mentioned in error) from different database. How do I fix this? Is there a way to edit this query? I can add database name in front of view.

By intermittent I meant everytime it occurs on different measure groups.

• Edited by Dee25 Tuesday, July 28, 2015 10:14 PM

I renamed those named queries which used inter database queries and tried to process cube. Im still getting same error. Does it have to do anything with partitions for those measure groups which are failing?

Yes, if you have partitions with query bindings you will also need to fix this issue there. 

Hi Darren, I looked into all partitions and all of them are using table bindings. I don't understand this error, Why is it looking for that view even if I process some measure group which has no relation to this view?

I'm not sure. But it's going to be something in the design of your cube.

One thing you could try in order to locate the problem reference is to do a Build of your project. This will create a file with a .asdatabase extension in the "bin" folder of your project (you will have to use Windows Explorer to find this file). If you open up this file in a text editor or SSMS (I like to use SSMS as it can format the file to make it easier to read) you will see that it is basically the XMLA definition of your project. You can then search for the problem view name and find every where that it is referenced. This should allow you to find whatever setting or property has been overlooked - you can then go back into your project and fix whatever references you find.