June 14, 2010 at 5:56 pm
My Transaction Log backup has 'MaximumErrorCount' error as below:
SSIS Warning Code DTS_W_MAXIMUMERRORCOUNTREACHED. The Execution method succeeded, but the number of errors raised (%1!d!) reached the maximum allowed (%2!d!); resulting in failure. This occurs when the number of errors reaches the number specified in MaximumErrorCount. Change the MaximumErrorCount or fix the errors.
Question: How to get or reset this maximum number before DtsContainer stops running?
Thanks
June 14, 2010 at 7:00 pm
Instead of looking at the agent job history, you need to be looking in the maintenance plan history. Open the maintenance plan folder in Object Explorer, right-click on your maintenance plan and View History.
Find the task in that maintenance plan that failed and review the message. That message will identify why the task failed and should help you fix the problem. If you still have issues, post that message here and we'll see if we can help you.
Jeffrey Williams
“We are all faced with a series of great opportunities brilliantly disguised as impossible situations.”
― Charles R. Swindoll
How to post questions to get better answers faster
Managing Transaction Logs
June 14, 2010 at 7:30 pm
Sorry, Job was run on SQL Server 2008, not 2005 as indicated earlier. Message from Job History is as following:
Executed as user: SCCGOV\sqlagent. Microsoft (R) SQL Server Execute Package Utility Version 10.0.2531.0 for 64-bit Copyright (C) Microsoft Corp 1984-2005. All rights reserved. Started: 8:00:02 PM Error: 2010-06-12 20:00:36.15 Code: 0xC00291EC Source: {3A069612-C02A-44B5-94D5-DBB8D3DF2DCD} Execute SQL Task Description: Failed to acquire connection "Local server connection". Connection may not be configured correctly or you may not have the right permissions on this connection. End Error Warning: 2010-06-12 20:00:36.17 Code: 0x80019002 Source: OnPreExecute Description: 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. End Warning Error: 2010-06-12 20:00:52.55 Code: 0xC0024104 Source: Back Up Database Task Description: The Execute method on the task returned error code 0x80131904 (A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server)). The Execute method must succeed, and indicate the result using an "out" parameter. End Error Error: 2010-06-12 20:01:08.56 Code: 0xC0024104 Source: Notify Operator Task Description: The Execute method on the task returned error code 0x80131904 (A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server)). The Execute method must succeed, and indicate the result using an "out" parameter. End Error Error: 2010-06-12 20:01:23.60 Code: 0xC0024104 Source: {C5EE17C7-FFA2-4974-A08F-D9D5178075D3} Description: The Execute method on the task returned error code 0x80131904 (A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server)). The Execute method must succeed, and indicate the result using an "out" parameter. End Error Warning: 2010-06-12 20:01:23.60 Code: 0x80019002 Source: OnPostExecute Description: SSIS Warning Code DTS_W_MAXIMUMERRORCOUNTREACHED. The Execution method succeeded, but the number of errors raised (2) 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. End Warning DTExec: The package execution returned DTSER_FAILURE (1). Started: 8:00:02 PM Finished: 8:01:23 PM Elapsed: 81.594 seconds. The package execution failed. The step failed.
Thanks!
June 14, 2010 at 7:49 pm
That is still the Job History and not the maintenance plan history. The maintenance plan history is going to tell you what task failed and why.
Based upon this message, the maintenance plan cannot run because it cannot connect to the instance. The connection information for the local connection is not correct.
How was this maintenance plan created?
Jeffrey Williams
“We are all faced with a series of great opportunities brilliantly disguised as impossible situations.”
― Charles R. Swindoll
How to post questions to get better answers faster
Managing Transaction Logs
June 15, 2010 at 10:21 am
When I click Maintenance plan history, it does not show anything, but when job history is also included, the message as following is almost the same as before. Since full database backup is successful, why should there be any connection issue with transaction log backup?
Message
Executed as user: SCCGOV\sqlagent. Microsoft (R) SQL Server Execute Package Utility Version 10.0.2531.0 for 64-bit Copyright (C) Microsoft Corp 1984-2005. All rights reserved. Started: 8:00:04 PM Error: 2010-06-14 20:00:39.37 Code: 0xC00291EC Source: {3A069612-C02A-44B5-94D5-DBB8D3DF2DCD} Execute SQL Task Description: Failed to acquire connection "Local server connection". Connection may not be configured correctly or you may not have the right permissions on this connection. End Error Warning: 2010-06-14 20:00:39.39 Code: 0x80019002 Source: OnPreExecute Description: 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. End Warning Error: 2010-06-14 20:00:56.23 Code: 0xC0024104 Source: Back Up Database Task Description: The Execute method on the task returned error code 0x80131904 (A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server)). The Execute method must succeed, and indicate the result using an "out" parameter. End Error Error: 2010-06-14 20:01:14.50 Code: 0xC0024104 Source: Notify Operator Task Description: The Execute method on the task returned error code 0x80131904 (A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server)). The Execute method must succeed, and indicate the result using an "out" parameter. End Error Error: 2010-06-14 20:01:30.54 Code: 0xC0024104 Source: {C5EE17C7-FFA2-4974-A08F-D9D5178075D3} Description: The Execute method on the task returned error code 0x80131904 (A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server)). The Execute method must succeed, and indicate the result using an "out" parameter. End Error Warning: 2010-06-14 20:01:30.54 Code: 0x80019002 Source: OnPostExecute Description: SSIS Warning Code DTS_W_MAXIMUMERRORCOUNTREACHED. The Execution method succeeded, but the number of errors raised (2) 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. End Warning DTExec: The package execution returned DTSER_FAILURE (1). Started: 8:00:04 PM Finished: 8:01:30 PM Elapsed: 86.25 seconds. The package execution failed. The step failed.
June 15, 2010 at 12:00 pm
Thanks for the hint on maintenance plan creation.
The issue is now resolved.
June 15, 2010 at 7:43 pm
irene.leung (6/15/2010)
Thanks for the hint on maintenance plan creation.The issue is now resolved.
So, what was the problem and how did you correct it? Maybe someone else will come across this same issue and it would help them resolve their problem if they see how you resolved yours.
Jeffrey Williams
“We are all faced with a series of great opportunities brilliantly disguised as impossible situations.”
― Charles R. Swindoll
How to post questions to get better answers faster
Managing Transaction Logs
February 9, 2012 at 11:28 am
The way to resolve is Open the maintenance plan and check the connection properties. You might used a user name and changed the password.
Melban Samuel
February 16, 2012 at 6:08 am
hi,
am having the same issue but mine was that i was trying to run a data profiling task which i did create a new file connection to my C:\dataprofile.xml , it came back as fail with the following messages
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 "Package.dtsx" finished: Failure.
The program '[3260] Package.dtsx: DTS' has exited with code 0 (0x0).
Any idea how to resolve this.
March 14, 2014 at 10:41 am
I had this happen to me this morning and I fixed it doing a few things.
1. switched recovery mode to SIMPLE from FULL and FULL to SIMPLE to break the backup chain.
2. took a full backup of all databases using the maint plan.
3. took trans log backup of all databases using the maint plan.
This fixed the first node. I am in an AlwaysOn configuration so I had to remove the databaes form the AG group and put them back when I was done. Here is where it got crazy.
I went to the second node and ran a full backup using the maint plan, worked, then I ran the trans log backup, it failed. HHMM...
I looked at the history of the main job for my trans logs, I saw this error number -1073548784. Couldn't find anything on it. Then I thought I am going to script it out to see what is going on and where it is failing. My user databases were getting backups but not my system from the execution results running it as a query. I then went back into the main plan, said only backup tran logs for user databases. The maint. plan finished with success. I then went and maunally did a full backup on my systems databases, Master, Model, MSDB. Change my maint. plan back to backup all databases, ignore offlines and ran it again. it FINISHED WITH SUCCESS.
Hope this helps someone! 🙂
MCSE SQL Server 2012\2014\2016
Viewing 10 posts - 1 through 9 (of 9 total)
You must be logged in to reply to this topic. Login to reply