Error 14274 Msx
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 error 14274 sql server not saved. December 20, 2006Pinal DaveSQL, SQL Server, SQL Tips error 14274 cannot add update msx server and Tricks97 commentsTo fix the error which occurs after the Windows server name been changed, when error 14274 delete job 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
Cannot Delete Job Originated Msx Server
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 sp_add_jobserver 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 * Recent PostsRecent Posts Popular TopicsPopular Topics Home Search Members Calendar Who's On Home » SQL Server 7,2000 » Administration » Error sp_delete_job 14274: Cannot add, update, or delete a... Error 14274: Cannot add, update, or delete a job Rate Topic Display Mode Topic Options Author Message Mani-584606Mani-584606 Posted Tuesday, January 12, 2010 3:35 PM Mr or Mrs. 500 Group: General Forum Members Last Login: Friday, July 25, 2014 2:47 PM Points: 586, Visits: 1,998 Hi,We have SQL Server 2000 with SP3. We have a maintenance plan for backups, integrity 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/ check.I’m trying to include some more databases in the maintenance plan but I’m getting 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 http://www.sqlservercentral.com/Forums/Topic846604-5-1.aspx Agent are NOT deleted and I tried to delete manually but still getting the same above error.please advice thanks Post #846604 - 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 Poi blog clouds Conway DataGridView DNS Extranet focus forms inheritance msdb redirect SharePoint sql server 2000 SSP sysjobs thunderstorm title bar Visual Studio window WordPress workaround Blog Stats 30,406 hits Subscribe Subscribe in a reader SQL Server 2000: Error 14274: Cannot delete a job that originated from an MSXserver https://dotnetengineer.wordpress.com/2008/07/08/sql-server-2000-error-14274-cannot-delete-a-job-that-originated-from-an-msx-server/ July 8, 2008 -- Brandon Ryan I don't work much with older versions of http://dba.stackexchange.com/questions/18612/cant-do-any-changes-to-a-job-in-sql-2000 SQL server, but I came across the following error today when trying to disable a scheduled SQL 2000 job while trying to backup a SharePoint Portal Server 2003 database. Error 14274: Cannot delete a job that originated from an MSX server This error message has two possible causes: either the SQL server is not a standalone server, and this message error 14274 is appropriate, or the name of the SQL server has changed since the scheduled job was created. In my case, the scheduled job had been around for over 6 years, and the server had been renamed about 5 years ago. The job has continued to run and noone needed to make changes to it. I looked in the sysjobs table in the msdb database and noticed that in the originating_server field, the old server name was error 14274 msx still there. I updated each of them with the following statement: UPDATE sysjobs SET originating_server='yourNewServerName' and all was well. Like this:Like Loading... Related Posted in SQL Server Maintenance. Tags: msdb, sql server 2000, sysjobs. 5 Comments » 5 Responses to "SQL Server 2000: Error 14274: Cannot delete a job that originated from an MSXserver" Bookmarks about Sql Says: December 10, 2008 at 11:15 am […] - bookmarked by 6 members originally found by anderzd on 2008-11-04 SQL Server 2000: Error 14274: Cannot delete a job that originated … […] Reply Ezequiel Says: September 27, 2009 at 4:54 am Thank's a lot! I can't find a simple solution like this in everyplce! Microsoft says that i need to change the name server to the old name, delete the jobs… To complicated and un-usefull for a production server! Sorry for my REALLY bad english! Greetings from Argentina! Reply Steve Says: October 28, 2011 at 3:22 pm Dude, thank you for the originating_server fix. MS was totally useless on how to fix this problem. Reply Abdulkarim Says: September 16, 2012 at 4:01 am clean solution… thanks man Reply Marcos Says: March 21, 2014 at 8:29 am The best solution. Only add that you must execute it for the msdb schema. Thank you very much. Reply Leave a Reply Cancel reply Enter your comment here... Fi 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 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 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 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 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 generated from step 2. Additionally you can find more discussion/suggestions here ... http://blog.s
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
DECLARE Sp_dropserver