SQL jobs are failing to run after upgrading from SQL 2005 TO SQL 2008 SP1

I am having a strange problem with certain SQL scheduled jobs failing every night.  I recently did a SQL upgrade on a SQL 2005 VM to SQL 2008 SP1.  The upgrade went smoothly with no errors to report.  But the following day I had several SQL jobs fail to run.  

I was able to manually run them with no problems.  I also scheduled the jobs to run at a different time and they ran fine.  But when they are scheduled to run at 8PM which they are normally scheduled to run they all failed with the following error message.

Date            3/10/2011 8:00:02 PM
Log            Job History (DISTRIBUTION.Subplan_1)

Step ID            1
Server            SERVERNAME
Job Name            DISTRIBUTION.Subplan_1
Step Name            Subplan_1
Duration            00:00:24
Sql Severity            0
Sql Message ID            0
Operator Emailed            
Operator Net sent            
Operator Paged            
Retries Attempted            0

Message
Executed as user: Domain Name\account name. Microsoft (R) SQL Server Execute Package Utility  Version 10.0.2531.0 for 32-bit  Copyright (C) Microsoft Corp 1984-2005. All rights reserved.    Started:  8:00:03 PM  Progress: 2011-03-10 20:00:13.30     Source: {DB51C47F-D2DD-47D8-B844-96E86F56A252}      Executing query "DECLARE @Guid UNIQUEIDENTIFIER      EXECUTE msdb..sp...".: 100% complete  End Progress  DTExec: The package execution returned DTSER_FAILURE (1).  Started:  8:00:03 PM  Finished: 8:00:25 PM  Elapsed:  21.891 seconds.  The package execution failed.  The step failed.

This is strange since running this job manually or at a different time works fine with no errors.  

I also deleted the old maintenance jobs and created new ones to see if this would resolve the problem and it did not.  

I am still having the same issues.




RayManAaaAsked:
Who is Participating?
 
Rich WeisslerConnect With a Mentor Professional Troublemaker^h^h^h^h^hshooterCommented:
Okay, trying wrapping my head around this, and what could be causing it to fail, and I eliminated almost everything I could think of... assuming you already checked it.  Finally I just decided to fall back on my google-fu.
http://ms-abhay.blogspot.com/2008/02/dtexec-package-execution-returned.html

And the answer there is "Check the sp_configure values and see if "allow updates" is set to 1 by mistake ..
reset it to 0 and you are done ...... "


See if that works for you.  *worry*
0
 
Rich WeisslerProfessional Troublemaker^h^h^h^h^hshooterCommented:
Just to double check, I haven't done an upgrade like this... but I do know that SQL 2008 sometimes present challenges because administrators on the local box don't necessary have SA permissions to SQL.  Referring to the message above... can you confirm that "Domain Name\account name" still has permissions to run the job?

(If you run the job manually, I believe it'll run under the permissions of the person manually running the job... not necessarily the person the job/task is configured to run as...)
0
 
RayManAaaAuthor Commented:
Yes, you are correct, when you run the job manually you run it under the permissions you are logged in with. Also, I am the local admin on this box and have sa rights.  The jobs are running under a windows domain account this account has local admin and sa permissions.  I never had a problem with any of these jobs failing before.  These problems started to occur after I did the upgrade to SQL 2008 SP1.  

Also in a vain attempt to resolve this problem I deleted these SQL jobs which were failing and re-creating them.  But for some reason these newly created jobs also to failed to run.  I have done many upgrade like this before and I never had any issues like this.  
0
 
RayManAaaAuthor Commented:
Oops,I forgot to award the points!
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.