Error: number of failing rows exceeds the maximum

  • I searched for a similar problem on this site and found one that had a near identical error in it. However that error was not the focus for the responses and so I am posting here to try and get more details on this error:

    Step 'DTSStep_DTSDataPumpTask_4' failed

    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

    Step Execution Started: 9/13/2002 3:26:25 AM

    Step Execution Completed: 9/13/2002 3:32:59 AM

    Total Step Execution Time: 393.812 seconds

    Progress count in Step: 0

    The above is the error we got in our DTS log file. It is a simple data pump and only started failing yesterday morning and now it failed this morning.

    Is there a way to increase this maximum thresh hold? Or is this related to a network connectivity problem?

    Let me provide some more details about the problem:

    All the servers involved are SQL Server 2000 and I think they are all running on Windows 2000. We have 3 clustered servers that are nearly identical and the section that fails has identical structures on all three servers. So we have 3 identical DTS packages, one that pumps the data to server 1, another for server 2, and another for server 3. The DTS package runs on a seperate server that is dedicated to DTS packages. The DTS server is at our office. All 3 cluster servers are off site. All trafic between the DTS server and the cluster servers travels across one T1 line. All three cluster DTS packages run simultaneously. Only the one for server 3 fails. The other two succeed. All of them were succeeding prior to 2 days ago. The only major known change is that the DTS server was upgraded from Windows NT to Windows 2000 2 days ago.

    Hopefully this is enough information to help you see our problem and to give me suggestions on what to do to fix it.

    Robert Marda

    SQL Server will deliver its data any way you want it

    when you give your SQL Programmer enough developing time.

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

  • Hey Robert

    The key is your statement here.

    quote:


    The number of failing rows exceeds the maximum specified.


    Have you looked at the detail or just that it failed. And have you tried execution by hand?

    It will usually containt the reson for fialures or you can generate a log for the DTS package. Look however like you have invalid data try to import and may need to do a sanity check and clean on the remote data before transformation.

    If however you know there will be errors you can set the maximum threshold by opening the package and on the package option of the toolbar choose properties. On one of the tabs you will find maximum errors and logging. Adjust to your needs.

    "Don't roll your eyes at me. I will tape them in place." (Teacher on Boston Public)

  • I guess I needed to provide more information and yes I feel like needing a sanity check after having sleepless nights the past 3 days.

    When I run this package manually it does not fail. There is no data in the destination table since the table is created prior to the import. The source data does not cause the identical packages for server 1 and server 2 to fail, they succeed. If there was an issue with the data I would expect all three to fail not just one.

    I am going to try increasing the maximum rows that can fail. If I increas the maximum rows that can fail to the total number of rows possible then even if no rows qualify the package would continue? The reason I can afford to do this is I have a step that fires after this one that checks to ensure the tables are not empty and if one is empty then it stops the package. But if even one row goes in I want to see it, this would be my only way of seeing anything different than I am now seeing.

    Robert Marda

    SQL Server will deliver its data any way you want it

    when you give your SQL Programmer enough developing time.

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

  • Can you dummy up some data that you know will not fail? If so, and the package still fails, I would think you could safely rule out a data integrity issue...at least that removes one variable from the picture!

    Michael Weiss


    Michael Weiss

  • I could do that. I think the best way to do that would be to reduce the number of rows. As far as I know they should all succeed. Usually there are about 770,000+ rows to be moved in the one table and 300,000+ rows in the other were I have seen the failure. Unfortunately, I can't run this package dudring normal business hours which makes it hard to do a lot of testing.

    Robert Marda

    SQL Server will deliver its data any way you want it

    when you give your SQL Programmer enough developing time.

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

  • I'll have to check that. Thanks!

    Robert Marda

    SQL Server will deliver its data any way you want it

    when you give your SQL Programmer enough developing time.

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

  • Antares,

    Perhaps I am too tired, but I can't find where to adjust the maximum rows allowed for failure. I looked on the general, globalvariables, logging, and advanced tabs and couldn't see anything that would let me make that change.

    Robert Marda

    SQL Server will deliver its data any way you want it

    when you give your SQL Programmer enough developing time.

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

  • it is the max error count of the options tab of the Transformation properties. I actually had this error while doing some activeX script testing over the weekend. I just do not recall what the solution was.

  • I did receive this error today. But not sure where can i specify or change the maximum value. Can you please help ?

    In Properties option from toolbar, i found General, Global Variables, Logging, Advanced. But don't have any option to change this max value. Correct me if i am wrong. We are new to this kind of error.

    Thank you.

    Step 'DTSStep_DTSDataPumpTask_1' failed

    Step Error Source: Microsoft Data Transformation Services (DTS) Data Pump

    Step Error Description:The number of failing rows exceeds the maximum specified. (Microsoft JET Database Engine (80004005): Invalid argument.)

    Step Error code: 8004206A

    Step Error Help File:sqldts80.hlp

    Step Error Help Context ID:0

Viewing 9 posts - 1 through 8 (of 8 total)

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