Error scene:
After the Windows hostname is changed, the 14274 error occurs when trying to update or delete the JOB created before the SQL Server 2000. SQL 7.0 does not appear this error, but in the Cluster environment, this error may be generated after upgrading SQL 7.0 virtual server to SQL Server 2000.
wrong reason:
The name of SQL Server 2000 Instance is saved in the column originating_server of MSDB..sysjobs, which is 'ServerInstance' (local in SQL 7.0, so unaffected), when the server name is changed, sysjobs Originating_Server and There is no corresponding update into new ServerInstance.
Workaround: 1. Remove Server back to the original name 2. Save all Job as Script, then delete 3. Change Server to a new name 4. Sequentially execute Script generated in step 2, restore all Job
Or directly update the sysjobs originating_serveruse msdb go SP_CONFIGURE 'ALLOW UPDATES', 1 RECONFIGURE WITH OVERRIDE GO update sysjobs set originating_server = @@ servername go SP_CONFIGURE 'ALLOW UPDATES', 0 RECONFIGURE WITH OVERRIDE GO
Reference article: http://support.microsoft.com/default.aspx? ScID = Kb; EN-US; 281642
