Hi,
some of the users are experiencing crashed when they download a snapshot on excel from TM1web 10.2.
Apparently it happens on random forms at random time ( I couldn't reproduce it).
Also the users themselves, they call me after a crash, they retry and cannot reproduce.
Do someone have had the same problems?
It seems not excel related (or at least, it seems not to occur outside the usage with TM1web).
Any Ideas?
tm1web 10.2 exports issue
-
- Posts: 78
- Joined: Tue Nov 30, 2010 1:18 am
- OLAP Product: TM1
- Version: 10.2.2
- Excel Version: 2010
Re: tm1web 10.2 exports issue
I think you're going to need to give us a bit more of a clue...
Is it Excel that crashes or windows?
Do the users have perspectives installed?
What OS does the user have?
What version of Excel are they running? Any FP?
Are there any Named Ranges with #REF in the sheet?
Does excel crash when the user tries to save the file, how about when they try and save it again?
Are there any links to other external files?
How big is the file?
etc (any thing else you can think of that may help!)
Is it Excel that crashes or windows?
Do the users have perspectives installed?
What OS does the user have?
What version of Excel are they running? Any FP?
Are there any Named Ranges with #REF in the sheet?
Does excel crash when the user tries to save the file, how about when they try and save it again?
Are there any links to other external files?
How big is the file?
etc (any thing else you can think of that may help!)
RHR
-
- MVP
- Posts: 3654
- Joined: Fri Mar 13, 2009 11:14 am
- OLAP Product: TableManager1
- Version: PA 2.0.x
- Excel Version: Office 365
- Location: Switzerland
Re: tm1web 10.2 exports issue
We have seen this quite a but too using 10.2.2 FP2.
User exports as snapshot from TM1 Web, then any subsequent editing of the file causes the user's Excel session to crash. We have found a work around is for the user to immediately save the file locally then close Excel fully and open the saved (exported) file. It can then be edited without causing Excel to crash. However the "workaround" is entirely unsuitable as it is a big inconvenience to users and it's an unrealistic expectation to be able to sensibilise users to go through these steps when they export from TM1 Web.
User exports as snapshot from TM1 Web, then any subsequent editing of the file causes the user's Excel session to crash. We have found a work around is for the user to immediately save the file locally then close Excel fully and open the saved (exported) file. It can then be edited without causing Excel to crash. However the "workaround" is entirely unsuitable as it is a big inconvenience to users and it's an unrealistic expectation to be able to sensibilise users to go through these steps when they export from TM1 Web.
Please place all requests for help in a public thread. I will not answer PMs requesting assistance.