Analysis Services 2005 Lock-up on Calculated Measures

AS 2005/VS 2005 is locking-up when I try to go to the calculated measures tab. It uses some CPU and I think a lot of I/O. My only way out is to close VS.

Everything else is working. I looked at the XML and it looked OK to me (naive me).

I have written out the xml and created another db/cube and the problem came along with the xml.

I'm stuck.

Tom

The calculation tab in BIDS (VS) has to do a parse of the script to display it in the UI, so this would suggest that there is something in the script that is giving it issues.

Try creating another database/cube using the xmla as you did before, but also do the following:

search for the <MDXScript></MDXScript> tags and copy the contents into another file for safe keeping|||

I tried that - no luck.

Also tried a transplant from a OK cube. I'm guessing it is not the mdx scripts.

It happens when I try to go to the translate tab and the perspective tab too (in addition to the calculated tab).

I also re-installed SS/AS/RP/IS 2005; (that was a train wreck)

I am still stuck; I'll try other tabs and maybe get a clue. Any assistance would be appreciated.

|||

OK, I did the previous post off the top of my head and as you must have figured out, you actually need to remove the data under the <MDXScript><Commands><Command><Text> Node to remove the calculation script.

The other structure under the MDXScript node is the <CalculationProperties> - this is where translations and display folders for the calculated members are stored so it might be this data that is causing your issue. This is the only data that I can think of at the moment that would appear in all three tabs that are causing you issues.

If you have not already, you could try the same approach as before, except you can actually remove all the calculation property nodes leaving just empty <CalculationProperties></CalculationProperties> tags.

|||

Got it!

Was behind on SQL server/AS updates and VS updates.

When I updated to cummulative SQL server updates and VS latest update the problem was resolved.

Thank you for your time and your input.

Tom