SQL Server Forums
Profile | Register | Active Topics | Members | Search | Forum FAQ
 
Register Now and get your question answered!
Username:
Password:
Save Password
Forgot your Password?

 All Forums
 SQL Server 2008 Forums
 SSIS and Import/Export (2008)
 Maximum Error Count Reached - Stumped!
 New Topic  Reply to Topic
 Printer Friendly
Author Previous Topic Topic Next Topic  

Grifter
Posting Yak Master

214 Posts

Posted - 08/10/2012 :  10:27:54  Show Profile  Reply with Quote
I have a script task in my SSIS that has been ok and now it keeps failing when I run it as part of the package, if I run it seperately it is fine.

If I put a break point in code it goes right through and out the code then fails. Not done anything to it, been working on other parts of the system.

I tried putting maximum error count to 2,then 10 then 100 and it still fails but not telling me what on and the code isn't going into err handler.

quote:
SSIS package "Package.dtsx" starting.
Error: 0x8 at Check if to run: The script returned a failure result.
Task failed: Check if to run
Warning: 0x80019002 at Package: SSIS Warning Code DTS_W_MAXIMUMERRORCOUNTREACHED. The Execution method succeeded, but the number of errors raised (1) reached the maximum allowed (1); resulting in failure. This occurs when the number of errors reaches the number specified in MaximumErrorCount. Change the MaximumErrorCount or fix the errors.
SSIS package "CD_Replication.dtsx" finished: Failure.


How can I find out what is causing this?

Thanks

G

Edited by - Grifter on 08/10/2012 10:29:21

visakh16
Very Important crosS Applying yaK Herder

India
47099 Posts

Posted - 08/10/2012 :  10:46:45  Show Profile  Reply with Quote
have you upgraded your db version recently?

------------------------------------------------------------------------------------------------------
SQL Server MVP
http://visakhm.blogspot.com/

Go to Top of Page

Grifter
Posting Yak Master

214 Posts

Posted - 08/10/2012 :  10:55:08  Show Profile  Reply with Quote
I'm not aware of anything being updated
Go to Top of Page

Grifter
Posting Yak Master

214 Posts

Posted - 08/10/2012 :  11:03:42  Show Profile  Reply with Quote
Ok I got it, we have a table in the DB the script task sets to 1, and this value is set at the end of the package back to 0, I must have interrupted the package run and left it set to 1 then when it re ran it went into a ScriptResults.Failure when the script task checked the value. However we have a task to handle this although it doesn't reset the DB value back to 0 - I think that needs to be included.

Thanks for any input anyway

G
Go to Top of Page

visakh16
Very Important crosS Applying yaK Herder

India
47099 Posts

Posted - 08/10/2012 :  11:04:58  Show Profile  Reply with Quote
do you've any other error in error log? is this happening only when its executed from job or is it happening even when running in BIDS?

------------------------------------------------------------------------------------------------------
SQL Server MVP
http://visakhm.blogspot.com/

Go to Top of Page
  Previous Topic Topic Next Topic  
 New Topic  Reply to Topic
 Printer Friendly
Jump To:
SQL Server Forums © 2000-2009 SQLTeam Publishing, LLC Go To Top Of Page
This page was generated in 0.05 seconds. Powered By: Snitz Forums 2000