Database Connection Error: failed OpenConnection for PC servers

[HardcoreTester]

Database Connection Error: failed OpenConnection: Login failed. The login is from an untrusted domain and cannot be used with Windows authentication.

When i do a "Check System" in labmanagement under the tab Performance Center i get the above error for both our PC servers.

In ALM, when i try to open an uploaded vuGen script i get the following error:

Problem encoutered when application tried to connect to data base: failed OpenConnection: Login failed. The login is from an untrusted domain and cannot be used with Windows authentication.Login failed. The login is from an untrusted domain and cannot be used with Windows authentication.

Does anyone know how to fix?

[sebastiena · Accepted solution]

Hi,

Can you confirm the version you are using?

I have seen such errors in the past when you configure your database to use Windows Authentication but you left the PC System user to its default (IUSR_METRO).

Changing the PC system identity to the user you are using to access the databse for Windows Authentication or to a domain user that has the same right on the databases will allow you to fix the issue.

Please refer to the following guides:

Performance Center Installation Guide - http://support.openview.hp.com/selfsolve/document/KM00425855

Section "Enabling MS-SQL Windows Authentication" page 137

Performance Center Administrator Guide - http://support.openview.hp.com/selfsolve/document/KM00425856

Section "How to Change the System User" page 458

Let me know if any of the above information is unclear

[HardcoreTester]

That solved this problem for us.

We are working with ALM PC 11.50 on Windows 2008 sp2 servers.

[Randy Waldorf]

When this problem occurred in our environment, we were using ALM PC 11.52  and transitioning to a new standalone database server, SQL Server 2008 R2 SP2 on a Windows Server 2012 R2 machine.  It turned out that the local account IUSR_METRO on the new database server had been assigned an incorrect password when the account was added to the server.   Changing the password for this account on the database server to match the password already assigned to this account on the other Performance Center machines resolved the problem.