If an SQL server error is solved (error 14274: unable to add, update, or delete a job initiated from the MSX server .)

After the Windows host name is changed, a 14274 error occurs when you try to update or delete a job created before SQL Server2000. This error does not occur in SQL 7.0, but this error may also occur after the SQL 7.0 virtual server is upgraded to SQL Server2000 in the cluster environment.

Error cause:

In MSDB .. the sysinating_server column of sysjobs stores the name of the SQL Server 2000 instance in the format of 'serverinstance' (in SQL 7.0, It is (local), so it is not affected). After the server name is changed, the originating_server of sysjobs is not updated to the new serverinstance.

Solution:

1. Change the server to its original name.
2. Save all jobs as scripts and delete them.
3. Change the server to a new name.
4. Execute the script generated in step 1 in sequence to restore all jobs.

Or directly update the originating_server of sysjobs.
Use 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

Or directly update the originating_server of sysjobs.
Use MSDB
Select * From sysjobs

Update sysjobs set originating_server = 'current server name'