Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
janelsen
Starting Member
3 Posts |
 Posted - 2005-11-28 : 18:59:29
|
| I'm new to the world of SQL and queries. There was an existing SQL server when I took the job and have been learning what I can as it comes up. My problem is that installed a new SQL server and moved everything to it. Everything seems to be working with the exception of the existing queries. I have changed the server in the ODBC Administrator but I still get the following error:Connection Failed:SQLState: 01000SQL SErer Error: 10060 & 10061[Microsoft][ODBC SQL Server Driver][TCP/IP Sockets]ConnectionOpen (Connect()).Connection Failed:SQLState: 08001SQL SErer Error: 17[Microsoft][ODBC SQL Server Driver][SQL Server does not exist or access denied.I have also checked to make sure that the server is listening for incoming sockets connections. (Port 1433) It is.I don't know if there are files (DSN) that need too be moved to the new server or if there is another place to change the server the queries are pointed to. I hope someone can help me.Thanks,Jo |
|
|
tkizer
Almighty SQL Goddess
38200 Posts |
Posted - 2005-11-28 : 19:20:07
|
| You first need to verify that SQL Server is listening on port 1433. You can do this via Server Network Utility which is located in the Microsoft SQL Server program group on the database server. You then may need to add an alias on the client machines. To do this, you click on the Network Administrator button while in the ODBC screens. Make sure to select TCP/IP and explicitly state the port of 1433 (well that's if Server Network Utility says you are listening on port 1433). You should be able to get a successful test from the ODBC screen after you are done filling out the alias. Do you get an error on the test? If you do, are you able to ping the database server from the client machine?Tara Kizeraka tduggan |
 |
|
|
janelsen
Starting Member
3 Posts |
Posted - 2005-11-28 : 19:35:14
|
| I have created the alias and the tests are successful. I can create a new query and it all works fine. But when I go and open an existing spreadsheet and ask to refresh data or edit the query I get the error I described earlier.Jo |
|
|
|
tkizer
Almighty SQL Goddess
38200 Posts |
Posted - 2005-11-28 : 19:46:11
|
| Are you sure that the application is only using ODBC? Is it possible that it is using OLE DB or ADO, which could mean that there are more connection strings to modify then just the ODBC DSN? Is there someone there who knows about the application and what needs to be configured?Tara Kizeraka tduggan |
|
|
|
janelsen
Starting Member
3 Posts |
Posted - 2005-11-29 : 19:38:12
|
| I'm pretty sure that they only ODBC. No, there's no-one here that knows what needs to be configured. There's is only one person that even knows how to create new queries.Jo |
|
|
|
tkizer
Almighty SQL Goddess
38200 Posts |
Posted - 2005-11-29 : 19:54:27
|
| It's almost impossible for us to be able to assist with this as we can't see your environment. The fact that certain things work and others don't (on the same computer) leads me to believe that you have multiple connection strings. I'm assuming you've rebooted the computer that is getting this error, otherwise we can could say that the old server is cached in memory still. When you say open an existing spreadsheet, are you referring to Excel? Or are we talking about a custom application? The only thing that I can suggest is to have your network administrator put a sniffer on the line to determine where it is trying to connect to. Outside of that, you'd need to bring someone in to help you with this.Tara Kizeraka tduggan |
|
|
|
|
|
|
New SQL server - old queries don't work