November 7, 2008 at 2:12 am
I have created a SSIS package, when I run the package the Package Execution Process reads:
The execution method succeeded but the number of errors raised (1) reseached the maximum allowed
imumErrorCount: Change the MaximumErrorCount or fix the error
1. How do I increase the MaximumErrorCount
2. where can i find out what the error is?
Thanks
November 7, 2008 at 5:19 am
You need to look at the rest of the output. The line you quoted comes at the very end of the output.
When I'm running in Debug mode via BIDS, I usually cut-n-paste the output to notepad then do a search for "Error:", which takes me to the first error. Usually the step / container name is included at the very start of the error messages.
To increase your maximum error count, you need to do the following:
In the Properties window, under Execution, every task has "Maximum Error Count". You change that from 1 to whatever value you wish. 1 is the default. I usually don't change this number because I want my package to bomb on errors rather than throw bad data in the DB.
Also, make sure to change this value on the Package level. If you change it only on the task level and not on the package level, it'll still bomb the package on the very first error. The property is hiding in the same place.
March 9, 2010 at 7:12 am
Hi
I got the same error in my master package but the underlying package executed without any errors....
I mean the EXCUTE PACKAGE TASK WENT RED(Error)
but the package that it was executing was fine (no errors)
Warning: 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.
Why is this happening even though I am not getting any errors...?
Can anyone explain me what exactly is the error......
Tahnks in advance
Thanks [/font]
March 9, 2010 at 7:59 am
Are that the only errors that you receive?
If the Execute Package went red, that there must be some sort of error that would explain why it has failed.
Need an answer? No, you need a question
My blog at https://sqlkover.com.
MCSE Business Intelligence - Microsoft Data Platform MVP
March 9, 2010 at 10:12 am
cRuchika,
FYI: I can't see whatever you posted in the scroll box.
Regarding a failed package but everything looks green or yellow? I've seen it before when a package has a task with multiple steps in it or a container with multiple lines of processing. The first error will error out the package, but the processes are still rolling back the rest of the tasks, so you won't necessarily see the specific task as highlighted red.
Example 1: A Data Flow Task has multiple, simultaneous, transformations happening. It only takes one to fail the package, but the rest of them still have to roll back before the SSIS package fails the DFT step.
Example 2: Task one branches off into three different other tasks with precendence contraints that allows for multiple simultaneous processing.
Example 3: Multiple containers run simultaneously.
In all of these scenarios, the key is that the package is still trying to run something when the failure occurs. The only ways to deal with it is to wait, stop the package when it fails (but still thinks its running) and locate the task / transformation in question, or disable various tasks / containers and re-run until you find the specific problem child.
March 9, 2010 at 1:26 pm
yes, this is the only error I am getting..
The execute package task is failing but as I am running directly the package I can clearly see that the underlying package that the EXECUTE packg TASK is running is running FINE and ALL GREEN...
Here is the error:
Warning: 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
I am not sure what is going wrong in this package...
Thanks [/font]
March 10, 2010 at 5:10 am
As I said, it sounds like the package hasn't "completed" when you're seeing the failure.
Can you attach a screen shot of the package when it's failed? I might be able to tell you where to disable tasks or such so you can track down the error.
November 18, 2011 at 2:34 pm
I just happen to receive the same error.
In my SSIS code, I had script task and I set the result to failure inside my C# code, when a variable failed on my validation. Testing the failure caused the DTEXEC to throw an error and I change the logic to always set to success then I do not see this error anymore. But, I created a variable myself and set the value to 0 if it is successful or 1 to failure. Later I use the variable to branch out the SSIS tasks.
June 13, 2012 at 5:21 am
in response to your second question 2. where can i find out what the error is?
I usually check the Output, do a crtl+f for error. I had a similar error when executing a child package. The package output indicated I had password issues (even though I knew I'd entered these correctly!). Turns out I had to reset the package password on the execute package task to resolve this. hope this helps!
June 13, 2012 at 5:28 am
ColdSurfer76, you might want to check the dates on threads like this before you respond. This thread is over 2 years old and the OP didn't respond to the last few posts, so I doubt (s)he cares about any further information at this point. (s)he either figured the problem out long ago, or didn't.
Viewing 10 posts - 1 through 9 (of 9 total)
You must be logged in to reply to this topic. Login to reply