This article will help you troubleshoot problems that you encounter while setting up Ignite, creating SQL Server repositories or registering SQL Server databases in Ignite PI.
All versions of DPA
Q: Using Windows Authentication but seeing login is from an untrusted domain connection errorEdit section. 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: Ensure that you can ping the SQL Server Host from the Ignite PI 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.
Several factors may cause the "connection could not be established" error. Below are the most common reasons and resolutions:
A: If you have only specified a Server and not a Server\Instance, ensure that the SQL Server instance you are trying to register is the default instance. If you are connecting to a Named Instance, enter that information in the Server field as Server\Instance. If you continue getting errors
A: If you have specified a Server\Instance, ensure that the Ignite PI Server is able to 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 Ignite 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 Ignite Registration Wizard.
Q: My SQL Server Administrator will not turn on TCP/IP for the SQL Server instance. What can I do?
A: By default, Ignite connects to SQL Server instances via TCP/IP. If the instance cannot be configured for TCP/IP connections, Ignite can be configured to connect using named pipes. Please see KB Article 5939 - Connect to SQL Server using named pipes for detailed instructions on how to enable Named Pipe connections in Ignite.
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, Ignite will not be able to connect to the SQL Server instance if the SQL Server Host is restarted without remembering to start this service manually.)
Select the Service tab to ensure that the Start Mode is set to Automatic for the SQL Server Browser, then click the Apply button:
Select the Log On tab to start the service if is stopped:
Once the service has started, select OK and return to the Ignite Registration Wizard to proceed with registration.
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: Ensure that the Server and Instance information as it was entered is correct.
A: Ensure 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 Ignite registration.(If your SQL Server Administrator will NOT allow this see how Ignite can be configured to use Named Pipes)
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, then select the IP Addresses Tab.
Once you have the TCP Dynamic Ports value, enter only the Server value NOT the Server\Instance value in the Server field of the Ignite Registration Wizard and enter the TCP Dynamic Ports value into the Port field to proceed with registration.
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:Telnet can be used 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 Ignite PI Server machine.
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 host name 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 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, Ignite PI authenticates with the Domain Controller using NTLM when using windows authentication. Please see KB article 5949 - Enable Windows Authentication Using NTLMv2 in Ignite Pl for detailed instructions on how to use NTLMv2 with Ignite PI.
Q: I am attempting to connect to our 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 Window's account credentials are not valid. Ensure that the domain and username (in format, DOMAIN\user) and password are correct and that the account is enabled and may also be successfully logged into (i.e. has not become locked out, etc.).
Q: I installed Ignite PI on a new server and now I am getting a "repository already exists in this location" error in the wizard. How do I connect to the Ignite PI repository that I already created?
A: If you have moved the Ignite PI Server but have left the repository intact on a SQL Server Instance, please see KB Article 5982 - Move DPA to another server for detailed instructions on how to move the Ignite PI Server. If you need to move the Ignite Repository (Ignite's set of tables residing on a database) see KB Article 5962 - Move a DPA repository on SQL Server
Q: Still unable to register?
A: Contact Confio support (email@example.com) with the errors you are encountering. Confio Support will gladly assist you.