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.

 All Forums
 SQL Server 2000 Forums
 SQL Server Administration (2000)
 General Network Error

Author  Topic 

rbarlow
Starting Member

26 Posts

Posted - 2009-08-26 : 13:18:38
I've run into a little interesting problem and was wondering if anybody else has encountered something like it before.

A DTS package failed this morning with the following error:

DTSRun OnError: DTSStep_DTSExecuteSQLTask_10, Error = -2147467259 (80004005)
Error string: [DBNETLIB][ConnectionWrite (WrapperWrite()).
General network error. Check your network documentation.
Error source: Microsoft OLE DB Provider for SQL Server

The package connects to 2 databases that are on the same server and executes some stored procs. The connections are both set with (local).

The support person restarted the package and it worked without a problem. I searched Google and the only thing that I found was a suggestion to use (local) or "." to connect which we already are.

russell
Pyro-ma-ni-yak

5072 Posts

Posted - 2009-08-26 : 13:45:18
it means that the package was unable to connect to the server. check the windows event logs and sql server error logs.
Go to Top of Page

rbarlow
Starting Member

26 Posts

Posted - 2009-08-26 : 15:17:24
I checked the logs and there is nothing indicating any problems.
Go to Top of Page

russell
Pyro-ma-ni-yak

5072 Posts

Posted - 2009-08-26 : 15:21:58
package and job that runs it lives on same server as databases it touches?

what MDAC version?
Go to Top of Page

rbarlow
Starting Member

26 Posts

Posted - 2009-08-26 : 16:25:03
Yup both the databases and package is on the same server. The MDAC version is 2.82.3959.0.
Go to Top of Page

russell
Pyro-ma-ni-yak

5072 Posts

Posted - 2009-08-27 : 08:44:28
And the SQL Agent job too right?

If no, then check network connectivity and event logs on client machine.

If yes, when was SQL Server last rebooted?

If this is the 1st time it's happened, I wouldn't worry much, unless it happens again. But I might restart SQL agent, or reboot the box at next maintenance window.
Go to Top of Page
   

- Advertisement -