Error 14274 Cannot Add, update or delete jobs
-
Greetings all,
Just wondering if anyone else has seen this error. I was attempting to modify a Log backup job so that it no longer did the integrity checks when I got the message below. I had a devil of a time finding any info from Microsoft, then finally found a description of the error at: http://support.microsoft.com/default.aspx?scid=kb;en-us;281642.
The entire message text is as follows:
"Error 14274: Cannot add, update, or delete a job (or its steps or schedules) that originated from an MSX server. The job was not saved."
This happened on a SQL 2000 server that I had renamed and recently brought into production. Apparently if a SQL 2000 server is renamed, you can no longer modify the Maintenance Plan jobs as the system thinks they came from a master server.
Rather than their suggested workaround, I plan on just deleting and recreating the jobs I need to modify unless someone has advice to the contrary. Guess it's just one more thing I have to add to my move/rename server checklist for doing this sort of thing in the future.
My hovercraft is full of eels.
-
Check whether the originating_server name from sysjobs table is different than SQL Server name, If it does, you have to update this column with SQL Server name in table sysjobs in MSDB.
-
Cool - Thanks!
So from QA I can just update the 'originating_server' in the sysjobs table? I did verify that it still lists the old server name here. Then I should be able to modify jobs without recreating them, correct? Wonder why Microsoft's web site didn't list this as a possible workaround. Instead, they want you to name the server back to what it was, make the modifications, name it back, etc. which fixes your smaller problem but you're still left with a server where the jobs can't be modified when you name it back.
(PS - sorry guys for not posting this to the 'Backups' folder, but I couldn't get there today as IE kept timing out. At least I didn't cross post
) Thanks!My hovercraft is full of eels.
-
After update that column with current SQL Server name, you will be able to modify the jobs.
sp_configure 'allow update', 1
go
reconfigure with override
go
use msdb
go
update sysjobs set originating_server = 'yourSQLServername'
go
sp_configure 'allow update', 0
go
reconfigure with override
) Thanks!Viewing 4 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply