Invalid login name/password. (1067 Views)
Reply
Frequent Advisor
zzgh
Posts: 68
Registered: ‎02-12-2013
Message 1 of 13 (1,067 Views)

Invalid login name/password.

Hello,

 

I'm having this message when I try to login to SM9.30. "invalid login name/password .Please Try again".

 

Help pls.

Honored Contributor
Piku
Posts: 3,972
Registered: ‎06-17-2010
Message 2 of 13 (1,039 Views)

Re: Invalid login name/password.

Hi,

It simply means that either operator did not created in SM or password provided is incorrect.

hth,
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Assign Kudo, if found post useful and mark it accepted if solves the issue.
http://h30499.www3.hp.com/t5/Tips-and-Tricks/Kudos-what-where-how-and-why/m-p/5677925#U5677925
Frequent Advisor
zzgh
Posts: 68
Registered: ‎02-12-2013
Message 3 of 13 (1,038 Views)

Re: Invalid login name/password.

the DB is a backup from another DB and I used to log in normally. I tried the 3 operators that I have and none is working

Honored Contributor
Misaq
Posts: 790
Registered: ‎12-04-2005
Message 4 of 13 (1,011 Views)

Re: Invalid login name/password.

could you post sm.log entries related to this user login session.
Respected Contributor
Alex-D
Posts: 105
Registered: ‎11-01-2011
Message 5 of 13 (986 Views)

Re: Invalid login name/password.


In case you do not know operator`s password and because of that you are not able to login, you can reset this password following the steps bellow:

 

- Open SQL Studio
- Right click on SM database
- Select new query
- Type update operatorm1 set password='';
- Click execute

If you find this post useful/helpful click the Kudo star on this post!

If you find that this or any post resolves your issue, please be sure to mark it as an accepted solution.
Frequent Advisor
zzgh
Posts: 68
Registered: ‎02-12-2013
Message 6 of 13 (960 Views)

Re: Invalid login name/password.

it didn't work. I already know the passwords. I even tried to copy operators from another database. nothing is working. this is the sm.log file:

1228( 2020) 03/04/2013 16:56:09 RTE I Process sm 9.30.021 (021) System: 13080 (0x784DFB00) on PC (x86 32-bit) running Windows Server 2003 SP2 (5.2 Build 3790) from gmhoba (192.168.244.108)
1228( 2020) 03/04/2013 16:56:09 RTE I Connected to SOAP client at 192.168.244.108
1228( 2020) 03/04/2013 16:56:09 RTE I Thread attaching to resources with key 0x784DFB00
1228( 2020) 03/04/2013 16:56:09 RTE I Info: SQL State: 01000-5701 Message: [Microsoft][ODBC SQL Server Driver][SQL Server]Changed database context to 'JordanDB3'.
1228( 2020) 03/04/2013 16:56:09 RTE I Info: SQL State: 01000-5703 Message: [Microsoft][ODBC SQL Server Driver][SQL Server]Changed language setting to us_english.
1228( 2020) 03/04/2013 16:56:09 RTE I API=SQLConnect
1228( 2020) 03/04/2013 16:56:09 RTE I Connection established to dbtype 'sqlserver' database 'JordanDB3' user 'test'
1228( 2020) 03/04/2013 16:56:09 RTE I Connected to Data source 'JordanDB3' SQL server 'CIS-SM' version: 9.0.1399 through SQL driver version: 3.86.3959 using database 'JordanDB3' as user 'dbo'
1228( 2020) 03/04/2013 16:56:09 RTE I MS SQL Server collation 'SQL_Latin1_General_CP1_CI_AS', varchar codepage 1252, comparison 196609: case insensitive, accent sensitive
1228( 2020) 03/04/2013 16:56:09 RTE I Thread FBBF05A0A08F0EB63396424D0DA22293 initialization done.
1228( 2020) 03/04/2013 16:56:09 JRTE I Termination signal: 0
1228( 2020) 03/04/2013 16:56:09 RTE I -Memory : S(503704) O(271780) MAX(1218396) - MALLOC's Total(5009)
1228( 2020) 03/04/2013 16:56:09 RTE I Thread termination in progress
1228( 2020) 03/04/2013 16:56:09 RTE I Thread termination cleanup complete
1228( 828) 03/04/2013 16:56:11 RTE I Using "utalloc" memory manager
1228( 828) 03/04/2013 16:56:11 RTE I Process sm 9.30.021 (021) System: 13080 (0x784DFB00) on PC (x86 32-bit) running Windows Server 2003 SP2 (5.2 Build 3790) from gmhoba (192.168.244.108)
1228( 828) 03/04/2013 16:56:11 RTE I Connected to SOAP client at 192.168.244.108
1228( 828) 03/04/2013 16:56:11 RTE I Thread attaching to resources with key 0x784DFB00
1228( 828) 03/04/2013 16:56:11 RTE I Info: SQL State: 01000-5701 Message: [Microsoft][ODBC SQL Server Driver][SQL Server]Changed database context to 'JordanDB3'.
1228( 828) 03/04/2013 16:56:11 RTE I Info: SQL State: 01000-5703 Message: [Microsoft][ODBC SQL Server Driver][SQL Server]Changed language setting to us_english.
1228( 828) 03/04/2013 16:56:11 RTE I API=SQLConnect
1228( 828) 03/04/2013 16:56:11 RTE I Connection established to dbtype 'sqlserver' database 'JordanDB3' user 'test'
1228( 828) 03/04/2013 16:56:11 RTE I Connected to Data source 'JordanDB3' SQL server 'CIS-SM' version: 9.0.1399 through SQL driver version: 3.86.3959 using database 'JordanDB3' as user 'dbo'
1228( 828) 03/04/2013 16:56:11 RTE I MS SQL Server collation 'SQL_Latin1_General_CP1_CI_AS', varchar codepage 1252, comparison 196609: case insensitive, accent sensitive
1228( 828) 03/04/2013 16:56:11 RTE I Thread 6B0CAE41D5CCF69524923E37215698EF initialization done.
1228( 828) 03/04/2013 16:56:11 RTE I SOAP client information scguiwswt 7.11.043 (043) at 192.168.244.108
1228( 828) 03/04/2013 16:56:11 RTE I Stop request received from client
1228( 828) 03/04/2013 16:56:11 JRTE I Termination signal: 0
1228( 828) 03/04/2013 16:56:11 RTE I -Memory : S(644792) O(331556) MAX(1206108) - MALLOC's Total(11187)
1228( 828) 03/04/2013 16:56:11 RTE I Thread termination in progress
1228( 828) 03/04/2013 16:56:11 RTE I Thread termination cleanup complete
Honored Contributor
Piku
Posts: 3,972
Registered: ‎06-17-2010
Message 7 of 13 (934 Views)

Re: Invalid login name/password.

Log entries do not seems to relevant , do you have any working sysadmin user, if so then try to reset the password or create new user. Then check for the same.

hth,
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Assign Kudo, if found post useful and mark it accepted if solves the issue.
http://h30499.www3.hp.com/t5/Tips-and-Tricks/Kudos-what-where-how-and-why/m-p/5677925#U5677925
Frequent Advisor
zzgh
Posts: 68
Registered: ‎02-12-2013
Message 8 of 13 (926 Views)

Re: Invalid login name/password.

No, none of the users is working.

Honored Contributor
Piku
Posts: 3,972
Registered: ‎06-17-2010
Message 9 of 13 (924 Views)

Re: Invalid login name/password.

Hi,

Then take the unload of few sysadmin user from working environment and load them from command prompt.
Also use below parameter in sm.ini file to details analysis from sm.log file,

RTM:3
debugdbquery:999

hth,
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Assign Kudo, if found post useful and mark it accepted if solves the issue.
http://h30499.www3.hp.com/t5/Tips-and-Tricks/Kudos-what-where-how-and-why/m-p/5677925#U5677925
Regular Advisor
Vikky
Posts: 184
Registered: ‎12-12-2010
Message 10 of 13 (922 Views)

Re: Invalid login name/password.

Hi ,

 

Not sure but i think you need to check teh DB parametres in sm.ini file & listener.ora file.

 

If you not deleted the oob logins please check "System.Admin" with blank password.

 

Hope it help you.

Honored Contributor
Jas1
Posts: 411
Registered: ‎04-05-2010
Message 11 of 13 (917 Views)

Re: Invalid login name/password.

Confirm that your SM is pointing to the correct DB. Checked your ODBC settings. Confirmed the user used for the ODBC is linked only to the SM db and not defaulting to samples db.
Checked your sm.ini settings if its pointing to the correct DB with the correct user id.
I had similar issue in the past and turned out I was still pointing to an old db and not connected to the new db I was trying to access.
Advisor
stsav
Posts: 17
Registered: ‎10-31-2011
Message 12 of 13 (586 Views)

Re: Invalid login name/password.

A common scenario: Service Manager backup is configured to connect to LDAP.

To disable ldap in such case, simply add the following to your sm.ini (save, no restart needed):

ldapdisable:1

 

Service Manager Expert (HP Global Support Organisation)
If you find this post useful/helpful click the Kudo star on this post!
If you find that this or any post resolves your issue, please be sure to mark it as an accepted solution.
Honored Contributor
John Stagaman
Posts: 3,429
Registered: ‎07-13-2007
Message 13 of 13 (582 Views)

Re: Invalid login name/password.

[ Edited ]

Have you executed the sm -unlockdatabase command from the RUN directory?

 

I'm not sure at which release that became required, but when you start SM it associates the database to a particular SM application instance, and you need to unlock a database copy to allow a different application instance to use it.

----------------------------------------------------
Kudos - what, where, how, and why
Want Good Answers? Ask Good Questions...
The opinions expressed above are the personal opinions of the authors, not of HP. By using this site, you accept the Terms of Use and Rules of Participation.