For more than a year the scheduled (every 25min) Job below worked fine
without any problems. Now it doesn't anymore and can't define why.
The SO is Win 2K3 Server SP1 with SQL Server 2000 SP3. I've installed SP4
and still not working.

There is no need to update this PC cause it is on a industrial enviroment.
What the procedure on the Job below does is to tranfer data from the linked
server to a resident Database table.
Here's the Job:

exec sp_addlinkedserver @srvproduct = 'HistoricalFix', @server =
'HistoricalFix', @provider = 'MSDASQL', @datasrc = 'FIX Dynamics Historical
Data'
exec TransferToDatabase
exec sp_dropserver @server = 'HistoricalFix', @droplogins = 'droplogins'

When i run this i got the error:

[Microsoft][ODBC SQL Server Driver][Shared Memory]ConnectionCheckForData
(CheckforData()).
Server: Msg 11, Level 16, State 1, Line 0
General network error. Check your network documentation.

Connection Broken

Need some help here.
Thnks in advance

Can you ping the server?

--
Arnie Rowland, Ph.D.
Westwood Consulting, Inc

Most good judgment comes from experience.
Most experience comes from bad judgment.
- Anonymous

You can't help someone get up a hill without getting a little closer to the
top yourself.
- H. Norman Schwarzkopf


"PG" <PG (AT) discussions (DOT) microsoft.com> wrote

Yes i can!
This all about one machine only (Local Server).
I've tried to replicate this problem on a Virtual System but it worked fine.
I could import the values from the linked server (This linked server still be
on local machine. An external application.) to the SQL Server database table.

I've figured out that the system suffered some power failures (the UPS
wasn't installed yet), could this be the reason so the SQL Job stopped work?

In the case of the external application (a SCADA application), i've realised
that some files were missing due to those power failures. Something like
this could be happening with SQL Server ? (but i don't have any errors about
faulting files).


Thanks in advance!

"Arnie Rowland" wrote: