Subscribe to this blog
Briefcase
Print
If you've ever had this error "OLE DB error: OLE DB or ODBC error: Operation canceled; HY008." appear while processing your cube you may be a little confused. Here were some of my frustrations with it:
-
First, this error doesn't really give you a single place to start looking.
-
Second, it may produce errors on several attributes that it has nothing to do with.
-
Last, there are plenty of references online asking questions about this error but not a lot of answers.
The only clue I had was one warning line after all the errors that referenced the column that was the culprit. The warning didn't even really directly tell me the problem but it did show me a column to look at. Turns out there were nulls in this column that caused the problem. I should have known! However, with the laundry list of errors that I was given it, that had nothing to do with the real problem attribute, it was hard to determine that nulls in a column was the real problem. Hope this helps!
Posted by david cleaves on 5 March 2009
Hi Devin,
I would really like to get to the bottom of this one and also a better in depth explanation maybe from Microsoft. I had a similar issue with nulls, but it never returned the same column as the source of the error, generally picking from a range of 5 fields.
What I discovered was that the way I had put attribute relationships into my hierarchy combined with the NULLS was the problem. When I took out teh attribute relationships which it couldn't enforce the problem went away.
david
Posted by Silvia Cobialca on 25 August 2009
We had this same issue, same error mesages, etc, but it solved after restarting the servers. Not sure if I look for NULLs if the restart woiuld fix it.
What do you think?
Posted by knight_devin@hotmail.com on 26 August 2009
Silvia
That's interesting. I wouldn't think restarting the server would solve that error. The problem is the errors are so undescriptive that it's hard to know what each error really means. Let me know if the error returns.
Devin
Posted by Franky Leeuwerck on 9 December 2009
Hello Devin,
We have seen this on a situation where the SSAS session went in timeout during the cube processing.
After adjusting the ExternalCommandTimeOut parameter, the problem was solved.
Regards,
Franky
Posted by knight_devin@hotmail.com on 9 December 2009
That's a great tip thanks Franky!
Posted by zaim_raza on 15 July 2010
Hi,
i have created one new dimension in cube and this cube is utlizing in SSRS report after successully adding in the cube as dimension and able to browse from cube browser but can't able to see this dimension in SSRS Cube dataset.
any idea that how i incorporate new dimension in SSRS existing cube dataset.
thanks in advance.
Posted by sunny on 26 August 2010
Hi Franky
where can i find the ExternalCommandTimeout Parameter??
I get same error when i process the cube.
Thanks
Posted by chrystalfaith on 8 November 2011
1. Location =
SSMS (SQL Server Management Studio) - Connect to the Analysis Services --> Right click on the server name and select "Properties" --> Check the box "Show Advanced (All) Properties"
2. Change value Find "ExternalCommandTimeout" and change the value to a higher one then the default of 360 and click OK to save
Note: The value is in seconds so if you want to find the hour value = 60 x 60 x number of hours
Posted by Chirag Prajapati on 17 June 2012
If you are getting as state by Devin.(Assuming error is because of NULL values)
One can do as given below and errors will apper. And Cube will happily processed and deployed.
1. Go to Cube Process Window
2. Click on Change Settings
3. Click on Dimension Key Errors
4. Change null key not allowed --> Report and Stop to Ignore Error.
Thanks,
Chirag Prajapati
Posted by Devin Knight on 18 June 2012
While you can do that. I wouldn't recommend it because you could be potentially hiding real problems with your data if you change that setting.
Posted by rlholmes on 26 May 2013
I am getting same error. Error processing changes to different attributes when processing the same dim. It does give HY008 at the 1 second mark. Any other options?
-No nulls in data - confirmed.
-The "ExternalCommandTimeout" is already set to 3600.