New v5 install - Database "invalid credentials"

[andy steven]

How can v5 be released by HP it clearly does not work???

support has got so bad from HP recently (move of call centre to India) has not helped.

If HP want to have all this functionality they need to do more than market it, it needs to work.


I can not consider using HP management software, it seems to just not work. had a call open about PMP for about 4 weeks and still not been fixed, just dont think i will bother using the HP software in the future.

[Darrin Rawls]

Actually for HPSIM and the plugins, support is a dedicated team in the states (not anywhere else). When you call in, did you specificy 'Insight Manager' when you called in?

Sorry to hear your concerns I will definitely take your concerns back, we definitely take HP Support seriously.

What was your PMP case number so I can follow up with what happened there?

[andy steven]

Thanks Darrin

The case is 1208109211, i cant seem to get past India at the moment, they never get any of my emails with all the logs that the second line guys require in Holand, the Duch guys will not pick up the call till they get the logs.

Have contacted my account manager who has done nothing and has now gone on holiday.

My email is andy.steven@bra.boehringer-ingelheim.com

any help you can give would be great.

[Darrin Rawls]

You bet, I'll see what I can do to get this escalated.

[Alen Ahja]

Hi everybody!
I had the same problem during upgrading from 4.2 to 5.0.
Now it works. What had I done:

I started the Program "svrnetcn.exe" and configure the port to 1453.
Then I restarted the MSDE.
Now I reconfigured the port back to 1433 and restarted the MSDE again. And then the Upgrading procedure is running.

Regards

Alen

[Terry_92]

I have been watching this topic with a view to upgrading to SIM 5.

Hope to do it soon.

However I must agree with the problems with the India call centre and a SIM 4 problem I had. The tech keeps on asking for info, I reply via email and/or online, nothing for weeks!

[Abdul Elabbar]

i just found that the TCP/IP is not enabled. it works now thanks guys!

[Todd Schelin]

I think this is a problem with the upgrade procedure of HP SIM 5.0. I should not have this much headache installing a product onto my existing server. I have been extremely disappointed by this installation and have followed a lot of the instructions provided by others and have had no success. So, essentially my server has been down since the release of 5.0. Next question is I am hoping HP is addressing this issue and has an advisory that they can support to come out soon.

[Jason_188]

I have tried every potential solution listed in this article and I still cannot install SIM 5! Has hp officially recognized a problem? Is there a known working solution? I have not had SIM up and running now for over a week.

Thanks
Jason

ps - what is the best tech support number for SIM?

[Mike Wilson_15]

I have had the exact same problem with the invalid credentials. In the large corporate enviroment that I work in, things like changing ports, simplfying passwords, and even rebooting servers it NOT an option without a MAJOR exception to our policies.
HP SIM 4.2 worked fine and we have chosen not to upgrade until the issues with 5.0 are solved.
Now for the Invalid Credentials there are two duplicate entries in the Event Logs.

Application Events;
Source: MSSQLSERVER
Category: (4)
Type: Information
Event: ID 17055
Description:
18452: Login failed for user '(null)'. reason: Not asscoaited with the trusted SQL Server Connection.

Security Events:
Source: Security
Category: Logon/Logoff
Type: Failure
Event ID: 529
User: NT AUTHORITY]SYSTEM
Description:
Logon Failure:
Reason: Unknown user name or bad password
Logon type: 3
Logon Process: NtLmSsp
Authentication Package: NTLM

So until 5.0 is fixed we cannot use it.

[Graham Drew]

I used the reg file posted earlier and see the following:

[Thu Sep 15 09:39:11 UTC+0100 2005]Install Shell:CheckDBHost cmd /c set JAVA_HOME=.\jre & set PATH=.\ & .\jre\bin\java -cp ".;.\jtds-1.0.2.jar" sql/SQLServer -h "HOSTNAME" -pn "1433" -db "master" -dm "DOMAIN" -u "USER" -debug

(HOSTNAME, DOMAIN and USER have the "right" values in them really).

A search on the jtds....jar file finds nothing - in fact there is no .jar file under the {INSTALLDIRECTORY}/jre path.

I'm no wiser... except I'm more confused about the claim that Java is no longer used.

Graham (not Lindsay)

[sandu_1]

Mike,
This problem is more likely to occur when both Multi-Protocol and TCP/IP sockets trusted connections are attempted from the same client computer.

Try the following work arounds...

1. Disable multiprotocol for SQL Server using the Server Network Utility.

Since the username is null the failure is occurring outside of SQL Server

2. Whats is the startup account used for SQL Server Service ? Make sure
that this account has following rights,

- act as part of OS
- logon as a service
- increase quotas
- replace a process level token

[andy steven]

Is HP going to fix this , work arrounds are no exceptable in an enterprise environment

[sandu_1]

Hi all,

Please let me know the security policies and additional setup details that you set in your domain so that I can have a closer look at the issue...

[Graham Drew]

Sandu,

Can you give me an email address? There is 645K of data, which should probably not be broadcast on the net.

Graham (Not Lindsay)

[sandu_1]

Hi Graham,

You can attach 1 MB of data with each reply. So please attach it in the forum itself.

Thanks

[Graham Drew]

I would rather the data in my security profiles wasn't published on the net - even in an HP forum.

Rgds.,

Graham

[sandu_1]

Hi,

My e-mail id is sandu_330@yahoo.com

Thanks

[RobSmith]

Getting the same issues on our system as well.
The SIM server is Win2k3 Std, running its own copy of SQL2000, sp3a, no named instances.
Using an account created just for SIM to do the install, it has domain admin rights.

Whats killing me is this box used to have 4.2, I upgraded successfully to 5.0, and then as a Proof Out for testing, I did a complete install from scratch, and encountered this problem.
I should note though, that sql was also reinstalled from scratch as part of the prove out. But for their original installs, all the default values were used, with Windows authentication selected for the sql setup.

[Aravindh Rajaram]

Can you give the contents of the log file?

and I hope you did not have special characeters in your pwd; TCP/IP is enabled for SQL Server; you have mentioned the correct SQL port number during the install...

[RobSmith]

FOrtunately, this install took place in a proof of concept lab that I have set up. A reimage of the server's OS, and reinstall of the software has cleared up the issue.

The problem was possibly related to some residual registry entries from the previous install. Sorry I can't be of any more assistance.

[Darrin Rawls · Accepted solution]

We've been investigating this a bit more, and it all boils down to a security policy (for us to replicate this). Can someone check to see if this was your culprit too?

I'm attaching a word doc with some details and screen shots.

Let me know.

[Jason_188]

Yes, this was exactly the issue for me. What I find most interesting is hp's requirement to LOWER the default Windows security settings in order to use SIM. FYI, this is required for SIM to run, not just during installation.

Jason

[Darrin Rawls]

Correct, we are making an OS call for the authentication and that's what is requiring it (same type call to add users/authenticate login). We'll see if there is something different that can be done, but don't think so at this point.

[Jonas Back_2]

I'm just following this thread aswell and giving a suggestion to HP to consider reading the excellent paper "Windows Server 2003 Security Guide" by Microsoft with detailed guides how to secure the Windows OS. This includes securing Group Policy Settings like refusing LM/NTLMv1 and so on.

http://www.microsoft.com/technet/security/guidance/secmod216.mspx

Every Microsoft security seminar I've attended the last year or two has included information regarding this guide and I think more and more people are implementing it so HP better make sure their software works on secured systems. Because telling us to "Just don't secure your servers then it'll work" is not enough.

But I guess that HP will release a patch for 5.0 for this issue (if it has been confirmed).

I have this problem aswell and I also think it's because we've secured our servers and everything worked fine in 4.2. Will post here with my progress aswell.