Intermittent Connection Problem to SQL 7

[wcburton]

We have an application that connects to 3 separate SQL 7 servers. The servers are NT 4 SP 6, dual Xeon PIII and 1GB RAM. I am not sure of the SP level for SQL 7 but the full version number is 7.00.842. The servers are also running Legato Co-Standy Server to provide fault tolerance. The workstations are running XP2 SP1.

The application is scheduled to be replaced early next year so we are not looking to change anything on the servers. We do not want to risk breaking anything else to fix this. Lately I am having intermittent connection problems from only 2 of 20 workstations in one area. The connections will be working correctly and then suddenly the workstation will lose connection to only 1 of the 3 SQL servers. I can go into the ODBC config and everything is set correctly but will not connect at all. I can try changing from Multi-protocol to TCP/IP to Named Pipes but it still will not connect. I get the connection timeout while trying to contact the server. I can ping the server OK. The only thing that will get it to reconnect is to reboot the workstation.

It is difficult to test solutions because I cannot force it to happen. That also means it will be difficult to tell if anything I change has really worked. Has anyone run into this before? Any other tests I should try?

 

[Catadmin]

Check to make sure the network cables aren't loose in the box or the wall. Also make sure they aren't pinched by anything.

If the above doesn't yield results, try the following test. Shut down a working PC (one without problems), borrow its network cable, hook up the good cable to the PC with problems, boot up the PC with problems and see if it continues to have problems. Do this for both machines.

If this fixes the issue, then your solution is the inexpensive purchase of new network cables. @=) If so, run diagnostics on the network cards on both machines.



Catadmin - MCDBA, MCSA
"If a person is Microsoft Certified, does that mean that Microsoft pays the bills for the funny white jackets that tie in the back???

 

[wcburton]

I would discount the network cable because I still have connectivity to the other 2 SQL servers, can ping all 3 SQL server, and can use all other network resources. It is only the ODBC connection to the database itself that cannot be made until I reboot. It behave like something corrupt is stuck in a local buffer. It also was not the same SQL server for each PC.

Just to clarify on what I mean by intermittent:
PC #1 for a few days was about once every 1 or 2 days. This PC is in use 24/7. When it has problems, it is with SQL 2.

PC #2 I have only seen happen once. This PC is in the same 24/7 environment but is not always logged into the application as is PC #1. (The position is not always staffed.) When it had the problem, it was with SQL 3.

I may have to let this one go as a mystery since the application is due to be replaced.