Post reply

DTS failing intermittently with the error :[DBNETLIB][ConnectionWrite (send()).]General network error.

  • June 5, 2005 at 1:15 pm

    #102571

    Hi,

    DTS is failing intermittently with the error as mentioned below:

    Error: Step Error Source: Microsoft Data Transformation Services (DTS) Data Pump Step Error Description:The number of failing rows exceeds the maximum specified. (Microsoft OLE DB Provider for SQL Server (80004005): [DBNETLIB][ConnectionWrite (send()).]General network error. Check your network documentation.)

    Step Error code: 8004206A

    Step Error Help File:sqldts80.hlp

    Step Error Help Context ID:0

    Any help will be much appreciated.

    My sql server version is : SQL server 2000(sp3) --8.00.818

    --SNT

     

  • June 6, 2005 at 7:10 am

    #563175

    This was generally a problem with the input data that was being converted.

    For instance trying to push a bogus date into a "Not Null" date column.

    Are you able to re-run the process without the error? 

     

  • May 23, 2006 at 11:14 am

    #639557

    I too am having this same problem and it's happening on a series of packages that deal with different data, thus ruling out being a data problem. All this ran fine until almost a week ago and since then it's failing consistently, and I cannot rerun packages manually with any success. Thoughts?

  • November 9, 2006 at 8:08 am

    #670854

     

    I too having same problem.  When I re-run the DTS Package,No errors.

    Any solution would be greatly appreciated.

     

  • January 24, 2008 at 4:46 am

    #771210

    I am also having the same issue. But on re-run, it works perfectly fine.

    Thanks in advance!

  • February 4, 2008 at 1:52 am

    #774661

    Take a look at the following:

    http://support.microsoft.com/default.aspx?scid=kb;en-us;899599

    Maybe it is the answer that you need. The entry applies to BizTalk but the symptoms are identical - it appears to be a problem with Windows Server 2003 SP1 and SP2. I am also encountering the same problem but I have yet to try the resolution provided.

  • February 5, 2008 at 8:53 am

    #775175

    I have had similar problems with DTS, in my case I missed the real problem for a while as it was "too obvious". In my case when the error would occur it turned out the data source was not accessible, either because of network downtime, server downtime/reboots, or source data being held open by back up operations.

    It may not be the answer in your cases, but it might not hurt to check. (It helps explain why when you re-run it things work fine as well)

Viewing 7 posts - 1 through 6 (of 6 total)

You must be logged in to reply to this topic. Login to reply