Error 14274 Cannot Msx Server
SERVER - Fix : Error 14274: Cannot add, update, or delete a job (or its steps or schedules) that originated from an MSX server. The job sp_add_jobserver was not saved. December 20, 2006Pinal DaveSQL, SQL Server, SQL sp_delete_job Tips and Tricks97 commentsTo fix the error which occurs after the Windows server name been changed, sp_dropserver when 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
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. December 20, 2006Pinal DaveSQL, SQL Server, SQL Tips and Tricks97 commentsTo fix the error which occurs after the Windows server name been changed, when 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 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/ 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 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 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 * add, update, or delete a 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/ 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 cannot 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 = ' 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+ acc
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