topic Re: New v5 install - Database "invalid credentials" in Server Management - Systems Insight Manager

New v5 install - Database "invalid credentials"

Jeff Rostis — Tue, 16 Aug 2005 16:31:01 GMT

During install of SIM, when setting up the database information, I recieve a "invalid credentials" upon hitting 'Next'. I have tried pointing at different databases, as well as several different domain accounts that have full access to the DB's.

What to try next?
Thanks!

Re: New v5 install - Database "invalid credentials"

Preston Gallwas — Tue, 16 Aug 2005 18:28:02 GMT

i ran into this same roadblock -- any help with this would be amazingly awesome! We're exicited about SIM 5 and getting rid of that java ;-)

Re: New v5 install - Database "invalid credentials"

Colin Moors — Thu, 18 Aug 2005 10:05:52 GMT

Sorry - this is a "me too" and not (sadly) a solution. I get to the point where I need to fill in my password to connect to SQL, and it tells me it requires SQL server 2000 SP3 or MSDE 2000 SP3. I am in fact already running SQL 2000 SP3, but cannot get past this point. All the credentials and detyails are correct as far as I'm aware, so I really can't imagine what the problem would be. A screen shot of the point of error is attached. Any thoughts or ideas welcomed!

-C-

Re: New v5 install - Database "invalid credentials"

Joe Wiedow — Thu, 18 Aug 2005 11:41:14 GMT

I originally ran into this same error as well in my upgrade installation. I found two items I needed to change to have the installation work.

1) Make sure that whatever account you are working with has access to the master database on the SQL server.
2) If you are using trusted authentication over tcp/ip, make sure that the time on both the SIM server and the database server are within a few seconds of each other. If there is too much of a drift between the two, the kereberos token creation will fail.

You can check to see if the trusted authentication is the issue by creating a dummy System DSN in Data Sources to your SQL server using Trusted Authentication. If you receive an error similiar to SSPI, then the time on the servers is most likely the issue.

Hope these help!

Re: New v5 install - Database "invalid credentials"

Jeff Rostis — Thu, 18 Aug 2005 11:57:13 GMT

Thanks for the replys...

I've tried master owner account that is used on the database, so I'm sure thats not an issue...

And the two systems are sync'd with our local time server...

Thanks!

Re: New v5 install - Database "invalid credentials"

Preston Gallwas — Thu, 18 Aug 2005 12:40:09 GMT

My username is "Administrator" -- and I'm unable to change it...the only user i have on the DB is 'sa'

I tried creating an Administrator account...no beans... :(

arg. its a default database install from SIM 4.2... arg.

Re: New v5 install - Database "invalid credentials"

Arne Reboot Andersen — Fri, 19 Aug 2005 04:38:14 GMT

Well. Count me in. I've got the same problems. And I'm sorry to say that I have no solution either.

But my thoughts goes to limitations due to GPO's in out Active Directory.

Could it be that the installation uses NTLM v 1 to update the DB ???

Have anyone tried to install on a standalone server ???

Re: New v5 install - Database "invalid credentials"

Preston Gallwas — Fri, 19 Aug 2005 13:53:56 GMT

I AM using a standalone server with MSDE hosted locally...I have a call into HP, but they haven't called me back today. Im going to call the mback after lunch

grr..

Re: New v5 install - Database "invalid credentials"

Jonathan Clark_2 — Mon, 22 Aug 2005 11:31:13 GMT

I got mine to work by switching the port number from 1433 to 1453. I have MSDE installed with other Named instances on the computer. Not sure why switching the port worked but hey now its working great.

I used typical install.
domain admin username/password for service account as well as database credentials.
svrnetcn to change the port number

works fine.

Re: New v5 install - Database "invalid credentials"

Preston Gallwas — Mon, 22 Aug 2005 12:47:48 GMT

I tried changing the port number and no beans for me.

I completely UNINSTALLED 4.2, and MSDE, and whacked all my previous data (GRRRR!!!!!!!!!!!!!) and still get the same error.

Dang it!

But apparently now my case with HP is escalated...GRR.....GRRRR

Re: New v5 install - Database "invalid credentials"

Joe Wiedow — Mon, 22 Aug 2005 13:52:30 GMT

Jeff,

Are you using a domain account when installing SIM 5 or a local administrator account?

Is the SQL server in the same domain as the SIM server?

Are you using the MSDE installation on the local server or a remote SQL server?

Is the database server you are connecting to a named instance?

Do you have port 1434 blocked in your network? If so, you may need to go into SQL client config (cliconfg.exe) and manually set the port of your named instance in order to connect.

Have you tried creating a trusted DSN connection to your SQL server using your installation account to make sure that you have access to the SQL server and to the master database on that server? What were the results of this test?

Re: New v5 install - Database "invalid credentials"

Jeff Rostis — Mon, 22 Aug 2005 14:02:44 GMT

Joe-
I am using a Domain Admin account to install, on a seperate SQL server within the domain. The SQL is a single instance, and I can connect and have full rights to the master database.

Re: New v5 install - Database "invalid credentials"

Jeff Rostis — Mon, 22 Aug 2005 14:19:50 GMT

I've just tried installing 4.2 and then upgrading to 5.0

4.2 installs just fine, but in the upgrade, the same 'invalid credentials' error comes up.

However, since 4.2 was able to access the SQL system and build the DB for itself, leads me to think that my settings and SQL access is working, and this perhaps an issue with the 5.0 installer?

Re: New v5 install - Database "invalid credentials"

Jonathan Clark_2 — Mon, 22 Aug 2005 15:29:20 GMT

Alright do you have MSDE installed with named instances. If so, do you have more than 1 instance on the server? I had to stop all instances of MSDE I had except for the one that I was going to use.

Also i spoke to HP and they gave me this reg file to use in order to enable advanced logging.

basically, run this file, delete your current C:\HPSIM.LOG and run the install agian. When it fails, open the new HPSIM.LOG and you'll have alot more info about it. Unfortunatly its gotten me no where except the product installed, cause now I'm having other issues. However it might help us all troubleshoot some.

Re: New v5 install - Database "invalid credentials"

Jeff Rostis — Mon, 22 Aug 2005 15:48:37 GMT

I am not using MSDE.
Thank you for the Reg File, hopefully it will help figure things out.

Re: New v5 install - Database "invalid credentials"

Darrin Rawls — Mon, 22 Aug 2005 15:52:13 GMT

Keep in mind a couple of things - first HP SIM wants to only use Windows Authentication (not SQL Authentication). Second, its trying to connect ONLY over TCP/IP (hench the port data). My guess is that is where it is bombing out. I wonder if TCP/IP connections are enabled in SQL?

Re: New v5 install - Database "invalid credentials"

Jeff Rostis — Mon, 22 Aug 2005 15:57:04 GMT

The SQL server is using windows auth. and are using TCP.

Re: New v5 install - Database "invalid credentials"

Jeff Rostis — Mon, 22 Aug 2005 15:57:34 GMT

The SQL server is using windows auth. and are using TCP. I'm going to scrounge the new log to see whats going on...

Re: New v5 install - Database "invalid credentials"

Darrin Rawls — Mon, 22 Aug 2005 16:24:48 GMT

Interesting, not sure what is going on there then in your case.

For those using Named Pipes and not TCP/IP (like in MSDE), you can change it using C:\Program Files\Microsoft SQL Server\80\Tools\Binn\svrnetcn.exe. FYI.

Re: New v5 install - Database "invalid credentials"

Preston Gallwas — Tue, 23 Aug 2005 11:12:30 GMT

Already done -- that was the first error I received upon trying to install it, and I corrected it, and have since rebooted many times

I completely uninstalled 4.2 and tried to install 5.0 flat, also uninstalling all accessories, MSDE, etc. Nothing, same error, same place.

I've got an open case with HP now, unfortunately the support rep replicated my error, but now it passed that screen. ;(