I work in a corporate environment with many TM1 users (ver 9.5). Recently some of them are having issues with Excel 2003 crashing. The main user that I am working with has Excel crash when he opens more than one workbook and does nothing more than move his mouse around. If he opens only one it will crash after about 10 minutes of use. I suspect the issue is related to about 20 security updates that were pushed down a couple of days before the issue started.
Any help would me much appreciated. Thanks - Kevin
Our configuration (This setup has worked in the past)...
*WinXP 32 bit - SP3
*Cognos TM1 ver. 9.5
*Office 2000 - SP3
*Excel & Outlook 2003 - SP3
Troublshooting step we have tried...*Office Repair
*Gave user local admin rights
*Rebuilt the user profile
*Uninstalled all of the above, rebooted and repushed Office 2000, Office 2003 then manual install of TM1. This worked for a while before the issue returned.
Excel 03 crashing after patches applied.
- Martin Ryan
- Site Admin
- Posts: 2003
- Joined: Sat May 10, 2008 9:08 am
- OLAP Product: TM1
- Version: 10.1
- Excel Version: 2010
- Location: Wellington, New Zealand
- Contact:
Re: Excel 03 crashing after patches applied.
You don't mention any evidence that this is TM1 specific - what happens if you remove the TM1 add-in? Is it still unstable? If so, try getting the latest hotfix. Otherwise raise a support call with IBM.
Martin
Martin
Please do not send technical questions via private message or email. Post them in the forum where you'll probably get a faster reply, and everyone can benefit from the answers.
Jodi Ryan Family Lawyer
Jodi Ryan Family Lawyer
Re: Excel 03 crashing after patches applied.
Martin, thanks for your reply.
The issue has been taken out of my hands but I will try to post back with the findings. There were issue with the add-in both enabled and disabled but we are not sure now if it is actually TM1 that is causing the problem.
The issue has been taken out of my hands but I will try to post back with the findings. There were issue with the add-in both enabled and disabled but we are not sure now if it is actually TM1 that is causing the problem.