SQL SERVER – Fix : 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.

December 20, 2006 by pinaldave

To fix the error which occurs after the Windows server name been changed, when trying to update or delete the jobs previously created in a SQL Server 2000 instance, or attaching msdb database.

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.

Reason:
SQL Server 2000 supports multi-instances, the originating_server field contains the instance name in the format ’server\instance’. Even for the default instance of the server, the actual server name is used instead of ‘(local)’. Therefore, after the Windows server is renamed, these jobs still reference the original server name and may not be updated or deleted by the process from the new server name. It’s a known problem with SQL2000 SP3.

Fix/Workaround/Solution:

In order to solve the problem you should perform the following steps:

From the Query Analyzer run following steps in order:
SELECT @@servername

and verify if it shows the correct SQL server name.

a) If not, run:
sp_dropserver <'name_returned'>

and then:
sp_addserver <'correct_servername'>, 'local'

to change the SQL server name.

Please restart SQL server service to let the new configuration takes effect.

b) If yes,

Please check the originating_server column in msdb..sysjobs by running:
SELECT * FROM msdb..sysjobs

and verify if all jobs have the correct server name for originating_server.

If not, update this value with the correct server name by running following script
USE msdb GO DECLARE @server sysname SET @server = CAST(SERVERPROPERTY('ServerName')AS sysname) UPDATE sysjobs SET originating_server = @server WHERE originating_server = '<wrong_servername>'

Reference: Pinal Dave (http://www.SQLAuthority.com),
http://support.microsoft.com/default.aspx?scid=kb;en-us;281642

Posted in Pinal Dave, SQL, SQL Authority, SQL Error Messages, SQL Query, SQL Scripts, SQL Server, SQL Stored Procedure, SQL Tips and Tricks, T SQL, Technology | 48 Comments

48 Responses

on March 9, 2007 at 12:58 pm James

Dave,

Excellent write-up!

Got me out of a pretty good jam!

Thanks!!
on April 26, 2007 at 11:52 pm Malik

Thanks Dear,

It solved my problem. Wish you a very happy life.

Regards,
Malik
on May 7, 2007 at 7:48 am Gabriel

Beautiful doc, excelent tip!

tks a lot!
Gabriel
on May 11, 2007 at 12:51 pm Max

I have to agree… Excellent, short and precise documentation.

Thanks,
Max
on May 13, 2007 at 8:34 am Marcus - Orange CA

This worked well… I was relieved to a final clean-up of the olf jobs I couldn’t remove.
Spent and hour searching for alternatives on microsoft.
found this in 2 minutes. Ran it in 1 minute.
10,000 thank you’s!
on May 31, 2007 at 11:02 pm udo

Thank you very much! Excellent document Have a long live!! :-))
on June 14, 2007 at 10:56 am Jose Luiz (Sao Paulo - Brazil)

Great tip, solve my problem
Thank you very much
on June 23, 2007 at 4:41 am Tudor

Dave,

Excellent and crystal article. THis solve my problem.
on July 15, 2007 at 5:30 pm Marcelo Fernandes (Brasilia- Brazil)

Thank you very much ! I solve my problem.
I hope you you have a very nice life
and God blesses you.
on July 30, 2007 at 4:46 am Càssio Dias - ( Brasíla - Brazil )

Thanks !!!!!!!!!!

It solved my problem!!!!!!!!!!

This document is very simple and very efficient.
on August 2, 2007 at 1:29 am Kevin Kemp- (England)

Thank you,

So simple and yet so effective. Having read what Microsoft suggested and then doing this. I am speachless.

Thanks again you saved my day
on August 16, 2007 at 5:26 pm Sathya

Great trick Boss! It helped fix our problem!
on September 6, 2007 at 6:51 am luca zaffarano

Thank you for you solution, good job!
Luca
on September 17, 2007 at 11:22 am Jim

Many thanks. You answered what many could not.
on September 21, 2007 at 9:28 am Amin Jamalomidy

It was wonderful. To be honest I am Oracle DBA but our company has few sql servers for support and I solved the problem with your tip. I wish a great life for you.
on December 13, 2007 at 3:10 pm Praseedha S

This blog was a big saviour!
Thanks a lot!
Praseedha S-India
on January 4, 2008 at 9:21 pm siva

Good artilce, it worked for me!

Thanks
Siva
on February 1, 2008 at 12:24 am Josh

Well done. Much better then MS fix!

Cheers,

Josh
on February 9, 2008 at 11:11 pm AMAVELI

congratulations you are my best friend…
on February 15, 2008 at 2:26 am In-Chang

Good solution – precise and direct. Thank you very much.

Microsoft should pay you for your support.
on March 12, 2008 at 12:36 pm Ashraf

That was straight forward and precise and yes it did solve the problem and saves my day man….thanks a lot to all.
on March 15, 2008 at 12:47 am Jon

Thanks, I had renamed a SQL server and this helped me fix sql agent jobs afterwards.
on April 5, 2008 at 4:08 am Dufftime

Thanks for the nice tip. There’s been so many times where I’ve renamed a SQL server and forgotten about the jobs. My only known solution was to rename it back temporarily just to delete the jobs.
on April 10, 2008 at 9:07 pm Dan

Thanks a lot for this! It was very helpful.

Just a note though, if you have MSDE, you might run into issues creating and using a variable. You can also use:

USE msdb
UPDATE sysjobs SET originating_server = @@servername

…IF you only have 1 instance and IF you correctly set the servername as the OP mentioned in part A.

Cheers,
Dan
on April 12, 2008 at 10:27 am Don Adams

What a time saver!
on May 15, 2008 at 3:30 am marilyn stokes

Thanks, I just migrated jobs from one server to another, and needed to quickly disable the jobs….and received an error. This has fixed my problem…thanks so much.
on May 28, 2008 at 9:38 am Manuel

Thanks you very much !!!
on May 29, 2008 at 5:37 pm shailesh

Excellent Article! Keep it up.

Thanks
on June 10, 2008 at 2:19 pm Nadear

Thanks a lot !
I’m Thai people..
This good blog..
I will come agin..
Bye Bye ^_____^
on June 26, 2008 at 1:21 pm Nur

Thank you very much. have a great day! :)
on June 30, 2008 at 10:43 pm Ramesh S

Hi Thanks a lot…..
on July 24, 2008 at 7:43 pm Murali

Excellent write-up!!!!
on July 29, 2008 at 5:37 pm kc

It worked. Thanks.
on August 19, 2008 at 7:51 pm mane

thank you very much. helped me to solve my problem.
on October 7, 2008 at 3:49 am Juan C

You are the Best!!!!
on October 23, 2008 at 7:48 am Nino

really helpfull!
on December 16, 2008 at 6:29 pm sveroa

Nice post…got me thinking and I could clean up some jobs that was copied from one server to another.

Thanks :)
on December 19, 2008 at 10:47 am George G

Thanks heaps mate – help me overcome my problem

many blessing to you and your family
on January 15, 2009 at 12:43 pm Roel

Dave, Thank you for this solution.
on January 29, 2009 at 1:14 am Toy

Thanks! I have implemented this fix successfully on SQL 2000 servers and now need to apply to a Sql 2005 server that was copied to another server. Unfortunately, the msdb.sysjobs table does not have an originating_server column in sql 2005. It is called originating_server_id. Is there a similiar fix for SQL 2005? Your assistance is greatly appreciated.
on March 26, 2009 at 11:26 pm jchen

I ran your script but it gave me another error.
here is your script:
USE msdb
GO
DECLARE @server sysname
SET @server = CAST(SERVERPROPERTY(‘ServerName’)AS sysname)
UPDATE sysjobs
SET originating_server = @server
WHERE originating_server = ‘’

here is the error:

Server: Msg 515, Level 16, State 2, Line 3
Cannot insert the value NULL into column ‘originating_server’,
table ‘msdb.dbo.sysjobs’; column does not allow nulls. UPDATE fails.
The statement has been terminated.

Can you help

Thank you so much,

chen
on April 17, 2009 at 6:15 am lalo

beautiful…… thanks a lot.. simply brilliant
on April 24, 2009 at 10:35 pm Craig Greenwood

As a way of improvement….

use msdb
UPDATE sysjobs SET originating_Server = ‘new_servername’

Does the same thing as:

USE msdb
GO
DECLARE @server sysname
SET @server = CAST(SERVERPROPERTY(’ServerName’)AS sysname)
UPDATE sysjobs
SET originating_server = @server
WHERE originating_server = ”

but it’s shorter. Less potential syntax issues as well.
on April 30, 2009 at 12:36 pm san

Thanks, it solved the problem as soon as the steps were performed.
on May 1, 2009 at 5:32 pm ashishtilak

Thanks a lot… It saved me!!!
on May 19, 2009 at 8:47 pm Bill T

This was very easy and concise. Great write up. It helped out a lot
on July 7, 2009 at 6:30 pm gavin

hi great write up,

what i did was a select:

SELECT *
FROM msdb..sysjobs

and then an update:

update msdb..sysjobs
set [originating_server] = ‘new_server_name’
where [originating_server] ‘new_server_name’

And then deleted it from the job schedule.

again good write up.
on July 8, 2009 at 6:09 am Genghis Khan

Gorgeous solution.
Thousand kisses from me.