New v5 install - Database "invalid credentials"

[Jeff Rostis]

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!

[Preston Gallwas]

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 ;-)

[Colin Moors]

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-

[Joe Wiedow]

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!

[Jeff Rostis]

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!

[Preston Gallwas]

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.

[Arne Reboot Andersen]

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 ???

[Preston Gallwas]

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..

[Jonathan Clark_2]

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.

[Preston Gallwas]

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

[Joe Wiedow]

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?

[Jeff Rostis]

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.

[Jeff Rostis]

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?

[Jonathan Clark_2]

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.

[Jeff Rostis]

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

[Darrin Rawls]

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?

[Jeff Rostis]

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

[Jeff Rostis]

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

[Darrin Rawls]

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.

[Preston Gallwas]

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. ;(

[Darrin Rawls]

Okay, some points to ponder.

We have changed the way we connect to the db starting in HPSIM 5.0 (going away from the ODBC connection in Windows) to facilitate the same setup environment for Windows, Linux, and HP-UX. We are using a different method (java-based) that does things a bit differently than straight ODBC (so if ODBC works that might not mean anything). FYI.

Some initial investigations are showing if we can't talk to the db server, this error message is what you get (duh). Java in general is really finiky around naming. Doing a ping and/or nslookup on the IP of your db server should show correct data, if it doesn't all resolve correctly, you'll have some connection issues.

To see if that is what is going on, go into your HOSTS file on your SIM server (windows/system32/drivers/etc) and add an entry for your database server (hostname, full dns, and IP). Save, close, then try the SIM install and see if it gets past that.

If you have SIM installed, and are having connectivity issues like this (i.e. upgrade environment, etc.), then change DATABASE.PROPS file to point to the IP address rather than the name.

Just checking to see if this is the actual problem (i.e. not resolving names correctly due to latent DNS scavaging, etc.).

Post out if this helps or not. thanks!

[Preston Gallwas]

Well, I'm hosting MSDE locally -- should I change the IP in DATABASE.PROPS to our server ip (152.157.72.13) or 127.0.0.1 ?

In addition, our server (insight.puyallup.k12.wa.us) has a server name of psdtsc82k (which had a CNAME to INSIGHT, however, I removed it and added a host and PTR record)

I tried changing database.props to 72.13, restarted MSSQLSERVER and HP SIM services, but the installer still 'detects' the hostname PSDTSC82K

hmm...

[Aravindh Rajaram]

Hi All,

If in case you are trying to connect to a named instance (could be the single instance running) on the SQL server, then in the "Host" field of the "Database Configuration" screen, enter \
This worked for me when I faced the "invalid credentials issue".

Hope this helps!

[Darrin Rawls]

Good point; sometimes I forget the correct naming for instances! Also, are there any special characters being used in either the username or password (I'm assuming at least one was tried)? Let me know what that was so I can see if that might have been the cause possibly too.

[Preston Gallwas]

Yes, the password im using contains a semi-colon

I cannot edit any fields except password, and port