July 27, 2005 at 9:49 am
I scripted the jobs from the old server onto the new server (MSSQL2000). I then took the old server offline and renamed the new server. The SQL install has always been configured as "(local)" so I didn't actually go through the SQL Server rename. I now am unable to delete or modify the jobs. Here's the error I receive:
Error 14274: Cannot add, update or delete a job that originated from an MSX Server.
I read the article that explains I cannot do this because it is still associated with the old server name and that I have to rename the server back to the old server name, delete the jobs, and then rename the server back.
Is there any work around that would prevent me from having to rename the server? I'm a little apprehensive about renaming the server if it would require the rename of the SQL Server as well.
Hope I made sense, it's still early for me.
Thanks!
July 27, 2005 at 9:55 am
The other way without scripting your job is to stop sql agent and restore msdb database. Your job will comes with it as well as DTS packages.
Anyway, the way to fixed your problem is to do
update msdb..sysjobs
set originating_server = Newservername
Have a good day.
mom
July 27, 2005 at 11:02 am
Thanks, Mom! That's exactly what I was hoping for. I didn't know if editing sysjobs in this fashion was recommended.
How about if instead of updating them and delete them where originating_server = 'xxx'? Would this be alright as well?
Thanks again!
July 27, 2005 at 11:41 pm
I'm not sure if this may solve your issue. But it might.
EXEC sp_add_jobserver @job_name = 'Your Job Here', @server_name = @@ServerName
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply