TM1 Forum

On the client side we use Office 2007 on XP, on the server it's 2003 R2.
During the upgrade we will up that to Office 2013 on Windows 8 and Server 212 R2.

OK, I was checking to see if you were using server 2008 which has been tied down quite considerably. I would now look Michel's point about the user being used to run the TM1 service,

Jim.

Nothing is changed to the user that runs the TM1 service and a TM1-Save works fine. It's just that when I try to run (or edit) a TI-process that uses an ODBC-connection the system hangs.
I guess the messages in the windows event log occur when the server is restarted after I had to manually stop the services (or when that didn't work kill the tm1sd.exe using the task manager) when the system hangs.
I now made workarounds for the import using the old-school I_PROCESS ("Process Data"), that is ok to use for a few weeks until we upgrade to 10.2.1. I hope the upgrade then also fixes the ODBC-problem.
Thanks all for your ideas !

Hi Hans,

Another logger you could try to get some usable debug info is Michel

Hi Everyone,

This has by far been the most helpful thread in diagnosing a similar issue I was having with a slugish Oracle 11g import through ODBC. Just thought I'd share my solution in case it helps anyone! After spending days trying everything from TI optimization, to stored procedure calls, and finally different Oracle ODBC driver versions, I finally gave in and called the Oracle support team. Turns out what I thought was a static table was just a complex view that executed LARGE queries (5 years of data between multiple tables) every time it was run. Once this was identified and the data was aggregated into a single table (refreshed daily), everything works in a matter of minutes vs. hours.

Moral of the story, sometimes it's worth picking up the phone.

Thanks everyone for your comments throughout this thread!