March 8, 2009 at 1:11 pm
Executed as user: domainname\USer. Microsoft (R) SQL Server Execute Package Utility Version 9.00.3042.00 for 32-bit Copyright (C) Microsoft Corp 1984-2005. All rights reserved. Started: 1:47:58 PM Progress: 2009-03-08 13:47:59.71 Source: {B36C637D-2C0C-4735-BEA1-DFB20346F726} Executing query "DECLARE @GUID UNIQUEIDENTIFIER EXECUTE msdb..sp".: 100% complete End Progress Error: 2009-03-08 13:48:02.57 Code: 0xC0024104 Source: Rebuild Index Task Description: The Execute method on the task returned error code 0x80131500 (Failed to retrieve data for this request.). The Execute method must succeed, and indicate the result using an "out" parameter. End Error DTExec: The package execution returned DTSER_FAILURE (1). Started: 1:47:58 PM Finished: 1:48:02 PM Elapsed: 3.875 seconds. The package execution failed. The step failed.
March 9, 2009 at 6:29 am
What kind of job are you executing? Sounds like an SSIS package error.
What version of SQL Server are you using (including service pack)?
March 10, 2009 at 6:51 am
Hi,
Job is crated by Database Maintenance plan.
Below is the box configuration:
Microsoft Windos 2003 with SP1,
MSSQL2005 Standard Edition with SP2
Please let me know if you are in need more info.
Regards,
Anurag
March 10, 2009 at 7:13 am
Okay. DB Maintenance plans are created as SSIS packages, so that explains the error format.
More questions & some suggestions.
Do you have any third party software installed for backing up your databases? Like Litespeed or things like that? This might be causing the issue.
Try right clicking the database and backing it up from the GUI. Does this work on its own?
Do the databases listed in your maintenance plan all still exist? One didn't accidently get deleted, did it?
This probably isn't the problem, but verify you have enough hard drive space to complete all the backups.
March 10, 2009 at 10:58 pm
Hi,
The above job is not for taking a Database backup. Infact, I have made one Maint plan which is having two steps:
1) First step execute the Rebuilt the all user databases,
2) Second step check the integrity of all system + User databases.
One more thing I wanted to tell you that For testing purpose, i have crated new maint plan for the same, it has executed successfully.
However, I am not identifying the root cause why the existing job is doing such type of behaviour.
Thanks for continuing the email.
Regards,
Anurag Tripathi
March 11, 2009 at 5:06 am
Anurag Tripathi (3/10/2009)
Hi,The above job is not for taking a Database backup. Infact, I have made one Maint plan which is having two steps:
Ah. In that case, you shouldn't have posted this in the backup forum. It should have been posted in General or Administering. The backup forum is for backup related issues, not generic maint. plan issues.
I'll ask Steve to move this post into one of the other forums so we can get more people on this thread.
March 15, 2009 at 12:40 pm
Hi,
Thanks for your continuous support.
I have recreated the Job and itis running fine as of now.
Regards,
Anurag Tripathi
March 19, 2009 at 4:47 am
I know you said things are working fine, but curiousity just struck.
Did you create the MP while your SQL Server was at SP1 patch level, then create the new job after patching up to SP2?
SP1 had all sorts of issues with MP's and the upgrade might not have "fixed" your previously existing package.
March 21, 2009 at 5:50 am
Hi,
It might be the same as you describing. Thanks for support.
🙂
Regards,
Anurag Tripathi.
March 23, 2009 at 4:12 am
NP. Glad we could help.
Viewing 10 posts - 1 through 9 (of 9 total)
You must be logged in to reply to this topic. Login to reply