I have a problem with EM and the msdb. I get an error message 14274
when I try to edit or delete a job. The data in the msdb for the jobs
was generated by a restored backup that came from another machine, and
a different instance of SQL Server. The old default server instance
was called 'SQL_Server' and the new default instance is called
'SDO-SQL'.
The error message states:
Cannot add, update, or delete a job (or its steps or schedules) that
originated from an MSX server.
I don't have a master scheduling server. I get the error
message when attempting to change a job. eg. enable/disable a job,
change the time, delete a job, add a job.
Server is running w2k Server SP4
I tired the following:
USE MSDB
UPDATE sysjobs
SET originating_server = 'SD0-SQL'
From the properties of any job, I can see that the 'Source' is now
correctly identified as 'SDO-SQL', but the problem still remains.
What can I do with these jobs so that I can edit and delete them on
the new server?
Thank you for your help!
CSDunnHi
It looks like you may have already seen
http://support.microsoft.com/defaul...kb;en-us;281642
It suggests that you rename the server back to the old server name rather
than mess with the tables, but if you are trying to update sysjob I would
expect originating_server to be in the form 'server\instance'.
John
"CSDunn" <cdunn@.valverde.edu> wrote in message
news:807dbff7.0405151632.2f68ffe8@.posting.google.c om...
> Hello,
> I have a problem with EM and the msdb. I get an error message 14274
> when I try to edit or delete a job. The data in the msdb for the jobs
> was generated by a restored backup that came from another machine, and
> a different instance of SQL Server. The old default server instance
> was called 'SQL_Server' and the new default instance is called
> 'SDO-SQL'.
> The error message states:
> Cannot add, update, or delete a job (or its steps or schedules) that
> originated from an MSX server.
> I don't have a master scheduling server. I get the error
> message when attempting to change a job. eg. enable/disable a job,
> change the time, delete a job, add a job.
> Server is running w2k Server SP4
> I tired the following:
> USE MSDB
> UPDATE sysjobs
> SET originating_server = 'SD0-SQL'
> From the properties of any job, I can see that the 'Source' is now
> correctly identified as 'SDO-SQL', but the problem still remains.
> What can I do with these jobs so that I can edit and delete them on
> the new server?
> Thank you for your help!
> CSDunn|||John,
Thank you for your help!
CSDunn
"John Bell" <jbellnewsposts@.hotmail.com> wrote in message news:<0lEpc.948$XY4.12507228@.news-text.cableinet.net>...
> Hi
> It looks like you may have already seen
> http://support.microsoft.com/defaul...kb;en-us;281642
> It suggests that you rename the server back to the old server name rather
> than mess with the tables, but if you are trying to update sysjob I would
> expect originating_server to be in the form 'server\instance'.
> John
> "CSDunn" <cdunn@.valverde.edu> wrote in message
> news:807dbff7.0405151632.2f68ffe8@.posting.google.c om...
> > Hello,
> > I have a problem with EM and the msdb. I get an error message 14274
> > when I try to edit or delete a job. The data in the msdb for the jobs
> > was generated by a restored backup that came from another machine, and
> > a different instance of SQL Server. The old default server instance
> > was called 'SQL_Server' and the new default instance is called
> > 'SDO-SQL'.
> > The error message states:
> > Cannot add, update, or delete a job (or its steps or schedules) that
> > originated from an MSX server.
> > I don't have a master scheduling server. I get the error
> > message when attempting to change a job. eg. enable/disable a job,
> > change the time, delete a job, add a job.
> > Server is running w2k Server SP4
> > I tired the following:
> > USE MSDB
> > UPDATE sysjobs
> > SET originating_server = 'SD0-SQL'
> > From the properties of any job, I can see that the 'Source' is now
> > correctly identified as 'SDO-SQL', but the problem still remains.
> > What can I do with these jobs so that I can edit and delete them on
> > the new server?
> > Thank you for your help!
> > CSDunn|||I found another workaround (OS W2K3 Server, SQL Server 2K with SP4):
1. Script out all of the jobs.
2. Update the job source by:
USE MSDB
UPDATE sysjobs
SET originating_server = 'New_Server_Name'
3. Rename the jobs to be deleted.
4. Delete the jobs.
5. Add back the jobs by running the script generated from step 1.
Hope this will work better!
Ray
