| Author |
 Topic  |
|
|
bechbd
Starting Member
7 Posts |
 Posted - 02/04/2004 : 10:53:41
|
I was wondering if anyone knew what the would cause the following error messages? These are on a remote server that is connecting to the SQL machine via ODBC. The SQL machine is running SQL Server 2000 SP3 and the Application machine is running MDAC 2.7 with named pipes and TCP/IP configured. These errors occur randomly but consistantly. The program still connects and works most of the time but these error messages appear on a regular basis. Does anyone have any idea what to try?
The VB Application identified by the event source logged this Application Process Scheduler: Thread ID: 1308 ,Logged: 7008 - ActiveModule-GetPrimaryRunDetailsTable -
vbError # 40002-01000: [Microsoft][ODBC SQL Server Driver][TCP/IP Sockets]ConnectionOpen (Connect()).
rdoError # 10060-01000: [Microsoft][ODBC SQL Server Driver][TCP/IP Sockets]ConnectionOpen (Connect()).
rdoError # 17-08001: [Microsoft][ODBC SQL Server Driver][TCP/IP Sockets]SQL Server does not exist or access denied.
|
|
|
tkizer
Almighty SQL Goddess
USA
28518 Posts |
Posted - 02/04/2004 : 12:49:48
|
The last error that you posted means that the client is unable to find the SQL Server by either the IP address or server name. Are you experiencing network problems during these times? Is the SQL Server restarting during these times? I would take a look at the network and the SQL Server Error log to figure out what is happening.
Tara |
 |
|
|
bechbd
Starting Member
7 Posts |
Posted - 02/05/2004 : 09:41:37
|
I took a look at the network and SQL logs and there does not appear to be anything out of the ordinary.
BTW: This error originally started occurring when the patch was applied to the serve to fix the slammer worm. Don't know if that matters just figured I throw that out there as well.
|
|
|
|
tkizer
Almighty SQL Goddess
USA
28518 Posts |
Posted - 02/05/2004 : 12:23:46
|
I would suggest running SQL Profiler to see what is occurring on the SQL Server.
Tara |
|
|
|
bechbd
Starting Member
7 Posts |
Posted - 02/05/2004 : 15:52:40
|
| I am sorry I am asking such newbie questions, but what exactly should I be looking for? I have done network traffic monitoring, performance monitoring on the SQL server, and performance and network monitoring on the application machine. With the exception of the performance monitoring on the SQL machine I have not seen anything out of the ordinary. On the SQL machine I tracked sql optimum memory required vs available memory and it appears that the server is running below the optimum but I can't convince anyone to buy sdome unless I can prove that this will solve the problem. |
|
|
|
tkizer
Almighty SQL Goddess
USA
28518 Posts |
Posted - 02/05/2004 : 16:25:34
|
SQL Profiler shows what transactions are running inside SQL Server.
Does the SQL Server Error Log show anyone killing transactions? Does it show if the service has been restarted? For kills, you'll see the a message like SPID 52 killed by tduggan. For restarts, you look at the date and time on the Error Log. As long as no one has cycled the error log, the date and time of when the Log was created will match with a restart of the service of a reboot of the server.
RAM isn't going to help this situation. To check if SQL Server has enough memory, you compare the Target and Total memory in the SQL Server:Memory manager counter.
"SQL Server does not exist or access denied" can mean that the SQL Server service is stopped. It can also mean that the client can't connect to the SQL Server through TCP/IP due to a network problem. The error can appear in lots of different scenarios.
Tara |
|
|
|
bechbd
Starting Member
7 Posts |
Posted - 02/05/2004 : 18:18:53
|
The SQL server log does not show any sort of killed transactions or service restarts that correspond to any of the times that the errors occur. The only thing in the logs for a day that had ~56 errors was:
2004-01-28 02:00:05.28 backup Database backed up: Database: master, creation date(time): 2004/01/27(17:13:06)
2004-01-28 02:00:05.81 backup Database backed up: Database: model, creation date(time): 2000/08/06(01:40:52),
2004-01-28 02:00:06.57 backup Database backed up: Database: msdb, creation date(time): 2000/08/06(01:40:56),
2004-01-28 08:27:54.20 spid55 Configuration option 'show advanced options' changed from 1 to 1. Run the RECON
2004-01-28 08:27:54.20 spid55 Error: 15457, Severity: 0, State: 1
2004-01-28 08:27:54.59 spid55 Using 'xplog70.dll' version '2000.80.760' to execute extended stored procedure
2004-01-28 12:00:13.68 backup Log backed up: Database: XXXXXX, creation date(time): 2002/04/25(14:33:33), f
2004-01-28 12:00:17.35 backup Log backed up: Database: XXXXXX_beta, creation date(time): 2002/04/25(11:08:3
2004-01-28 13:19:32.74 spid54 DBCC TRACEON 208, server process ID (SPID) 54.
2004-01-28 13:19:33.02 spid55 DBCC TRACEON 208, server process ID (SPID) 55.
2004-01-28 13:23:02.68 spid55 DBCC TRACEON 208, server process ID (SPID) 55.
2004-01-28 18:03:25.20 backup Database backed up: Database: EFLEXION, creation date(time): 2002/04/25(14:33:3
2004-01-28 18:04:25.27 backup Database backed up: Database: Eflexion_beta, creation date(time): 2002/04/25(11
2004-01-29 02:00:04.07 backup Database backed up: Database: master, creation date(time): 2004/01/27(17:13:06)
2004-01-29 02:00:05.01 backup Database backed up: Database: model, creation date(time): 2000/08/06(01:40:52),
2004-01-29 02:00:06.23 backup Database backed up: Database: msdb, creation date(time): 2000/08/06(01:40:56),
2004-01-29 12:00:10.61 backup Log backed up: Database: XXXXX, creation date(time): 2002/04/25(14:33:33), f
2004-01-29 12:00:13.10 backup Log backed up: Database: XXXXX_beta, creation date(time): 2002/04/25(11:08:3)
The target vs total memory waswhat I had run to get those results, I just couldn't remember the name. Thank you very much for helping me. I am not a DBA and have no training in this sort of thing so your help is very much appreciated. |
|
|
|
tkizer
Almighty SQL Goddess
USA
28518 Posts |
Posted - 02/05/2004 : 18:27:23
|
Since the error log doesn't show KILLs or a restart, the problem is most likely outside of SQL Server. A network sniffer should be run to determine what is occurring on the network. The SQL Server box probably can't even be pinged from the client when the error occurs.
You mentioned that the error started after the patch was installed due to the slammer worm. Have you installed service pack 3a? The patch was to fix service pack 2. Service pack 3 has been released since then, and then service pack 3a was created to fix problems in service pack 3.
Tara |
|
|
|
bechbd
Starting Member
7 Posts |
Posted - 02/06/2004 : 09:36:05
|
| Yes, Service Pack 3a was installed on SQL server and MDAC 2.7 was installed on the application machine. |
|
|
|
banksy
Starting Member
USA
2 Posts |
Posted - 02/06/2004 : 10:32:56
|
I would try installing the SQL Desktop Utilities and then configuring the TCP/IP connector. Also, can you ping the SQL Server by name as well as IP? Perhaps you ahve a bad hosts file?
-----------------------
Terry Banks
Sr. Tech Support Analyst
Merge eFilm |
|
|
|
tkizer
Almighty SQL Goddess
USA
28518 Posts |
Posted - 02/06/2004 : 12:18:51
|
I'm not sure what the point of installing the SQL client tools is. Configuring the TCP/IP connector is the same thing as creating an alias. You don't need the tools to do this. It can be done from the registry. But the fact that it works some of the time means that an alias isn't going to help anyway.
Tara |
|
|
|
Scott W
Starting Member
3 Posts |
Posted - 02/09/2004 : 22:55:29
|
I am having the exact same problem... before the windows update patch, could connect through my web apps, now I can't. Interestingly, I can connect through EM from any other system with no problems. But the web applications attempting to connect can no longer connect.
I have checked my hosts file(s), the login account in question, the db's in question (more than one, depending on the web app). |
Edited by - Scott W on 02/09/2004 22:56:56 |
|
|
|
Scott W
Starting Member
3 Posts |
Posted - 02/09/2004 : 23:36:20
|
Well, I downloaded and installed sql2k's SP3a and now all is apparently well... hope someone else who gets bit by this finds this thread.  |
|
|
| |
Topic |
|
TCP/IP Sockets error
Forum Locked
