TM1 Forum

Urgent.

Our TM1 admin password is locked due to overtimes wrong password logon attemptions.

Now as a securityadmin, how can we reset or release the admin's password?

Regards,
Chris

SecurityAdmins cannot assign people to the Admin group, including themselves. Nor can they assign themselves to DataAdmin.

The classic route out of this trap is to restart your server without }ClientProperties.cub. In the process you will lose all the passwords so you need a smart strategy to reset them to something after the server comes back up (i.e. write a TI to do this).

Terrible news.

Buy lucky, we made a backup last night, so there won't be much loss.

But where can we set the logon test times in TM1?

Regards,
Chris

wang_chris wrote:Our TM1 admin password is locked due to overtimes wrong password logon attemptions.

rmackenzie wrote:SecurityAdmins cannot assign people to the Admin group, including themselves. Nor can they assign themselves to DataAdmin.

The classic route out of this trap is to restart your server without }ClientProperties.cub. In the process you will lose all the passwords so you need a smart strategy to reset them to something after the server comes back up (i.e. write a TI to do this).

I think you misread the OP's problem. I *think* they are saying that the Admin account is locked due to maximum number of logon attempts exceeded. In which case a server restart would unlock the account, no need to remove the password unless no one knows what it is.

wang_chris wrote:Terrible news.

Buy lucky, we made a backup last night, so there won't be much loss.

Robin's suggestion was based on the assumption that you had forgotten the password. If you simply mis-entered it too many times, rebooting the server alone will clear the problem.
(Edit: Lotsaram just beat me to this one.)

wang_chris wrote: But where can we set the logon test times in TM1?

MaximumLoginAttempts in the tm1.cfg file.

Great news.

I restart the server and it's fine for admin to access system, thank you a million for your all.


Regards,
Chris

Another proven technique is to simply increase the "MaximumLoginAttempts" parameter (because it's dynamic) in tm1s.cfg for a few seconds and login before you go back to the original value. If it is not there, you need to add it with a higher value than 3 (default).

Thanks guys, indeed I mis-read it like they'd totally forgotten the password.