Error 14274 Sql
Contents |
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 sp_add_jobserver not saved. December 20, 2006Pinal DaveSQL, SQL Server, SQL Tips
Sp_delete_job
and Tricks97 commentsTo fix the error which occurs after the Windows server name been changed, when
Sp_dropserver
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 @@servernameand 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..sysjobsand 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
http://blog.sqlauthority.com/2006/12/20/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/ the below error:Error 14274: Cannot add, update, or delete a job (or its steps or schedules) that originated from MSX server.After getting this error, I tried to delete the Maintenance plan, it gave same error couple of times and then it got deleted. But jobs related to this maintenance plan in SQL Agent are NOT deleted and I tried to delete manually but still getting the same above error.please advice thanks Post #846604 - http://www.sqlservercentral.com/Forums/Topic846604-5-1.aspx Win.- Win. Posted Tuesday, January 12, 2010 8:59 PM SSC Veteran Group: General Forum Members Last Login: Thursday, March 29, 2012 5:22 AM Points: 260, Visits: 800 If you want to delete the job, you can do that manually.Try :select * from sysjobs delete from sysjobs where name = '<>' or Job_ID = <>hope it will work. Cheers,- Win." Have a great day " Post #846668 MANU-J.MANU-J. Posted Wednesday, January 13, 2010 4:02 PM SSCommitted Group: General Forum Members Last Login: Thursday, May 22, 2014 7:04 AM Points: 1,688, Visits: 8,766 Have you renamed the server in recent past?http://support.microsoft.com/kb/281642MJ Post #847253 pakmanpakman Posted Tuesday, February 16, 2010 9:41 PM Forum Newbie Group: General Forum Members Last Login: Friday, September 16, 2011 10:51 PM Points: 8, Visits: 172 Open sysjobs table on msdb db and update originating_server field from old server name to newe.g. use msdbgoupdate sysjobs set originating_server = ‘new server name’ Post #866725 cute_lhen05cute_lhen05 Posted Tuesday, February 23, 2010 12:37 AM Grasshopper Group: General Forum Members Last Login: Thursday, May 6, 2010 2:30 AM Points: 23, Visits: 117 good job. it did work..if you want to disable a certain job.. no need to for the sp_dropdatabase procedure; you just need to check the msdb then sysjobs table, then change 1 to 0 from the enabled column; you may mod
log in tour help Tour Start here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and policies of this site About Us Learn more http://dba.stackexchange.com/questions/18612/cant-do-any-changes-to-a-job-in-sql-2000 about Stack Overflow the company Business Learn more about hiring developers or posting ads with us Database Administrators Questions Tags Users Badges Unanswered Ask Question _ Database Administrators Stack Exchange is a question and answer https://sqlcan.com/2009/01/20/error-14274-cannot-add-update-or-delete-a-job-or-its-steps-or-schedule-that-originated-from-an-msx-server/ site for database professionals who wish to improve their database skills and learn from others in the community. Join them; it only takes a minute: Sign up Here's how it works: Anybody can ask a error 14274 question Anybody can answer The best answers are voted up and rise to the top Can't do any changes to a job in SQL 2000 up vote 1 down vote favorite I have a job in my SQL 2000 server, this job is used to execute a DTS, i want to change the schedule of this job. but every time i try to change of delete or stop this job error 14274 sql i get the error message 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. i have a system shutdown coming up in the weekend and i cant stop this job... sql-server-2000 jobs share|improve this question edited May 31 '12 at 12:18 Leigh Riffel 18.4k1053127 asked May 31 '12 at 7:30 AmmarR 1,94921225 add a comment| 1 Answer 1 active oldest votes up vote 0 down vote accepted It sounds like you might be facing this issue ... http://support.microsoft.com/kb/281642 After the Windows server name been changed, when trying to update or delete the jobs previously created in a SQL Server 2000 instance, you may receive the following error message: 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. Here are the suggested steps to workaround the issue ... The best way to handle this problem after the rename process is to follow these steps: Rename the server back to the original name. Script out all of the jobs and then delete them. Rename the server to the new name. Add back the jobs by running the script
an MSXserver. Error 14274: Cannot add, update, or delete a job (or its steps or schedule) that originated from an MSXserver. January 20, 2009 Mohit Leave a comment Go to comments You can get this error when trying to modify the properties of a Job after the SQL Server has been renamed or cloned into another computer. When we create a job on SQL Server it creates an entry in sysjobs table logging the job and server originated from. We can fix this issue by updating the sysjobs table: USE [msdb] GO UPDATE sysjobs SET originating_server = 'NewServerName' GO In addition to jobs not working now the @@ServerName variable can also return invalid information, old server name. Because the @@ServerName gets the server information from the sysservers system table. We can fix this issue with following script: USE [master] GO sp_dropserver 'OldServerName' GO sp_addserver 'NewServerName', 'local' GO You will have to restart the SQL Server to see the new changes. Rate this:Share this:Click to share on Twitter (Opens in new window)Share on Facebook (Opens in new window)Click to share on LinkedIn (Opens in new window)Click to share on Google+ (Opens in new window)MoreClick to print (Opens in new window)Click to email (Opens in new window)Like this:Like Loading... Categories: SQL 2000, SQL Errors Tags: SQL Error 14274 Comments (0) Trackbacks (0) Leave a comment Trackback No comments yet. No trackbacks yet. Leave a Reply Cancel reply Enter your comment here... Fill in your details below or click an icon to log in: Email (required) (Address never made public) Name (required) Website You are commenting using your WordPress.com account. (LogOut/Change) You are commenting using your Twitter account. (LogOut/Change) You are commenting using your Facebook account. (LogOut/Change) You are commenting using your Google+ account. (LogOut/Change) Cancel Connecting to %s Notify me of new comments via email. Notify