TM1 Forum

Hi-

Has anyone encountered this situation where there is a single user (client) that can access TM1 Web fine and dandy, but gets the credential error ("Could not logon to any available servers with the provided credentials") when trying to access TM1 Applications/Contributor? I'm ruling out that it is the user's computer, as I had her try logging in directly on the server that TM1 is installed on and she still got the error, but I was able to log in fine. I've also checked that the Group she is in has EDIT rights to the application and she is in the Group }tp_Everyone.

This is happening with TM1 10.2.2. The security uses mode 3 with LDAP. IntergatedSecurityMode=3, SecurityPackage=Kerberos
I checked the log file and there was nothing funky in it at the time she tried to log in and got the error. On days that she has logged into TM1 Web, the log file notes it correctly that she has been validated. None of the other users are having this problem.

Thank you in advance for your help.

Have you checked Security Overlay which implements an additional layer of security between TM1 and contributor applications?

Are any of your other users in the same security groups as your problem user?

Hi Edward-

I don't see any Security Overlay cubes in the model. This is the only user that is having the problem and I even created a test user that mimics her security groups and the test user (client) doesn't have a problem.

Does the user have any quirks in their tm1.ini file? Have you tried clearing the cache on the user machine? Does the same issue present when a user logs in via a different machine?

I haven't checked the user's .ini file as they only would use TM1Web or TM1Applications. The error happens on any machine she tries to access TM1 Applications. I had her try to log in on the machine that TM1 is installed on and IT had her try on another machine and she got the same error both times. Would an .ini file "haunt" her on every machine?

I think we figured out the culprit on this. It appears that TM1 Applications does not like certain special characters in the password. The @ and ! seem to be okay, but one of these is causing a problem: $:). The client user passwords for TM1 are their network password, which requires them to use a special character. The offending special characters do NOT seem to affect TM1Web access though.