Error 14274 Cannot Add Update Or Delete Msx Server
Contents |
SERVER - Fix : Error 14274: Cannot add, update, or delete a job (or its steps or schedules) that originated
Sp_add_jobserver
from an MSX server. The job was not saved. sp_delete_job December 20, 2006Pinal DaveSQL, SQL Server, SQL Tips and Tricks97 commentsTo fix the error sp_dropserver 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 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 Recent PostsRecent Posts Popular TopicsPopular Topics Home Search Members Calendar Who's On Home » SQL Server 7,2000 » Administration » Error 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 check.I’m trying to include some more databases in the 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/ 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 Agent are NOT deleted and I tried to delete manually but still getting the http://www.sqlservercentral.com/Forums/Topic846604-5-1.aspx 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 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 che add, update, or delete a job (or its steps or schedules) that originated from an MSX server. http://www.sqlbackuprestore.com/error14274.htm 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 = ' transaction log Backing up the tail Inside the transaction log So, what's in a backup file? Test: A full backup does not contain deleted data Verifying backup files Verifying backup files on a budget Cumulative backups Recovering individual tables Backup and restore history details Backup reads and writes Speeding up backups Backup speed details Speeding up restores Restore state affects speed too Backup and restore rights Log shipping Log shipping in SQL Server 2000 Setting up log shipping using Enterprise Manager Checking the set up Failover Log shipping in SQL Server 2005 Setting up log shipping using Management Studio Checking the set up Log shipping status report Failover Log shipping in SQL Backup Using the CopyTool utility Failover 3rd party backup applications VDI VDI versions VDI errors SQL Backup - beyond compression Restoring a chain of transaction log backups Restoring to the latest possible state Backing up multiple databases Backup retention Making a copy of the backup file Backup file naming conventions Restoring the latest backup set Network resilience Encryption Integrated database verification Database file relocation Improved backup retention RESTORE HELP High-availability group support Common SQL Backup issues Installation checklist Setting up rights Configuring service rights Backup data Hanging issues Common backup and restore errors Error 3201 - when performing a backup to a network share Full database backup file is larger than database size Error 3205 - Too many backup devices specified for backup or restore Error 4305 - an earlier transaction log backup is required Bringing a database that is in recovery or read-only mode online Using bulk-logged recovery model but transaction log backup is still large Error 14274 - unable to delete SQL Server Agent job Error messages when restoring from different versions of SQL Server. Pending vdi error codes Restore speed details Help, my transaction log file is huge! Mirror or log ship What When you attempt to edit or delete a SQL Server Agent job, you receive the following error: Error 14274: Cannot add, update, or delete a job (or its steps or schedules) that originated from an MSX server. and you do not have MSX or TSX servers set up. Why This is a known issue as reported here. The recommended approach is to rename the server to its original name, script out your jobs, rename the server back again, and recreate your jobs. There is a faster way that involves modifying the sysjobs table, so do this only with caution, and after you've backed up the msdb table. The reason for the error is because in msdb..sysjobs, the o