Hi
I restored msdb database successfully,
because of changing
the server and needed to restore all jobs
have been schaduled for periodical backup all
user batabases.
but when I want to change the text of step1
of every job to new drive in a new server
following error happened:
""
why? what's wrong?
any help would be greatly appreciated.
RM,
Do you get an error number?
Mark Allison, SQL Server MVP
http://www.markallison.co.uk
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
RM wrote:
> Hi
> I restored msdb database successfully,
> because of changing
> the server and needed to restore all jobs
> have been schaduled for periodical backup all
> user batabases.
> but when I want to change the text of step1
> of every job to new drive in a new server
> following error happened:
> ""
> why? what's wrong?
> any help would be greatly appreciated.
|||Also check SQL server error log and SQLAgent log for complete information on this behaviour.
--
Satya SKJ
"Mark Allison" wrote:
> RM,
> Do you get an error number?
> --
> Mark Allison, SQL Server MVP
> http://www.markallison.co.uk
> Looking for a SQL Server replication book?
> http://www.nwsu.com/0974973602.html
>
> RM wrote:
>
|||yeah,
error 14274
On Mon, 12 Jul 2004 11:32:16 +0100, Mark Allison
<marka@.no.tinned.meat.mvps.org> wrote:
[vbcol=seagreen]
> RM,
> Do you get an error number?
> --
> Mark Allison, SQL Server MVP
> http://www.markallison.co.uk
> Looking for a SQL Server replication book?
> http://www.nwsu.com/0974973602.html
>
> RM wrote:
|||RM, I don't know why your error message text is not showing but it
should be this:
"Error 14274: Cannot add, update, or delete a job (or its steps or
schedules) that originated from an MSX server."
This means that the server has been renamed and the originating_server
column in the sysjobs table is referencing the old server name. Update
sysjobs and it should be fine.
Use this proc to do the rename:
http://sqldev.net/download/sqlagent/...ent_rename.sql
This proc assumes that @.@.SERVERNAME is correct, you might want to check
that first, and correct it if it's wrong using sp_dropserver, sp_addserver
Mark Allison, SQL Server MVP
http://www.markallison.co.uk
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
RM wrote:
> yeah,
> error 14274
> On Mon, 12 Jul 2004 11:32:16 +0100, Mark Allison
> <marka@.no.tinned.meat.mvps.org> wrote:
>
>
|||thanks alot,
I was suprised ,very useful help**
On Tue, 13 Jul 2004 09:24:57 +0100, Mark Allison
<marka@.no.tinned.meat.mvps.org> wrote:
[vbcol=seagreen]
> RM, I don't know why your error message text is not showing but it
> should be this:
> "Error 14274: Cannot add, update, or delete a job (or its steps or
> schedules) that originated from an MSX server."
> This means that the server has been renamed and the originating_server
> column in the sysjobs table is referencing the old server name. Update
> sysjobs and it should be fine.
> Use this proc to do the rename:
> http://sqldev.net/download/sqlagent/...ent_rename.sql
> This proc assumes that @.@.SERVERNAME is correct, you might want to check
> that first, and correct it if it's wrong using sp_dropserver,
> sp_addserver
> --
> Mark Allison, SQL Server MVP
> http://www.markallison.co.uk
> Looking for a SQL Server replication book?
> http://www.nwsu.com/0974973602.html
>
> RM wrote:
Showing posts with label periodical. Show all posts
Showing posts with label periodical. Show all posts
Tuesday, March 20, 2012
restoring msdb**
Hi
I restored msdb database successfully,
because of changing
the server and needed to restore all jobs
have been schaduled for periodical backup all
user batabases.
but when I want to change the text of step1
of every job to new drive in a new server
following error happened:
""
why? what's wrong?
any help would be greatly appreciated.RM,
Do you get an error number?
--
Mark Allison, SQL Server MVP
http://www.markallison.co.uk
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
RM wrote:
> Hi
> I restored msdb database successfully,
> because of changing
> the server and needed to restore all jobs
> have been schaduled for periodical backup all
> user batabases.
> but when I want to change the text of step1
> of every job to new drive in a new server
> following error happened:
> ""
> why? what's wrong?
> any help would be greatly appreciated.|||Also check SQL server error log and SQLAgent log for complete information on
this behaviour.
--
--
Satya SKJ
"Mark Allison" wrote:
> RM,
> Do you get an error number?
> --
> Mark Allison, SQL Server MVP
> http://www.markallison.co.uk
> Looking for a SQL Server replication book?
> http://www.nwsu.com/0974973602.html
>
> RM wrote:
>|||yeah,
error 14274
On Mon, 12 Jul 2004 11:32:16 +0100, Mark Allison
<marka@.no.tinned.meat.mvps.org> wrote:
[vbcol=seagreen]
> RM,
> Do you get an error number?
> --
> Mark Allison, SQL Server MVP
> http://www.markallison.co.uk
> Looking for a SQL Server replication book?
> http://www.nwsu.com/0974973602.html
>
> RM wrote:|||RM, I don't know why your error message text is not showing but it
should be this:
"Error 14274: Cannot add, update, or delete a job (or its steps or
schedules) that originated from an MSX server."
This means that the server has been renamed and the originating_server
column in the sysjobs table is referencing the old server name. Update
sysjobs and it should be fine.
Use this proc to do the rename:
http://sqldev.net/download/sqlagent...gent_rename.sql
This proc assumes that @.@.SERVERNAME is correct, you might want to check
that first, and correct it if it's wrong using sp_dropserver, sp_addserver
Mark Allison, SQL Server MVP
http://www.markallison.co.uk
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
RM wrote:
> yeah,
> error 14274
> On Mon, 12 Jul 2004 11:32:16 +0100, Mark Allison
> <marka@.no.tinned.meat.mvps.org> wrote:
>
>|||thanks alot,
I was suprised ,very useful help**
On Tue, 13 Jul 2004 09:24:57 +0100, Mark Allison
<marka@.no.tinned.meat.mvps.org> wrote:
[vbcol=seagreen]
> RM, I don't know why your error message text is not showing but it
> should be this:
> "Error 14274: Cannot add, update, or delete a job (or its steps or
> schedules) that originated from an MSX server."
> This means that the server has been renamed and the originating_server
> column in the sysjobs table is referencing the old server name. Update
> sysjobs and it should be fine.
> Use this proc to do the rename:
> http://sqldev.net/download/sqlagent...gent_rename.sql
> This proc assumes that @.@.SERVERNAME is correct, you might want to check
> that first, and correct it if it's wrong using sp_dropserver,
> sp_addserver
> --
> Mark Allison, SQL Server MVP
> http://www.markallison.co.uk
> Looking for a SQL Server replication book?
> http://www.nwsu.com/0974973602.html
>
> RM wrote:
I restored msdb database successfully,
because of changing
the server and needed to restore all jobs
have been schaduled for periodical backup all
user batabases.
but when I want to change the text of step1
of every job to new drive in a new server
following error happened:
""
why? what's wrong?
any help would be greatly appreciated.RM,
Do you get an error number?
--
Mark Allison, SQL Server MVP
http://www.markallison.co.uk
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
RM wrote:
> Hi
> I restored msdb database successfully,
> because of changing
> the server and needed to restore all jobs
> have been schaduled for periodical backup all
> user batabases.
> but when I want to change the text of step1
> of every job to new drive in a new server
> following error happened:
> ""
> why? what's wrong?
> any help would be greatly appreciated.|||Also check SQL server error log and SQLAgent log for complete information on
this behaviour.
--
--
Satya SKJ
"Mark Allison" wrote:
> RM,
> Do you get an error number?
> --
> Mark Allison, SQL Server MVP
> http://www.markallison.co.uk
> Looking for a SQL Server replication book?
> http://www.nwsu.com/0974973602.html
>
> RM wrote:
>|||yeah,
error 14274
On Mon, 12 Jul 2004 11:32:16 +0100, Mark Allison
<marka@.no.tinned.meat.mvps.org> wrote:
[vbcol=seagreen]
> RM,
> Do you get an error number?
> --
> Mark Allison, SQL Server MVP
> http://www.markallison.co.uk
> Looking for a SQL Server replication book?
> http://www.nwsu.com/0974973602.html
>
> RM wrote:|||RM, I don't know why your error message text is not showing but it
should be this:
"Error 14274: Cannot add, update, or delete a job (or its steps or
schedules) that originated from an MSX server."
This means that the server has been renamed and the originating_server
column in the sysjobs table is referencing the old server name. Update
sysjobs and it should be fine.
Use this proc to do the rename:
http://sqldev.net/download/sqlagent...gent_rename.sql
This proc assumes that @.@.SERVERNAME is correct, you might want to check
that first, and correct it if it's wrong using sp_dropserver, sp_addserver
Mark Allison, SQL Server MVP
http://www.markallison.co.uk
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
RM wrote:
> yeah,
> error 14274
> On Mon, 12 Jul 2004 11:32:16 +0100, Mark Allison
> <marka@.no.tinned.meat.mvps.org> wrote:
>
>|||thanks alot,
I was suprised ,very useful help**
On Tue, 13 Jul 2004 09:24:57 +0100, Mark Allison
<marka@.no.tinned.meat.mvps.org> wrote:
[vbcol=seagreen]
> RM, I don't know why your error message text is not showing but it
> should be this:
> "Error 14274: Cannot add, update, or delete a job (or its steps or
> schedules) that originated from an MSX server."
> This means that the server has been renamed and the originating_server
> column in the sysjobs table is referencing the old server name. Update
> sysjobs and it should be fine.
> Use this proc to do the rename:
> http://sqldev.net/download/sqlagent...gent_rename.sql
> This proc assumes that @.@.SERVERNAME is correct, you might want to check
> that first, and correct it if it's wrong using sp_dropserver,
> sp_addserver
> --
> Mark Allison, SQL Server MVP
> http://www.markallison.co.uk
> Looking for a SQL Server replication book?
> http://www.nwsu.com/0974973602.html
>
> RM wrote:
restoring msdb**
Hi
I restored msdb database successfully,
because of changing
the server and needed to restore all jobs
have been schaduled for periodical backup all
user batabases.
but when I want to change the text of step1
of every job to new drive in a new server
following error happened:
""
why? what's wrong?
any help would be greatly appreciated.RM,
Do you get an error number?
--
Mark Allison, SQL Server MVP
http://www.markallison.co.uk
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
RM wrote:
> Hi
> I restored msdb database successfully,
> because of changing
> the server and needed to restore all jobs
> have been schaduled for periodical backup all
> user batabases.
> but when I want to change the text of step1
> of every job to new drive in a new server
> following error happened:
> ""
> why? what's wrong?
> any help would be greatly appreciated.|||Also check SQL server error log and SQLAgent log for complete information on this behaviour.
--
--
Satya SKJ
"Mark Allison" wrote:
> RM,
> Do you get an error number?
> --
> Mark Allison, SQL Server MVP
> http://www.markallison.co.uk
> Looking for a SQL Server replication book?
> http://www.nwsu.com/0974973602.html
>
> RM wrote:
> > Hi
> >
> > I restored msdb database successfully,
> > because of changing
> > the server and needed to restore all jobs
> > have been schaduled for periodical backup all
> > user batabases.
> > but when I want to change the text of step1
> > of every job to new drive in a new server
> > following error happened:
> > ""
> >
> > why? what's wrong?
> > any help would be greatly appreciated.
>|||yeah,
error 14274
On Mon, 12 Jul 2004 11:32:16 +0100, Mark Allison
<marka@.no.tinned.meat.mvps.org> wrote:
> RM,
> Do you get an error number?
> --
> Mark Allison, SQL Server MVP
> http://www.markallison.co.uk
> Looking for a SQL Server replication book?
> http://www.nwsu.com/0974973602.html
>
> RM wrote:
>> Hi
>> I restored msdb database successfully,
>> because of changing
>> the server and needed to restore all jobs
>> have been schaduled for periodical backup all
>> user batabases.
>> but when I want to change the text of step1
>> of every job to new drive in a new server
>> following error happened:
>> ""
>> why? what's wrong?
>> any help would be greatly appreciated.|||RM, I don't know why your error message text is not showing but it
should be this:
"Error 14274: Cannot add, update, or delete a job (or its steps or
schedules) that originated from an MSX server."
This means that the server has been renamed and the originating_server
column in the sysjobs table is referencing the old server name. Update
sysjobs and it should be fine.
Use this proc to do the rename:
http://sqldev.net/download/sqlagent/sp_sqlagent_rename.sql
This proc assumes that @.@.SERVERNAME is correct, you might want to check
that first, and correct it if it's wrong using sp_dropserver, sp_addserver
--
Mark Allison, SQL Server MVP
http://www.markallison.co.uk
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
RM wrote:
> yeah,
> error 14274
> On Mon, 12 Jul 2004 11:32:16 +0100, Mark Allison
> <marka@.no.tinned.meat.mvps.org> wrote:
>> RM,
>> Do you get an error number?
>> --
>> Mark Allison, SQL Server MVP
>> http://www.markallison.co.uk
>> Looking for a SQL Server replication book?
>> http://www.nwsu.com/0974973602.html
>>
>> RM wrote:
>> Hi
>> I restored msdb database successfully,
>> because of changing
>> the server and needed to restore all jobs
>> have been schaduled for periodical backup all
>> user batabases.
>> but when I want to change the text of step1
>> of every job to new drive in a new server
>> following error happened:
>> ""
>> why? what's wrong?
>> any help would be greatly appreciated.
>|||thanks alot,
I was suprised ,very useful help**
On Tue, 13 Jul 2004 09:24:57 +0100, Mark Allison
<marka@.no.tinned.meat.mvps.org> wrote:
> RM, I don't know why your error message text is not showing but it
> should be this:
> "Error 14274: Cannot add, update, or delete a job (or its steps or
> schedules) that originated from an MSX server."
> This means that the server has been renamed and the originating_server
> column in the sysjobs table is referencing the old server name. Update
> sysjobs and it should be fine.
> Use this proc to do the rename:
> http://sqldev.net/download/sqlagent/sp_sqlagent_rename.sql
> This proc assumes that @.@.SERVERNAME is correct, you might want to check
> that first, and correct it if it's wrong using sp_dropserver,
> sp_addserver
> --
> Mark Allison, SQL Server MVP
> http://www.markallison.co.uk
> Looking for a SQL Server replication book?
> http://www.nwsu.com/0974973602.html
>
> RM wrote:
>> yeah,
>> error 14274
>> On Mon, 12 Jul 2004 11:32:16 +0100, Mark Allison
>> <marka@.no.tinned.meat.mvps.org> wrote:
>> RM,
>> Do you get an error number?
>> -- Mark Allison, SQL Server MVP
>> http://www.markallison.co.uk
>> Looking for a SQL Server replication book?
>> http://www.nwsu.com/0974973602.html
>>
>> RM wrote:
>> Hi
>> I restored msdb database successfully,
>> because of changing
>> the server and needed to restore all jobs
>> have been schaduled for periodical backup all
>> user batabases.
>> but when I want to change the text of step1
>> of every job to new drive in a new server
>> following error happened:
>> ""
>> why? what's wrong?
>> any help would be greatly appreciated.
>>
I restored msdb database successfully,
because of changing
the server and needed to restore all jobs
have been schaduled for periodical backup all
user batabases.
but when I want to change the text of step1
of every job to new drive in a new server
following error happened:
""
why? what's wrong?
any help would be greatly appreciated.RM,
Do you get an error number?
--
Mark Allison, SQL Server MVP
http://www.markallison.co.uk
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
RM wrote:
> Hi
> I restored msdb database successfully,
> because of changing
> the server and needed to restore all jobs
> have been schaduled for periodical backup all
> user batabases.
> but when I want to change the text of step1
> of every job to new drive in a new server
> following error happened:
> ""
> why? what's wrong?
> any help would be greatly appreciated.|||Also check SQL server error log and SQLAgent log for complete information on this behaviour.
--
--
Satya SKJ
"Mark Allison" wrote:
> RM,
> Do you get an error number?
> --
> Mark Allison, SQL Server MVP
> http://www.markallison.co.uk
> Looking for a SQL Server replication book?
> http://www.nwsu.com/0974973602.html
>
> RM wrote:
> > Hi
> >
> > I restored msdb database successfully,
> > because of changing
> > the server and needed to restore all jobs
> > have been schaduled for periodical backup all
> > user batabases.
> > but when I want to change the text of step1
> > of every job to new drive in a new server
> > following error happened:
> > ""
> >
> > why? what's wrong?
> > any help would be greatly appreciated.
>|||yeah,
error 14274
On Mon, 12 Jul 2004 11:32:16 +0100, Mark Allison
<marka@.no.tinned.meat.mvps.org> wrote:
> RM,
> Do you get an error number?
> --
> Mark Allison, SQL Server MVP
> http://www.markallison.co.uk
> Looking for a SQL Server replication book?
> http://www.nwsu.com/0974973602.html
>
> RM wrote:
>> Hi
>> I restored msdb database successfully,
>> because of changing
>> the server and needed to restore all jobs
>> have been schaduled for periodical backup all
>> user batabases.
>> but when I want to change the text of step1
>> of every job to new drive in a new server
>> following error happened:
>> ""
>> why? what's wrong?
>> any help would be greatly appreciated.|||RM, I don't know why your error message text is not showing but it
should be this:
"Error 14274: Cannot add, update, or delete a job (or its steps or
schedules) that originated from an MSX server."
This means that the server has been renamed and the originating_server
column in the sysjobs table is referencing the old server name. Update
sysjobs and it should be fine.
Use this proc to do the rename:
http://sqldev.net/download/sqlagent/sp_sqlagent_rename.sql
This proc assumes that @.@.SERVERNAME is correct, you might want to check
that first, and correct it if it's wrong using sp_dropserver, sp_addserver
--
Mark Allison, SQL Server MVP
http://www.markallison.co.uk
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
RM wrote:
> yeah,
> error 14274
> On Mon, 12 Jul 2004 11:32:16 +0100, Mark Allison
> <marka@.no.tinned.meat.mvps.org> wrote:
>> RM,
>> Do you get an error number?
>> --
>> Mark Allison, SQL Server MVP
>> http://www.markallison.co.uk
>> Looking for a SQL Server replication book?
>> http://www.nwsu.com/0974973602.html
>>
>> RM wrote:
>> Hi
>> I restored msdb database successfully,
>> because of changing
>> the server and needed to restore all jobs
>> have been schaduled for periodical backup all
>> user batabases.
>> but when I want to change the text of step1
>> of every job to new drive in a new server
>> following error happened:
>> ""
>> why? what's wrong?
>> any help would be greatly appreciated.
>|||thanks alot,
I was suprised ,very useful help**
On Tue, 13 Jul 2004 09:24:57 +0100, Mark Allison
<marka@.no.tinned.meat.mvps.org> wrote:
> RM, I don't know why your error message text is not showing but it
> should be this:
> "Error 14274: Cannot add, update, or delete a job (or its steps or
> schedules) that originated from an MSX server."
> This means that the server has been renamed and the originating_server
> column in the sysjobs table is referencing the old server name. Update
> sysjobs and it should be fine.
> Use this proc to do the rename:
> http://sqldev.net/download/sqlagent/sp_sqlagent_rename.sql
> This proc assumes that @.@.SERVERNAME is correct, you might want to check
> that first, and correct it if it's wrong using sp_dropserver,
> sp_addserver
> --
> Mark Allison, SQL Server MVP
> http://www.markallison.co.uk
> Looking for a SQL Server replication book?
> http://www.nwsu.com/0974973602.html
>
> RM wrote:
>> yeah,
>> error 14274
>> On Mon, 12 Jul 2004 11:32:16 +0100, Mark Allison
>> <marka@.no.tinned.meat.mvps.org> wrote:
>> RM,
>> Do you get an error number?
>> -- Mark Allison, SQL Server MVP
>> http://www.markallison.co.uk
>> Looking for a SQL Server replication book?
>> http://www.nwsu.com/0974973602.html
>>
>> RM wrote:
>> Hi
>> I restored msdb database successfully,
>> because of changing
>> the server and needed to restore all jobs
>> have been schaduled for periodical backup all
>> user batabases.
>> but when I want to change the text of step1
>> of every job to new drive in a new server
>> following error happened:
>> ""
>> why? what's wrong?
>> any help would be greatly appreciated.
>>
Subscribe to:
Posts (Atom)