Submit a ticketCall us

Cloud Workloads: Meet Your New Hybrid IT Reality
Have you found yourself in that evolving, hybrid IT grey area and wondering if cloud workloads are now part of your purview? And if so, will monitoring cloud workloads require a new set of dedicated cloud monitoring tools? Your answers: yes, they should be, and no, they don’t.

Find out how SolarWinds® Server & Application Monitor (SAM) can help you monitor your cloud workloads side by side with your on-premises workloads. Register Now.

Home > Success Center > Database Performance Analyzer (DPA) > DPA for SQL Server installation troubleshooting

DPA for SQL Server installation troubleshooting

Overview

This article helps you troubleshoot problems you encounter while setting up DPA, creating SQL Server repositories, or registering SQL Server databases for monitoring in DPA.

Resolution

Using Windows Authentication but seeing login is from an untrusted domain connection errorEdit section

Q: I am getting an "invalid host" error message.

A: Try using the IP address of the SQL Server Host machine instead of the host name.

A: Try using the fully qualified name of the SQL Server Host machine instead of the short host name. Example: Use SQL-HOST.confio.com in place of SQL-HOST.

A: Make sure you can ping the SQL Server Host from the DPA server host and that there is not a firewall blocking the connection.

 

Q: I am getting a "connection could not be established" error but I know that SQL Server is running.

These are the most common reasons and resolutions for this error:

A: If you have only specified a Server and not a Server\Instance, make sure the SQL Server instance you are registering is the default instance. If you are connecting to a Named Instance, enter that information in the Server field as Server\Instance.

A: If you have specified a Server\Instance, make sure that the DPA server can resolve the server name. To do this, remove the \Instance from the Server line, enter 1 for the port value, and click Next. If the error you receive is "The host is incorrect. Correct the host entry." See help for an invalid host. If you again receive a connection could not be established error, the hostname was able to be resolved. Please see the other Answers in this section to find a resolution.

A: Ensure that TCP/IP is enabled by viewing the following settings in the SQL Server Configuration Manager for the SQL Server instance. If either of the following are disabled, they must be enabled to proceed with DPA registration. (If your SQL Server Administrator will NOT allow this see below for how to use Named Pipes)


 


 

A: Ensure that if you have only specified a Server and not a Server\Instance that the Port entry is correct and that the instance you are trying to register is the default instance. To determine the port for a default instance, open the SQL Server Configuration Manager for the SQL Service Instance, select the TCP/IP Properties, and enter the Default Port value in the port field on the wizard.

 



 

Q: My SQL Server Administrator will not turn on TCP/IP for the SQL Server instance. What can I do?

A: By default, DPA connects to SQL Server instances via TCP/IP. If the instance cannot be configured for TCP/IP connections, DPA can be configured to connect using named pipes. See this article for detailed instructions on how to enable Named Pipe connections in DPA.

 

Q: I specified a Server\Instance to register a named instance but received the error "SQL Server Instance could not be retrieved."

A: Ensure that the SQL Server Browser Service (SQL 2005 and up) or the SQL Server Resolution Protocol (SSRP) listener service (SQL 2000) is Started and has a start mode of Automatic on the SQL Server host. (Note: If the start mode is not set to Automatic, DPA cannot connect to the SQL Server instance if you restart the SQL Server host but do not start this service manually.)


 

Select the Service tab to ensure that the Start Mode is set to Automatic for the SQL Server Browser, and click Apply:


 

Click the Log On tab to start the service if it is stopped:


 

Once the service starts, click OK and return to the Register Instance Wizard to continue.

 

Q: I specified a Server\Instance to register a named instance but received the error "Could not get JDBC Connection; nested exception is java.sql.SQLException: Server SERVER has no instance named INSTANCE."

A: Make sure the Server and Instance are correct.

A: Make sure that TCP/IP is enabled for this instance by viewing the following settings in the SQL Server Configuration Manager for the SQL Server instance. If either of the following is disabled, they must be enabled to proceed with DPA registration. If your SQL Server Administrator will not allow this, DPA can be configured to use Named Pipes.

settcpenabled1.png
 

settcpenabled2.png


 

Q: My SQL Server Administrator will not turn on the SQL Server Browser. What can I do?

A: In order to register a named instance without having the SQL Server Browser enabled, TCP Dynamic Ports must be enabled and set to a value. To find this value, open the SQL Server Configuration Manager for the SQL Service Instance, select the TCP/IP Properties for the SQL Server Network Configuration Protocols, and then click the IP Addresses tab.


 

After you have the TCP Dynamic Ports value, enter only the Server value (not the Server\Instance value) in the Server field of the Register Instance Wizard and enter the TCP Dynamic Ports value in the Port field to continue.

 

Q: I requested that the SQL Server Host and Port combination be opened on our firewall, but I am still getting errors. How can I tell if our IT department has actually opened the ports so I can register our SQL Server instance?

A: Use Telnet to check that a TCP connection can be established to the SQL Server host and port. If the Telnet connection fails, the SQL Server Host and Port combination has probably not been opened for access from the DPA server.

To determine if the port is being blocked by a firewall, open a command prompt and type:

telnet SERVER PORT

Where SERVER and PORT are the known server hostname or server IP address and port combination that SQL Server is running on. An unsuccessful or blocked TCP Connect will show the following:


 

A successful TCP Connect will change the command prompt to a Telnet window:


 

Q: Our SQL Server uses Windows Authentication and I have verified my user name and password, but I keep getting the error "The login failed for user. The user is not associated with a trusted SQL Server connection."

A: Certain Microsoft Domain configurations require authentication with the Domain Controller to use NTLMv2. By default, DPA authenticates with the Domain Controller using NTLM when using Windows authentication.

 

Q: I am attempting to connect to a SQL Server 2008 instance using Windows Authentication, but I keep getting the error "Login failed. The login is from an untrusted domain and cannot be used with Windows Authentication."

A:This error is generated by SQL Server 2008 when the Windows account credentials are not valid. Ensure that the domain and user name (in the format of DOMAIN\user) and password are correct. Ensure the account is enabled and has not become locked out.

 

Q: I installed DPA on a new server and I see the "repository already exists in this location" error in the wizard. How do I connect to the existing DPA repository?

A: If you moved the DPA server but left the repository on a SQL Server instance, see this knowledge base article on how to move the DPA server. If you need to move the DPA repository (the set of tables in DPA residing on a database), see this knowledge base article.

 

Q: Still unable to register?

A: Contact SolarWinds support through the customer portal with the errors you see.

Last modified

Tags

This page has no custom tags.

Classifications

Public