April 5, 2010 at 9:53 am
I ran into this problem with a maintenance plan, a simple set of jobs to backup my databases and perform a CHECKDB:
Executed as user: csus\sls-dh. Microsoft (R) SQL Server Execute Package Utility Version 9.00.4035.00 for 32-bit Copyright (C) Microsoft Corp 1984-2005. All rights reserved. Started: 2:00:01 AM DTExec: The package execution returned DTSER_FAILURE (1). Started: 2:00:01 AM Finished: 2:01:46 AM Elapsed: 105.375 seconds. The package execution failed. The step failed.
Searches on all the pertinent sites didn't yield much, most told me to recreate the job or reboot the server. I tried both, no luck.
The messages started happening the same day I had to elevate privileges for a vendor account to upgrade their database. I ended up giving the account 'sysadmin' privs on the server (after trying to narrow down exactly what they needed and failing) which completed the upgrade successfully, but ending up causing the problem. Going thru the logs I found that the account changed the system setting 'allow updates' from 0 to 1. Checking BOL, found out that this is a no-no, that it's deprecated for SS2K5 and can cause problems. Changing it back solved my issue:
sp_configure 'allow updates', 0
go
reconfigure
go
Hope this helps someone else.
----------------------------------------------------------------------------
Sacramento SQL Server users group - http://sac.sqlpass.org
Follow me on Twitter - @SQLDCH
----------------------------------------------------------------------------
July 1, 2011 at 7:23 am
Yes it helped, I had this info from another site I'm not familiar with, your post confirmed for me it's the correct solution in my case. Lots of posts on here about this error without a solution posted. So thanks!
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply