Discovery Accelerator client will not connect. 'Retrieving the list of instances from server...' does not complete.
Article ID: 100030908
Updated On:
Description
Error Message
On the DA server the following event is seen:
Event ID: 130
Description:
APP AS - Customer ID: 7 - An error has occured when initializing the Customers. System.Data.SqlClient.SqlException: 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: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server)
Description:
APP AS - Customer ID: 7 - An error has occured when initializing the Customers. System.Data.SqlClient.SqlException: 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: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server)
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 KVS.Accelerator.Configuration.Customer.GetCustomerDS(Int32 CustomerID, String VirtualDirectory, String Version, Int32 ServerID, CustomerState State)
Additionally, Events 148, 149, and 201 may be seen on the DA server with similar event descriptions relating to connections to the SQL Server.
Cause
These errors indicate a possible loss of communication with the Microsoft SQL Server that hosts the DA Configuration and /or Customer databases.
Resolution
Log onto the DA server and:
- If the name of the SQL Server is not known, open the AcceleratorManager.exe.config file in NotePad. This file can be located in the DA installation folder (default location is C:\Program Files\Enterprise Vault Accelerator Manager)
- Search for string ‘"DSNConfiguration" value="server=
- The SQL server name is after the ‘server=’
- Open a Command Prompt window
- Use the PING command to determine if the communications link between the DA server's network card and the SQL Server's network card is available (i.e., ping sqlserver1)
- If the PING command returns connection timeouts for every attempt, check the SQL Server to ensure it is running and connected to the network
- If the SQL Server is running and connected to the network, check the network connections and devices between the DA and SQL Servers to determine why these servers cannot communicate
- Resolve the connectivity issue and ensure the SQL Services on the SQL Server are running
- After the connectivity has been re-established between the DA and SQL Servers, restart the Enterprise Vault Accelerator Manager Service (EVAMS) on the DA server and attempt to connect via the DA client again.
Issue/Introduction
Discovery Accelerator client will not connect. 'Retrieving the list of instances from server...' does not complete.
Was this article helpful?
Yes
No
Powered by
