Error 14274
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 not error 14274 that originated from an msx server saved. December 20, 2006Pinal DaveSQL, SQL Server, SQL Tips and
Error 14274 Delete Job
Tricks97 commentsTo fix the error which occurs after the Windows server name been changed, when trying error 14274 cannot add update 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
Sp_add_jobserver
(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 sp_delete_job 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 * 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 check.I’m trying to include some more databases in the maintenance plan but I’m getting the below error:Error 14274: Cannot 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/ 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 - Win.- Win. Posted Tuesday, January 12, 2010 http://www.sqlservercentral.com/Forums/Topic846604-5-1.aspx 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 modify the properties through that table Post #870951 john.schenckjohn.schenck Posted Wednesday, May 18, 20 add, update, or delete a job (or its steps or schedules) that originated from an MSX server. http://www.sqlserver-query.com/sql-server-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 error 14274 the format server\instance. Even for the default instance of the server, the actual server name is used instead of (local). After the Windows server is renamed, these jobs still reference the original server name and may not be updated or error 14274 that deleted by the process from the new server name. It’s a known problem with SQL2000 SP3. Fix --Verify Server Name SELECT @@servername If SQL name is not correct run. -- if no sp_dropserver <'nameReturned'> -- and then sp_addserver <'correctServername'> , 'local' Print 'Your server name has now been changed, restart SQL Service so changes will take effect.' If SQL name is correct run. --check originating_server column SELECT * FROM msdb..sysjobs --if not USE msdb GO DECLARE @server sysname SET @server = CAST(SERVERPROPERTY('ServerName')AS sysname) UPDATE sysjobs SET originating_server = @server WHERE originating_server = ' Database Engine Tuning Advisor SQL SERVER - Create Database Role with simple example using tsql Script » SQL Server Error 14274 - Cannot add, update or delete a job (or its steps or schedules) that originated from an MSX server 7 Nov 2014 | SQL Server Database Maintenance Error 14274 occurs when you try to update a sql agent job after renaming server name. If sql server is running on the server then after renaming windows server, you need to update sql server name. Otherwise when you will try to add, update or delete a job on sql server, it will throw below error. SQL Server 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. Because MSDB stores server name in originating_server field under sysjobs table. So now whenever you will try to access jobs information it will refer to old server. SQL server 2000 supports multiple instances so for default instance also it store server name instead of local. Fix-Workaround-Solution To fix this problem, one option to drop old server name using system stored procedure in sql server and then add new server name and restart the services. a. Run the below query SELECT @@servername b. Run system stored procedure to drop server sp_dropserver ‘old server name' c. Run system stored procedure to drop server sp_addserver ‘new server name' d. Restart sql server services to takes change e. Again perform the step 1 to verify the updated server name. Now you can run query against sysjobs table to see the changes in originating_server field. 2. To resolve this problem by using manual method (script out) 1. Revert the server back to old name. 2. Generate script for all sql jobs and delete them. 3. Rename the server to the new name. 4. Execute the script generated by step 2. If all above solution doesn't work for you then run update command to server name in sysjobs table. UPDATE sysjobs SET originating_server = ‘New Server Name' Where originating_server = ‘old Server name' Leave a Reply Cancel Reply Author (required) Email (will not be published)(required) Website 6 − = 3 « SQL Server Profiler – Collect Workload data fo
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 @server Sp_dropserver