Troubleshooting: Server Does Not Exist / Access Denied

Issue

When you try to create a DSN to connect a workstation to a ProFicient SQL database, one of the following errors opens:

• Example 1:

  Connection failed: SQLState: '01000' SQL SQL Server Error: 231 (or Error: 10061) [Microsoft][ODBC SQL Server Driver][Named Pipes]Open (Connect()). Connection failed; SQL State: '08001' SQL Server Error: 17 [Microsoft][ODBC SQL Server Driver][Named Pipes] or [TCP/IP Sockets] SQL Server does not exist or access denied.

• Example 2:

  Connection failed: SQLState: '01000' SQL SQL Server Error: 67 (or Error: 53)[Microsoft][ODBC SQL Server Driver][DBNETLIB]ConnectionOpen Connect())) Connection failed: SQL State: '08001' SQL Server Error: 17 [Microsoft][ODBC SQL Server Driver][DBNETLIB] SQL Server does not exist or access denied.

• Example 3:

  Connection failed: SQLState: '01000' SQL SQL Server Error: 11001 [Microsoft][ODBC SQL Server Driver][DBNETLIB]ConnectionOpen Connect())) Connection failed: SQL State: '08001' SQL Server Error: 6 [Microsoft][ODBC SQL Server Driver][DBNETLIB] SQL Server not found.

• Example 4:

  Connection failed: SQL State: '01000' SQL SQL Server Error: 0 [Microsoft][ODBC SQL Server Driver][DBNETLIB]ConnectionOpen (SECCreateCredentials()) Connection failed: SQL State: '08001'SQL Server Error: 18 [Microsoft][ODBC SQL Server Driver][DBNETLIB] SSL Security Error.

• Example 5: Reported on all database management systems, including Oracle and SQL

  Database Error DATABASE CONNECTION FAILED! An attempt to re-establish connection will be tried. Please retry operation. Login failed. The login is from an untrusted domain and cannot be used with Windows authentication. - 28000 Module: OpenDataSource.

• Example 6: Logged by DCS

  Database Not Accessible...... Try #2 - will retry in 6 seconds. Save - Retry.

• Example 7: Attempting DSN creation following ProFicient Advanced installation

  [Microsoft][ODBC Driver Manager] Data source name not found and no default driver specified - IM002

Possible Root Causes

• The network connection to ProFicient data is skipped or unavailable. For SQL connection errors, you have not enabled SQL remote connections.
• You did not open firewall port 1433.
• You did not configure the SQL ServerBrowser.
• You did not enable TCP/IP.
• The ODBC Pass-Through is incorrect or missing. In this example, the combination of user DSN and incorrect pass-through caused the error.
• An SSL security error indicated an issue with network and domain permissions. SSL is an encryption type configured in the database management system (for example, SQL) and the ODBC connection.

Troubleshooting (Standard)

1. Remove the extra user DSN and fix the incorrect ODBC Pass-Through. For more information, please see Using ODBC Pass-Through.
2. Restart the server.
3. Enable SQL remote connections.
4. Open firewall port 1433.
5. Configure the SQL ServerBrowser.
6. Enable TCP/IP.
7. Switch from the SQL Server driver to the SQL Native Client.

Troubleshooting (DCS)

1. Configure DCS to log on as a domain admin account. For more information, please see Service Accounts.
2. Add the Windows domain as a local administrator on the server.
3. Restart the server.