View script runtime settings in Performance Center - connect to Database error

 

 

 

 

ALM Performance 11, latest ALM & PC patches applied.

 

When editing a test and trying to view a scripts runtime settings I get the following error.

 

_______

 

Performance Center has encountered a fatal error
 Problem encoutered when application tried to connect to data base: failed OpenConnection: A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: TCP Provider, error: 0 - A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.)A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: TCP Provider, error: 0 - A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.)  

 

at HP.PC.DAL.Impl.DbContextImpl.OpenConnection(Boolean isLabProject, String project) at HP.PC.DAL.Impl.DbContextAdapter.Open(Boolean labProject) at HP.PC.DAL.DbContextHelper.GetLabContext(Boolean tx) at HP.PC.DAL.DbContextHelper.GetLabContext() at HP.PC.BL.QC.Repository.RepositoryBL.DownloadCachedEntity[TEntity](IEntityBL`1 entityBL, RepositoryOperationSettings operationSettings, Int32 latestVersion, RepositoryType repositoryType, Int32 bitFilter, Action`2 postDownloadAction) at HP.PC.BL.QC.Tests.TestBL.DownloadTest(RepositoryOperationSettings operationSettings) at HP.PC.Web.UI.DownloadManager.DownloadScript(Int32 scriptID, Nullable`1 version) at HP.PC.Web.UI.DownloadManager.DownloadScript(Int32 scriptID) at HP.PC.RTS.BL.RunTimeSettings..ctor(String sessionID, Int32 scriptId, String groupRTS, String groupRunLogic) at HP.PC.RTS.BL.RunTimeSettings..ctor(String sessionID, Int32 scriptId) at HP.PC.Web.UI.UserSite.RTS.RTSettings.get_RunTimeSettings() at HP.PC.Web.UI.UserSite.RTS.RTSettings.InitNavigationTree() at HP.PC.Web.UI.UserSite.RTS.RTSettings.Page_Load(Object sender, EventArgs e) at System.Web.Util.CalliHelper.EventArgFunctionCaller(IntPtr fp, Object o, Object t, EventArgs e) at System.Web.Util.CalliEventHandlerDelegateProxy.Callback(Object sender, EventArgs e) at System.Web.UI.Control.OnLoad(EventArgs e) at HP.PC.Web.UI.PageBase.OnLoad(EventArgs e) at System.Web.UI.Adapters.ControlAdapter.OnLoad(EventArgs e) at System.Web.UI.Control.LoadRecursive() at System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint)
Use case context : 269d44c0-e0ab-4971-8d5b-c8f0ba43ef49
at System.Data.SqlClient.SqlInternalConnection.OnError(SqlException exception, Boolean breakConnection) at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj) at System.Data.SqlClient.TdsParser.Connect(ServerInfo serverInfo, SqlInternalConnectionTds connHandler, Boolean ignoreSniOpenTimeout, Int64 timerExpire, Boolean encrypt, Boolean trustServerCert, Boolean integratedSecurity, SqlConnection owningObject) at System.Data.SqlClient.SqlInternalConnectionTds.AttemptOneLogin(ServerInfo serverInfo, String newPassword, Boolean ignoreSniOpenTimeout, Int64 timerExpire, SqlConnection owningObject) at System.Data.SqlClient.SqlInternalConnectionTds.LoginNoFailover(String host, String newPassword, Boolean redirectedUserInstance, SqlConnection owningObject, SqlConnectionString connectionOptions, Int64 timerStart) at System.Data.SqlClient.SqlInternalConnectionTds.OpenLoginEnlist(SqlConnection owningObject, SqlConnectionString connectionOptions, String newPassword, Boolean redirectedUserInstance) at System.Data.SqlClient.SqlInternalConnectionTds..ctor(DbConnectionPoolIdentity identity, SqlConnectionString connectionOptions, Object providerInfo, String newPassword, SqlConnection owningObject, Boolean redirectedUserInstance) at System.Data.SqlClient.SqlConnectionFactory.CreateConnection(DbConnectionOptions options, Object poolGroupProviderInfo, DbConnectionPool pool, DbConnection owningConnection) at System.Data.ProviderBase.DbConnectionFactory.CreatePooledConnection(DbConnection owningConnection, DbConnectionPool pool, DbConnectionOptions options) at System.Data.ProviderBase.DbConnectionPool.CreateObject(DbConnection owningObject) at System.Data.ProviderBase.DbConnectionPool.UserCreateRequest(DbConnection owningObject) at System.Data.ProviderBase.DbConnectionPool.GetConnection(DbConnection owningObject) at System.Data.ProviderBase.DbConnectionFactory.GetConnection(DbConnection owningConnection) at System.Data.ProviderBase.DbConnectionClosed.OpenConnection(DbConnection outerConnection, DbConnectionFactory connectionFactory) at System.Data.SqlClient.SqlConnection.Open() at HP.PC.DAL.Impl.DbContextImpl.OpenConnection(Boolean isLabProject, String project)
Use case context : 269d44c0-e0ab-4971-8d5b-c8f0ba43ef49

____________

 

I am logged on locally to the ALM server, with the SQL 2008 DB also on the same machine, and have 2 PC servers connected successfully.

 

I believe this to be a database access problem from the PC servers. What connection string does it use to try and connect

to the ALM database?

  • Please run the Health check from the Lab Management module on PCS/Host machines and see if you receive any errors.

     

    Madan

  • Verified Answer

    Health checks came out green.

     

    I have managed to solve the issue anyway, problem was a firewall issue blocking port 1433, managed to use DNS to route through another internal route where it wasn't blocked, then change the connection string for the project in Site Admin.

  • 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.   We discovered that the Windows file HOSTS (C:\Windows\System32\drivers\etc) contained an entry for that that database server but with the incorrect IP address.  Changing the entry to reference the correct IP address resolved the problem as did removing the entry from the file.