Post reply

DTS - General Network Error

  • September 29, 2003 at 8:01 am

    #176727

    Getting the following message in the DTS package log when running one specific DTS package out of 400+ DTS packages. It causes the package step to fail.

    ----

    Step Error Source: Microsoft OLE DB Provider for SQL Server

    Step Error Description:[DBNETLIB][ConnectionRead (recv()).]General network error. Check your network documentation.

    Step Error code: 80004005

    Step Error Help File:

    Step Error Help Context ID:0

    ----

    Any ideas about what could be happening? There are no corresponding Event log entries and this issue does not occur with the other 400+ DTS packages that we run (some before, some after, some at the same time). I would think if it was truly a network error then the other packages running at the same time would fail.

  • September 29, 2003 at 8:47 am

    #476224

    I have seen errors like this when I knew there shouldn't be a problem with connectivity. My advice to you is to try executing the task that is failing in the DTS package. If you get an error there then move the code inside the task to Query Analyzer (unless it is an ActiveX script) and execute it there. If you get a similar error then start remarking out lines of code until the error goes away, then you should be able to analyze table structure, indexes, triggers, etc to determine why that part of the code gives you problems.

    That is the best I can suggest without more details.

    Robert W. Marda

    SQL Programmer

    bigdough.com

    The world’s leading capital markets contact database and software platform.

    Robert W. Marda
    Billing and OSS Specialist - SQL Programmer
    MCL Systems

  • September 29, 2003 at 12:48 pm

    #476258

    Sorry, should have added that running the problem task in Query Analyser does not cause the problem to occur.

  • September 29, 2003 at 5:34 pm

    #476283

    Do you have package logging enabled? What is the step that's failing? Also, you mentioned this is one of 400+ packages. What sort of workflow is there between these packages? Is it possibel that another package is clashing with the one that fails?

    Hope this helps

    Phill Carter

    --------------------

    Colt 45 - the original point and click interface

    Edited by - phillcart on 09/29/2003 5:35:49 PM

    --------------------
    Colt 45 - the original point and click interface

  • September 30, 2003 at 9:40 am

    #476399

    This kind of error is generally encountered when the DTS has been develped on some other Server and then Copied to the new server.

    The properties of the associated databases referencing other connection do not get corrected.

    I will recommend you go in the DTS package and right click the properties of the SQL severs(a box like icon) check up that the linking severs are properly connected. If not go the security tab on the Enterprise manager and add the SQL server in the linked servers to which the connection is being referenced to

    Hope it helps

Viewing 5 posts - 1 through 4 (of 4 total)

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