December 23, 2013 at 3:51 am
i have a weelkly maintainence job which is to rebuild\reorg indices in all the databases , the jobs are geting failed from last run but in maintainence plan history i didnot observed any error
Executing query "DECLARE @GUID UNIQUEIDENTIFIER EXECUTE msdb..sp".: 100% complete End Progress Error: 2013-12-22 04:48:59.01 Code: 0xC0024104 Source: Reorganize Index Description: The Execute method on the task returned error code 0x80004003 (Object reference not set to an instance of an object.). The Execute method must succeed, and indicate the result using an "out" parameter. End Error DTExec: The package execution returned DTSER_FAILURE (1).
How to reslove the error
December 23, 2013 at 5:50 am
Does it fail if you run it again at a different time?
It might be a table that is dropped / recreated frequently or during the maintenance period.
Do you have rebuild statistics ticked? The error message cuts off to early to tell, but it could be failing on sp_updatestats which you can run manually at a different time.
To get more info about the error, try opening the maintenance plan from BIDS and run it there manually with logging turned on, or follow these steps to enable more verbose logging: http://support.microsoft.com/kb/288577
September 8, 2015 at 1:37 am
I also got same error today:
Reorganize Index Description: The Execute method on the task returned error code 0x80004003 (Object reference not set to an instance of an object.). The Execute method must succeed, and indicate the result using an "out" parameter. End Error DTExec: The package execution returned DTSER_FAILURE (1).
Checked maintenance plan history,logs, event viwer etc but did not find anything useful. Also, no object was created/altered/dropped during this window.
Could you please help
September 8, 2015 at 7:54 am
Just a hunch... I've not had such thing happen to me for maintenance plans because I don't use them. However, if I did, the first thing I'd try is to open the maintenance plan and resave it.
--Jeff Moden
September 8, 2015 at 8:08 am
Thanks for the reply sir..I am not able to get why it failed. Could you please advise
September 8, 2015 at 8:26 am
Looking at ... "(Object reference not set to an instance of an object.)" ...
I would reconfigure every item in the package, especially the section where you select the database(s). It looks like something got "disconnected".
For best practices on asking questions, please read the following article: Forum Etiquette: How to post data/code on a forum to get the best help[/url]
September 8, 2015 at 10:50 am
I don't use MPs either.
But check for missing dbs. For example, maybe a db was moved or renamed.
SQL DBA,SQL Server MVP(07, 08, 09) "Money can't buy you happiness." Maybe so, but it can make your unhappiness a LOT more comfortable!
September 9, 2015 at 10:21 am
It ran successfully today. Thanks everyone
September 9, 2015 at 11:07 am
coolchaitu (9/9/2015)
It ran successfully today. Thanks everyone
What changed? Or did you resave it?
--Jeff Moden
September 9, 2015 at 11:36 am
Dear Jeff sir,
I did not re-save it and nothing changed. I just waited for job to run again today to see the outcome, and it ran successfully
September 9, 2015 at 5:05 pm
Thanks for the feedback... I hate problems like that because you never know when they'll occur again.
--Jeff Moden
September 10, 2015 at 12:09 pm
Jeff Moden (9/9/2015)
Thanks for the feedback... I hate problems like that because you never know when they'll occur again.
Reason why it failed? The job was run on the 2nd Monday after the last full moon in August. :alien:
For best practices on asking questions, please read the following article: Forum Etiquette: How to post data/code on a forum to get the best help[/url]
Viewing 12 posts - 1 through 11 (of 11 total)
You must be logged in to reply to this topic. Login to reply