Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
DBA007
Posting Yak Master
145 Posts |
 Posted - 2010-02-18 : 12:35:40
|
| Team,My Maintenanceplan had failed stating the error as 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-02-15 02:00:39.88 Code: 0xC0024104 Source: Check Database Integrity Ta... The package execution fa... The step failed. |
|
|
tkizer
Almighty SQL Goddess
38200 Posts |
|
|
DBA007
Posting Yak Master
145 Posts |
Posted - 2010-02-18 : 15:44:00
|
| thanks tara it worked.But my another maintanance plan have got the problem and i dont fix even after running checkdb it says like below,even it has remote connections enable.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: TCP Provider, error: 0 - No connection could be made because the target machine actively refused it.)). The Execute method must succeed, and indicate the result using an "out" parameter. End Error Warning: 2010-02-15 10:41:09.83 Code: 0x80019002 Source: OnPostExecute Description: SSIS Warning Code DTS_W_MAXIMUMERRORCOUNTREACHED. The Execution method succeeded, but the number of errors raised (2) reached ... The package execution fa... The step failed. |
 |
|
|
tkizer
Almighty SQL Goddess
38200 Posts |
Posted - 2010-02-19 : 16:23:02
|
| Running DCCC CHECKDB didn't fix the problem. I posted that so that you could determine if you had any data corruption, which is one of the reasons why an Integrity Checks job would fail. If DBCC CHECKDB didn't show any errors, then at least you don't have any data corruption.Your last post's error is because the SQL Server is unable to connect to the remote server. You'll probably need to add an alias to the database server where the job exists in order for the connection to work.Tara KizerMicrosoft MVP for Windows Server System - SQL Serverhttp://weblogs.sqlteam.com/tarad/Subscribe to my blog"Let's begin with the premise that everything you've done up until this point is wrong." |
|
|
|
DBA007
Posting Yak Master
145 Posts |
Posted - 2010-02-19 : 16:30:16
|
| can you provide me the steps to do that |
|
|
|
tkizer
Almighty SQL Goddess
38200 Posts |
|
|
|
|
|
MaximumErrorCount