Need Help Please with General Network Error!

[jsql12]

Hello,

I get the following error when executing some stored procs in one of the client servers.

[Microsoft][ODBC SQL Server Driver][TCP/IP Sockets]ConnectionCheck ForData (CheckforData())

The stored procs actually reside on a different server, which I have registered in my EM. I can ping the remote server, the NIC speed is set to 100 MB Full on both servers, the MDAC on both servers is 2.71, and both servers have SQL server 2000 SP3 installed.

I don't know what's causing this issue, but your help would be greatly appreciated.

Thank you all!

 

[mrdenny]

Does this happen when you first try to run the procedure or part way through the procedure? Does it happen every time or just some times? How are you running the procedure?

Denny
MCSA (2003) / MCDBA (SQL 2000)
MCTS (SQL 2005 / Microsoft Windows SharePoint Services 3.0: Configuration / Microsoft Office SharePoint Server 2007: Configuration)
MCITP Database Administrator (SQL 2005) / Database Developer (SQL 2005)

My Blog

 

[jsql12]

Thank you Denny for your quick response!

The Stored procs are part of a DTS package that we execute every night. The DTS has been running for years without any issues. Recently, since last week, we started getting these errors consistently and I found out that the step that fails is the one where the stored procs are executed. So I tried to execute the SPs manually in query analyzer but I got the same error that I described previously. To my knowledge, we didn't change any network configuration. The only thing that we did is to patch our servers with the regular server patches as we've been doing for years.

Thanks again!

 

[mrdenny]

When you run the procedure manually it should tell you what line it's failing on. Can you post that statement that it's failing on?

Denny
MCSA (2003) / MCDBA (SQL 2000)
MCTS (SQL 2005 / Microsoft Windows SharePoint Services 3.0: Configuration / Microsoft Office SharePoint Server 2007: Configuration)
MCITP Database Administrator (SQL 2005) / Database Developer (SQL 2005)

My Blog

 

[SQLSister]

I'd check to make sure you still have a linked server set up. Maybe one of the patches accidentally did away with this.

"NOTHING is more important in a database than integrity." ESquared

 

[Crowley16]

yeah, I always try to keep any automatic patches/updates off production servers, they can cause all sorts of strange problems...

I would do what's already been mentioned, plus check for permissions on the 2 servers, user accounts and also try to fire off a simple select query to the other server just to make sure it's not a connection problem...

--------------------
Procrastinate Now!