Error DTExec: The package execution returned DTSER_FAILURE (1)

Question

Error DTExec: The package execution returned DTSER_FAILURE (1)

dm_tapas

Hall of Fame

Points: 3515
More actions
September 10, 2013 at 4:45 am

#297577

Hi,
A Maintenance Plan Job for UpdateStatistics is scheduled from SQL Server 2008 and it is a weekly job (Sunday). Last Sunday it failed with the below error. Can some body help me to fix the issue.
Error:
Executed as user: ABC\XXX. Microsoft (R) SQL Server Execute Package Utility Version 10.50.1600.1 for 64-bit Copyright (C) Microsoft Corporation 2010. All rights reserved. Started: 6:00:02 AM Progress: 2013-09-08 06:00:11.52 Source: {9B20A854-9645-4762-B4C7-8B5DA1A19210} Executing query "DECLARE @GUID UNIQUEIDENTIFIER EXECUTE msdb..sp...".: 100% complete End Progress Error: 2013-09-08 06:22:09.05 Code: 0xC0024104 Source: Update Statistics Description: The Execute method on the task returned error code 0x80131501 (An exception occurred while executing a Transact-SQL statement or batch.). The Execute method must succeed, and indicate the result using an "out" parameter. End Error DTExec: The package execution returned DTSER_FAILURE (1). Started: 6:00:02 AM Finished: 6:22:09 AM Elapsed: 1327.41 seconds. The package execution failed. The step failed.
Thanks in advance
Tapas

Viewing 8 posts - 1 through 7 (of 7 total)

You must be logged in to reply to this topic. Login to reply

RTaylor2208 SSChampion Points: 13298 More actions · Answer 1

The error does not show enough detail to debug the problem. Have you tried running the the package using the dtexec command line and redirecting the output to a file so you have the complete logging?

It will give you the failure message as the results you have there are truncated.

MCITP SQL 2005, MCSA SQL 2012

RTaylor2208 SSChampion Points: 13298 More actions · Answer 2

Having just re-read your question and realising you are using a maintenance plan.

You can edit your maintenance plan and if you click on the button that looks like 2 pages which when hovered over has the text "reporting and Logging" you can add logging output to a file. When the plan is ran this file will have the whole output and give you more information as to why the process failed which is not included in the SQL agent job output.

MCITP SQL 2005, MCSA SQL 2012

SQL Surfer '66 SSCertifiable Points: 5161 More actions · Answer 3

Has the job worked before? Has there been any changes in permissions?

Have you tried running the query in SSMS logged in as the same user running the job?

dm_tapas Hall of Fame Points: 3515 More actions · Answer 4

Thank you,

The job is running since 3 years,,, last 2 weeks it got failed. Nothing has been changed compare to earlier.

some body suggested to delete and recreate the job.. actually, it worked for them.

But I want to know the actual reason of the issue.

Tapas

Koen Verbeeck SSC Guru Points: 259115 More actions · Answer 5

dm_tapas (9/13/2013)
Thank you,
The job is running since 3 years,,, last 2 weeks it got failed. Nothing has been changed compare to earlier.
some body suggested to delete and recreate the job.. actually, it worked for them.
But I want to know the actual reason of the issue.
Tapas

To know the actual reason, you need detailed logging.

Need an answer? No, you need a question
My blog at https://sqlkover.com.
MCSE Business Intelligence - Microsoft Data Platform MVP

SQL Surfer '66 SSCertifiable Points: 5161 More actions · Answer 6

Have you tried running the query in SSMS logged in as the same user running the job?

dm_tapas Hall of Fame Points: 3515 More actions · Answer 7

this is production system.... I have to run the script on Sunday .... as scheduled .

Let me check...