error 14274 (trying to edit job after restoring msdb) 
Author Message
 error 14274 (trying to edit job after restoring msdb)
Hi! I have two stand alone server running sql server 2k SP2. I took back up
of msdb from one server and restored it to another. when I tried to
edit/delete some of the jobs in new server its giving me following error:
"can't delete/edit/change the job(or one of his steps) that is originated by
an msx-server."
Since my two server are stand alone server, I think there shouldn't be any
master or target server, then why this error message? how can I edit those
jobs?
any help is appreciated. thanks.


Mon, 01 Nov 2004 01:52:57 GMT
 error 14274 (trying to edit job after restoring msdb)

Your server reference in msdb..sysjobs refers to the other
server name. It's the same issue addressed in the following:
BUG: Error 14274 When Updating a SQL Agent Job After
Renaming Windows Server (Q281642)
http://support.microsoft.com/default.aspx?scid=kb;en-us;Q281642
The only other work around is unsupported and not
recommended as you have to update the system table directly
but....you would update the msdb..sysjobs table and change
the value in the originating_server column to the new server
name.

-Sue

On Wed, 15 May 2002 10:52:57 -0700, "james"

Quote:

>Hi! I have two stand alone server running sql server 2k SP2. I took back up
>of msdb from one server and restored it to another. when I tried to
>edit/delete some of the jobs in new server its giving me following error:
>"can't delete/edit/change the job(or one of his steps) that is originated by
>an msx-server."
>Since my two server are stand alone server, I think there shouldn't be any
>master or target server, then why this error message? how can I edit those
>jobs?
>any help is appreciated. thanks.



Mon, 01 Nov 2004 02:04:16 GMT
 error 14274 (trying to edit job after restoring msdb)
Because 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, because the two Windows
servers have different names, the jobs in question still
reference the original server name and may not be updated
or deleted by the process from the new server name.

WORKAROUND
==========

Solution:

1. Script out all of the jobs on the original server.

2. Add back the jobs to the other server by running the
script(s) generated from step 1.

For additional information, see the "Multiserver
Administration" article in SQL
Server Books Online.

Quote:
>-----Original Message-----
>Hi! I have two stand alone server running sql server 2k
SP2. I took back up
>of msdb from one server and restored it to another. when
I tried to
>edit/delete some of the jobs in new server its giving me
following error:
>"can't delete/edit/change the job(or one of his steps)

that is originated by
Quote:
>an msx-server."
>Since my two server are stand alone server, I think

there shouldn't be any
Quote:
>master or target server, then why this error message?

how can I edit those
Quote:
>jobs?
>any help is appreciated. thanks.

>.



Mon, 01 Nov 2004 02:08:16 GMT
 error 14274 (trying to edit job after restoring msdb)
Sue,
Thanks a lot. After updating sysjobs table I am able to edit the job. thanks
again.


Quote:
> Your server reference in msdb..sysjobs refers to the other
> server name. It's the same issue addressed in the following:
> BUG: Error 14274 When Updating a SQL Agent Job After
> Renaming Windows Server (Q281642)
> http://support.microsoft.com/default.aspx?scid=kb;en-us;Q281642
> The only other work around is unsupported and not
> recommended as you have to update the system table directly
> but....you would update the msdb..sysjobs table and change
> the value in the originating_server column to the new server
> name.

> -Sue

> On Wed, 15 May 2002 10:52:57 -0700, "james"

> >Hi! I have two stand alone server running sql server 2k SP2. I took back
up
> >of msdb from one server and restored it to another. when I tried to
> >edit/delete some of the jobs in new server its giving me following error:
> >"can't delete/edit/change the job(or one of his steps) that is originated
by
> >an msx-server."
> >Since my two server are stand alone server, I think there shouldn't be
any
> >master or target server, then why this error message? how can I edit
those
> >jobs?
> >any help is appreciated. thanks.



Mon, 01 Nov 2004 02:24:30 GMT
 error 14274 (trying to edit job after restoring msdb)

Hi,

This is a known issue if the Windows Server name was changed after the jobs
were created.
See http://support.microsoft.com/support/kb/articles/q281/6/42.asp for more
information.

-Ajay.

This posting is provided AS IS with no warranties, and confers no rights.
You assume all risk for your use. ? 2001 Microsoft Corporation. All rights
reserved.

Are you secure?  For information about the Strategic Technology Protection
Program and to order your FREE Security Tool Kit, please visit
http://www.microsoft.com/security.

--------------------

Quote:
>Content-Class: urn:content-classes:message



>Subject: error 14274 (trying to edit job after restoring msdb)
>Date: Wed, 15 May 2002 11:08:16 -0700
>Lines: 43

>MIME-Version: 1.0
>Content-Type: text/plain;
>    charset="iso-8859-1"
>Content-Transfer-Encoding: 7bit
>X-Newsreader: Microsoft CDO for Windows 2000
>X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4910.0300
>Thread-Index: AcH8O3zHhJsF1MrHSKedsnejfYhw2Q==
>Newsgroups: microsoft.public.sqlserver.server
>Path: cpmsftngxa08
>Xref: cpmsftngxa08 microsoft.public.sqlserver.server:210069
>NNTP-Posting-Host: TKMSFTNGXA13 10.201.226.41
>X-Tomcat-NG: microsoft.public.sqlserver.server

>Because 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, because the two Windows
>servers have different names, the jobs in question still
>reference the original server name and may not be updated
>or deleted by the process from the new server name.

>WORKAROUND
>==========

>Solution:

>1. Script out all of the jobs on the original server.

>2. Add back the jobs to the other server by running the
>script(s) generated from step 1.

>For additional information, see the "Multiserver
>Administration" article in SQL
>Server Books Online.

>>-----Original Message-----
>>Hi! I have two stand alone server running sql server 2k
>SP2. I took back up
>>of msdb from one server and restored it to another. when
>I tried to
>>edit/delete some of the jobs in new server its giving me
>following error:
>>"can't delete/edit/change the job(or one of his steps)
>that is originated by
>>an msx-server."
>>Since my two server are stand alone server, I think
>there shouldn't be any
>>master or target server, then why this error message?
>how can I edit those
>>jobs?
>>any help is appreciated. thanks.

>>.



Sat, 06 Nov 2004 00:18:38 GMT
 error 14274 (trying to edit job after restoring msdb)
Hi There,
A better way to work around this poblem is to use local\instancename if SQL
2K or local for SQL 7.0 so that if the server is renamed or moved again,
this error would not pop up for the jobs.

Hope this helps,
Thanks.

"This posting is provided AS IS with no warranties, and confers no
rights."



Sun, 07 Nov 2004 07:23:46 GMT
 
 [ 6 post ] 

 Relevant Pages 

1. Error 14274: Cannot add, update, or delete a job (or its steps or schedules) tha

2. Error 14274: Cannot add, update, or delete a job (or its steps or schedules) tha

3. Problems deleting a Job MSX server error 14274

4. Error 14274 working with scheduled jobs

5. Error 14274 working with scheduled jobs

6. Unable to delete job Error:14274

7. error 14274 -- 2nd request pls help

8. Error 14274

9. Solution for Error 14274 in SQL 2000

10. error 14274 - MSX server

11. Error : 14274

12. Error 14274: problem with MSX server


 
Powered by phpBB® Forum Software