TM1 Forum

I just started to get this error- haven't seen this before today. I'm simply trying to slice data from our Finance cube into Excel and save it. I get all the way up to the point of the name and location of the file, click on save, and Excel crashes. Here is the cube view that I am trying to slice: Here is the Save As window: This is the error message that is displayed: Has anybody else had a problem like this? I've already left a message with my VAR, but haven't heard back from them yet. Thanks for your help!

I'm assuming that you've already tried shutting down and restarting Excel?

I doubt that it has much to do with the fact that it's a TM1 slice; at that point you're saving an Excel workbook which just happens to have TM1 formulas in it. (I'm also assuming that you have your options set to manual calculation, and do NOT calculate before save. If you do, you've taken TM1 entirely out of the equation.)

This is a long shot, but about a billion years ago when I was a regular in the Excel Usenet forums we found that Excel would often misbehave and crash if your Temp directory was over-cluttered with junk. Try the following:
- Open Windows Explorer;
- In the address bar, type %Temp% to take you to your own Temp folder;
- Clear out as much junk as you can (you won't be able to delete everything since some of the files will still be in use);
- Try saving a slice again and see whether that makes a difference.

As I said, a bit of a long shot but it can't do any harm.

Alan-

Thanks for the suggestions. I changed the calculation setting to manual, and unchecked "Recalculate before Save". I also deleted as many temp files as I could. No dice. Funny enough, when I snapshot the data out, instead of slicing it, the worksheet will save without crashing Excel. I also tried copy-paste special-values for all of the TM1 fomulas (DBRW & SUBNM), but that didn't help. Next step is to wait for my VAR and open up a trouble ticket with IBM/Cognos.

Worthy of note: This seems to only occur with one cube. I tried the same with another cube, and the file saved fine without crashing Excel. Maybe the .cub file has been corrupted somehow? My VAR is going to open up a trouble ticket- we'll see what happens. If the .cub file has been corrupted, I wonder if the problem would be fixed if I used a backup copy...

Just noticed that you have a program name of "0000" in your dimension. It's possible that excel interprets this as a blank cell at some point and then the slice fails. Do you get the same results with this cube with a different project number?

In general terms its bad practice to have numeric only element names since Excel can sometomes decode to convert them into dates and so on.

Just a thoguht!
Cheers

Hmm might be right there. TM1 would see that (if it was a data point) as empty. Excel would always see that as a blank cell. If the slice is trying to calculate values in Excel based on an "empty" cell as an element reference there is more than a slight chance it would get its knickers in a knot and die horribly. Steve's suggestion will prove or disprove that, try the same slice but without that element in and see what happens. If its fine then you'll have to get your users to agree to a different element naming convention

Sometimes the naming convention can't be changed. A bunch of our elements come from Oracle GL and are numeric-only. Every dimension has an all-zeros element, and all elements are zero-padded too. I've found that it's best to plan for formatting issues and now build TEXT() into the DBRWs for "real" templates that I send around.

That being said, those have never caused crashes, and I'd be surprised if a corrupted cube, server-side, is crashing the client. I've been able to solve most Excel crash issues by installing all of the Excel patches at office.microsoft.com. After that, as Alan recommended, ensuring that automatic calculation disabled helps a lot too.

Matt

It's gone. The IT guy came over and took a peek at the Process Monitor that was filtered just for Excel processes. Seems like the point of crashing was when it was trying to write to 'desktop.ini'. When we tried to locate the file via windows explorer, it was nowhere to be found, even with hidden files and folders being displayed. We searched for the file, and the OS "found" it in the docs&settings directory under my username, but we couldn't visibly see it. He decided to run a chkdsk /f to see if any indexes had been corrupted, and I also remapped the shortcut to tm1p.xla on my desktop, just in case. I also downloaded/installed Office updates (although most of them were generic 'security updates' for Office; only one of them was a specific 'security' update for Excel). Now I can save the worksheet without crashing the app. Thanks for your suggestions and comments!