Encountered the following SQL Server error today that prevented modifying a job:
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.
This occurred in our instance because the server was built and SQL Server installed with a different name prior to going into production. Jobs created in SQL prior to the name change were recorded as having a different 'originating_server' to what the name of the server is now.
A quick google search revealed MS kb281642 that suggested
| 1. |
Rename the server back to the original name. |
| 2. |
Script out all of the jobs and then delete them. |
| 3. |
Rename the server to the new name. |
| 4. |
Add back the jobs by running the script generated from step 2. |
As this seemed a bit drastic under the circumstances, I took a look into msdb.sysjobs. It revealed the offending originating_server field and the pre-production server name values. Changing these to the current server name resolved the problem in this instance.