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: michael

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

Thank you for this, saved me!

By: Paul Hills

Paul Hills — Fri, 30 Oct 2009 10:27:13 +0000

Absolutely spot on – many thanks!!

By: Jane

Jane — Fri, 23 Oct 2009 09:34:34 +0000

Have just realised this seems to be a bug introduced in SQL2000 SP3 and not fixed in SP4.

Just waiting for permission to restart SQL on the affected box!

many thanks

By: P.L.

P.L. — Tue, 20 Oct 2009 11:57:17 +0000

THANKS a million!

By: aymeric

aymeric — Thu, 15 Oct 2009 14:26:41 +0000

Thanks, solved my problem

By: ceoj

ceoj — Mon, 28 Sep 2009 20:23:43 +0000

Dude! You are a GENIUS!

By: yoodles

yoodles — Thu, 13 Aug 2009 17:53:35 +0000

Great work, this really helped me out. Short and precise, do not find that much with us geeks, always want too much info in there! (myself included) Thanks again.

By: Kali

Kali — Mon, 10 Aug 2009 21:09:40 +0000

To people getting the error message:

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.

Please do not alter the line:

SET @server = CAST(SERVERPROPERTY(‘ServerName’)AS sysname)

You should leave ‘ServerName’ as it is. You should not replace it with your own server name.

Regards

By: Edivaldo Costa

Edivaldo Costa — Tue, 04 Aug 2009 23:02:10 +0000

Thanks a lot…

My case resolved too, after to apply last sugestion . This is error my jobs:

Solution:

use msdb
UPDATE sysjobs SET originating_Server = ‘new_servername’

Thanks again!!!

By: Genghis Khan

Genghis Khan — Wed, 08 Jul 2009 00:39:03 +0000

Gorgeous solution.
Thousand kisses from me.

By: gavin

gavin — Tue, 07 Jul 2009 13:00:31 +0000

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.

By: Bill T

Bill T — Tue, 19 May 2009 15:17:17 +0000

This was very easy and concise. Great write up. It helped out a lot

By: ashishtilak

ashishtilak — Fri, 01 May 2009 12:02:24 +0000

Thanks a lot… It saved me!!!

By: san

san — Thu, 30 Apr 2009 07:06:49 +0000

Thanks, it solved the problem as soon as the steps were performed.

By: Craig Greenwood

Craig Greenwood — Fri, 24 Apr 2009 17:05:59 +0000

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.

By: lalo

lalo — Fri, 17 Apr 2009 00:45:12 +0000

beautiful…… thanks a lot.. simply brilliant

By: jchen

jchen — Thu, 26 Mar 2009 17:56:52 +0000

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:

Can you help

Thank you so much,

chen

By: Toy

Toy — Wed, 28 Jan 2009 19:44:37 +0000

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.

By: Roel

Roel — Thu, 15 Jan 2009 07:13:50 +0000

Dave, Thank you for this solution.

By: George G

George G — Fri, 19 Dec 2008 05:17:59 +0000

Thanks heaps mate – help me overcome my problem

many blessing to you and your family