TM1 Forum

Dear Forum users,

Our TM1 system is upgraded from 9.4 to 10.2.2. The user name and password are achieved from Windows Active Directory. However after upgrade, there is a problem: newly created user account in TM1 system will be unavailable after few days (say one week). The first day or second day after creating the account is fine, user can login to TM1 web. But after few days, user can't login TM1 web anymore. The error message is: Login is failed, please try again.

Only delete this user account in TM1 system, and create it again, could solve the problem. But after a few days, the problem comes again. It is really annoying. Could some one please give me a help?

Thanks a lot.

Learn_TM1

This is going to be a shot in the dark but many of my recent TM1 Web issues seem to be resolved by clearing the cache on the browser-my users have been using Internet Explorer and do Ctrl+Shift+F5 or Ctrl+Shift+Refresh (icon on address bar)

Hi gtonkin,

Thanks for your reply. I asked my user to try in this way:
1. Open IE
2. Ctrl-Shift-F5
3. Try to login TM1 Web.

But this user still can't login.

Should I also perform the following steps in order to solve the problem?
1- Stop IBM Cognos TM1 Application service (this stops Tomcat), please ensure it is stopped checking that in the Task Manager the
"IBM Cognos TM1 Application Server" is really stopped.
2- Move the following folders into another directory as a back up:
C:\Program Files\ibm\cognos\tm1_64\tomcat\work\Catalina\localhost\tm1web
C:\Program Files\ibm\cognos\tm1_64\tomcat\work\Catalina\localhost\pmhub
C:\Program Files\ibm\cognos\tm1_64\tomcat\work\Catalina\localhost\pmpsvc
3- Restart the TM1 Application service, this will redeploy the folders moved.
4- Clean the cache of the browser.


Best regards,

Learn_TM1

Not sure about clearing all the caches and folders on the server but my guess would be that if this works then it could be a validity on something to do with Kerberos etc. Never had this before and have been running 10.2.2 FP4 now for two months at a client where the only restart on Tomcat and TM1 has been due to planned maintnenance. Only had issues with the client cache where users who logged in on 10.2.2 base could not connect once we upgraded to 10.2.2 FP4 without clearing their cache first.