xtross
asked on
SQL Error 53 and 17
Connection failed:
SQLState: '01000'
SQL Server Error: 53
[Microssoft][ODBC SQLServer Driver][Named Pipes]Connection Open
(Connect()).
Connection failed:
SQLState: '08001'
SQL Server Error: 17
[Microssoft][ODBC SQLServer Driver][Named Pipes]SQL Server does not
exist or access denied.
We have an application here that was developed by a vendor but some how has become an in house app. The app team does not really support the app other than knowing what files are needed for it to run. As far as I can tell the last time an update was made to the application was back in 2001.
Some of the people running the app are getting the above error. Some are able to use the application with no problems. All of these people are using the same image. I have gone through the DSNs, dlls, and all recently deployed MS patches on one of the PCs where the application does not work. Basically what I have found is that any new instance of the application does not work. I even imaged a PC with an older image where I know the application worked. It did not. I have tried moving the PC to different subnets. I just can't figure out why any new instance of the application does not work. The server team tells me nothing has changed on their end.
SQLState: '01000'
SQL Server Error: 53
[Microssoft][ODBC SQLServer Driver][Named Pipes]Connection Open
(Connect()).
Connection failed:
SQLState: '08001'
SQL Server Error: 17
[Microssoft][ODBC SQLServer Driver][Named Pipes]SQL Server does not
exist or access denied.
We have an application here that was developed by a vendor but some how has become an in house app. The app team does not really support the app other than knowing what files are needed for it to run. As far as I can tell the last time an update was made to the application was back in 2001.
Some of the people running the app are getting the above error. Some are able to use the application with no problems. All of these people are using the same image. I have gone through the DSNs, dlls, and all recently deployed MS patches on one of the PCs where the application does not work. Basically what I have found is that any new instance of the application does not work. I even imaged a PC with an older image where I know the application worked. It did not. I have tried moving the PC to different subnets. I just can't figure out why any new instance of the application does not work. The server team tells me nothing has changed on their end.
Try setting the connection library in the DSN to TCP/IP rather than named pipes
ASKER
Tried TCP/IP same error.
Connection failed:
SQLState: '01000'
SQL Server Error: 53
[Microssoft][ODBC SQLServer Driver][DBNETLIB]Connectio
(Connect()).
Connection failed:
SQLState: '08001'
SQL Server Error: 17
[Microssoft][ODBC SQLServer Driver][DBNETLIB]SQL Server does not
exist or access denied.
I have also verified that there are available connections.
Connection failed:
SQLState: '01000'
SQL Server Error: 53
[Microssoft][ODBC SQLServer Driver][DBNETLIB]Connectio
(Connect()).
Connection failed:
SQLState: '08001'
SQL Server Error: 17
[Microssoft][ODBC SQLServer Driver][DBNETLIB]SQL Server does not
exist or access denied.
I have also verified that there are available connections.
1) Make sure there is not an alias in the SQL Server Client Connection dialog alias tab on the working machines. If there is, you might add same to a new machine.
2) Look at c:\WINDOWS\system32\driver
3) Can you connect to the server with Query Analyzer from the new machines?
4) Can you ping the server by both IP and name from the new machines?
2) Look at c:\WINDOWS\system32\driver
3) Can you connect to the server with Query Analyzer from the new machines?
4) Can you ping the server by both IP and name from the new machines?
ASKER
1) Where is this tab?
2) No entry in the host file for either SQL server (read below for "either" explaination)
3) Sorry I don't know Query Analyzer. Seperate application?
4) I can ping by both.
Here is how the application seems to work from just looking at the front end.
A GUI opens that has basicly 3 main fields. The top field is AccessDatabase.mdb. Then then next two are data sources. SQL-Source1 and SQL-Source2. AccessDatabase.mdb is always the same. SQL-Source1 and SQL-Source2 can be picked from a pick list. Both SQL sources have DSNs that I have checked and tested about a million times. Clicking the open button produces the error after about 30 seconds.
After clicking OK a SQL server login box appears. I can try the login here but get the same 53 & 17 error. So I just click cancel. Get another error message: Unable to create link to table "AppAccount" (Action cancled by user). Click OK and get another error: Error linking in App tables. After that I am back to the main GUI.
It does not matter what SQL sources I pick. I have about five to pick from in each list.
Should I be focusing on the Access part more?
2) No entry in the host file for either SQL server (read below for "either" explaination)
3) Sorry I don't know Query Analyzer. Seperate application?
4) I can ping by both.
Here is how the application seems to work from just looking at the front end.
A GUI opens that has basicly 3 main fields. The top field is AccessDatabase.mdb. Then then next two are data sources. SQL-Source1 and SQL-Source2. AccessDatabase.mdb is always the same. SQL-Source1 and SQL-Source2 can be picked from a pick list. Both SQL sources have DSNs that I have checked and tested about a million times. Clicking the open button produces the error after about 30 seconds.
After clicking OK a SQL server login box appears. I can try the login here but get the same 53 & 17 error. So I just click cancel. Get another error message: Unable to create link to table "AppAccount" (Action cancled by user). Click OK and get another error: Error linking in App tables. After that I am back to the main GUI.
It does not matter what SQL sources I pick. I have about five to pick from in each list.
Should I be focusing on the Access part more?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
I changed the protocol in the DSN. On the second window there is a client configuration button.
I will check the other items now and repost soon.
I will check the other items now and repost soon.
ASKER
It was an ODBC setting. The people that develop the app checked the settings before I received the ticket. I checked the settings but only against documentation given to me by the application team. Yesterday I checked all the ODBC settings against the PC where the application is working. One setting was set to Server21 when it should have been Server18.
ASKER
Thank You for your help