We use SSIS packages to import files. These SSIS packages are run with sqljobs. During deployment the sqljobs are created with a script. That is the plan.
While running the script to create the sqljobs we got an error:
Error 14274: Cannot add, update, or delete a job (or its steps or schedules) that originated from an MSX server
Image courtesy of jesadaphorn / FreeDigitalPhotos.net
Most solutions found on the internet talk about the name of the server. When you’ve renamed your Sql Server (yeah right) then you need to update the originating_server column in the sysjobs. This was not the case for us.
Over at msdn someone suggested to look at the variables. The first create sqljob would set the @jobid variable and the second create statement would use that value as input, where it is intended as output. The suggested SET @jobid = NULL before each call to sp_add_job did the trick.
