TM1 is out of memory, exiting...

[Catherine]

Hi everybody,

Our users experience some excel crashes, with the message: "TM1 is out of memory, exiting...".
This is is a crash on the client side, everything is fine on the server side.
This always happens when refreshing Excel reports (not in Perspectives itself).

Our TM1 version is 9.4.1 FP3 HF21, with Excel 2007. This message has appeared since we applied HF21. Is it a coincidence or not ?

Any suggestion on the cause of this problem?

Thank you in advance

[declanr]

What sort of sheets are the users trying to open?

If it is essentially a big part of a cube it could just be that they are trying to view shedloads of data and it can't cope.
If you are using dynamic subsets in the sheet, perhaps try and build an equivalent static version and see if the same error occurs.

[lotsaram]

This is caused by Excel going over the 2Gb application limit in 32 bit Windows OS. I have seen this a bit with users trying to refresh really big Active Forms (big like 50,000 rows) where a static report of the same size is slow but does refresh without crashing Excel. VBA is notoriously flaky with memory allocation and leaks and my guess is that the extra VBA used to drive active forms is behind it.

Do you know what the users are doing in besides opening a very big view? (In terms of exact UI e.g. Perspectives cube viewer, static slice, or active form)

[Olivier]

have seen this a bit with users trying to refresh really big Active Forms (big like 50,000 rows) where a static report of the same size is slow but does refresh without crashing Excel.

I have seen a message "Selection is too large" for the exact same symptoms ? ( Using 9.4 and Excel 2003 on XP).
Then press OK for each instance of the warning message and end up with a half baked active form result...

[Catherine]

As a matter of fact, this message appears when opening "big" Excel reports.
But the thing is (after some testing) that it is clearly linked to HF21. The problem first appeared after the hot fix installation. Some Excel files refreshing before without problem are now provoking this error.

I have opened a PMR at IBM, and I gave them all material necessary to reproduce the problem. Waiting from a hot fix from them, we'll downgrade to HF12...

Thank you all for your help