Comments on: 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.

By: Vramby

Vramby — Thu, 17 Nov 2011 12:50:06 +0000

Worked like a charm for meon a clone of an existing server with another name.

By: dan

dan — Tue, 15 Nov 2011 16:34:01 +0000

Fabulous… worked just as expected… 5 stars for this effort

By: k

Mon, 26 Sep 2011 22:45:19 +0000

Pinal, by any chance do you happen to know Sumit Dave?
He looks remarkabally like you.. just like your long lost brother. Have you been to kumbh?
- KK

By: Saravana Kumar

Saravana Kumar — Wed, 21 Sep 2011 13:51:32 +0000

Thanks

By: Ed Kamarauskas

Ed Kamarauskas — Fri, 29 Jul 2011 16:06:06 +0000

This worked perfectly. Many thanks! Both my production server and standby server names have been set properly. Thanks Again, Ed K

By: JB

JB — Sun, 24 Jul 2011 01:07:45 +0000

Thanks!!

By: BY

BY — Thu, 09 Jun 2011 17:43:15 +0000

This is still very effective after all these years. Thank you for writing it.

By: RD

RD — Fri, 25 Mar 2011 02:09:27 +0000

Thanx Matey!

By: Vishal

Vishal — Mon, 21 Mar 2011 07:47:47 +0000

You are superb.. Pinal

Thanks a lot..

By: Catherine Sulit

Catherine Sulit — Wed, 16 Mar 2011 13:37:59 +0000

Thank you. This is just one of your posts that really helped me.
We restored an image of our server so all jobs goofed up because of server renamed. And your solution just worked like a charm.

Best wishes to you.

By: RAJU BANDARU

RAJU BANDARU — Fri, 25 Feb 2011 07:58:49 +0000

TY Pinal.

By: Kaushal

Kaushal — Tue, 01 Feb 2011 06:53:57 +0000

Thanks Pinal. Worked well and saved a lot of time.

By: Michele Wu

Michele Wu — Fri, 14 Jan 2011 16:19:55 +0000

This works perfectly. Thanks a lot for always sharing useful stuff!!

By: Richard Tracy

Richard Tracy — Tue, 02 Nov 2010 20:25:17 +0000

This worked really well for me

Thank you very much

By: ott

ott — Tue, 28 Sep 2010 00:33:13 +0000

I just ran it like this
DELETE
FROM msdb..sysjobs

and it took them all off for me, if you don’t want to remove them all then put the name of the backup like

DELETE backup1
FROM msdb..sysjobs

By: Lori

Lori — Thu, 23 Sep 2010 14:19:07 +0000

Just what I needed! You’re the best!

By: Bryan

Bryan — Thu, 02 Sep 2010 14:16:55 +0000

Thanks a load… You’re GREAT

By: kunal

kunal — Fri, 13 Aug 2010 06:12:13 +0000

Great…Thanks for your help

By: Jasmin Hadzigrahic

Jasmin Hadzigrahic — Tue, 20 Apr 2010 07:50:47 +0000

Really, really, great work! You helped me sooo much!

Thanks a lot!
JSK

By: Tina

Tina — Thu, 25 Feb 2010 19:55:51 +0000

Thanks so much. Fixed my problem too.

By: David Chief

David Chief — Mon, 22 Feb 2010 23:19:50 +0000

Thanks so much!
Worked perfectly

By: zaty

zaty — Wed, 03 Feb 2010 18:19:52 +0000

Hi Dave,

I still having the following error when trying to delete a job even though the value of @@servername and originating_server is the same :

“Error 14274: Cannot add, update, or delete a job (or its steps or schedules) that originated from an MSX server”

select @@servername
AMCDE\VAULINETIX

SELECT originating_server FROM msdb..sysjobs

AMCDE\VAULINETIX

appreciate yr help. thanks

By: Alex

Alex — Thu, 28 Jan 2010 18:10:45 +0000

Thanks, worked like a charm!

By: Geoff

Geoff — Wed, 25 Nov 2009 17:26:09 +0000

Hey this was great, I did a small modification which takes care of all jobs that where not on this server by doing the following:

USE msdb
GO
DECLARE @server sysname
SET @server = CAST(SERVERPROPERTY(‘ServerName’)AS sysname)
PRINT @server

SELECT *
FROM msdb..sysjobs WHERE originating_server @server

UPDATE sysjobs
SET originating_server = @server
WHERE originating_server @server

the change is minor but it guarantees only changing those jobs that were not created on the new server

By: michael

michael — Thu, 05 Nov 2009 22:17:37 +0000

Thank you for this, saved me!