topic Re: SIM 6.2 no longer can connect to SQL instance in Server Management - Systems Insight Manager

SIM 6.2 no longer can connect to SQL instance

NJK-Work — Wed, 10 Nov 2010 22:38:41 GMT

I installed a SIM 6.2 test server. The server is Windows 2008 R2 and SQL 2008 R2 (installed locally). Was working fine for a few weeks and now I get these messages:

Login failed. The login is from an untrusted domain and cannot be used with Windows authentication...

SSPI handshake failed with error code 0x8009030c, state 14 while establishing a connection with integrated security; the connection has been closed. Reason: AcceptSecurityContext failed. The Windows error code indicates the cause of failure.

com.hp.mx.database.DbVerificationException: Error loading database verification handler 'com.hp.mx.database.MsSqlVerificationHandler'
com.hp.mx.database.DbVerificationException: Error accessing database

The only that I can think of is that I change my password a few days. But I don't use my account for anything in SQL or SIM. I have a dedicated account for the SIM service - and that is still starting.

I used my account to INSTALL SIM, but it is not used to run any services.

SQL is running, SIM is running, just the two cannot talk to each other (or at least that is what I gather from the above logs).

Any ideas?

Thanks
Nelson

Re: SIM 6.2 no longer can connect to SQL instance

sam_193 — Thu, 11 Nov 2010 23:54:23 GMT

I dont think 6.2 is supporting SQL 2008 R2. I heard support is there for 6.2 udpates..

Re: SIM 6.2 no longer can connect to SQL instance

NJK-Work — Fri, 12 Nov 2010 01:57:15 GMT

Good point about the R2. Thanks.

I checked the database.props file and indeed my user name was listed there. I must of glazed over something and used my name by mistake.

Nelson

Re: SIM 6.2 no longer can connect to SQL instance

NJK-Work — Fri, 12 Nov 2010 01:58:42 GMT

Somewhere in the install I must have used my account by mistake. I am going to do a fresh install and try to figure out what I did wrong. Also possible support issue with using SQL 2008 R2.