Log Shipping Jobs please help us (Urgent need)

Hi,
When i am changing Log Shipping job owner in Monitor server, stand by server
and primary server, i am getting error as "Error 14269:Job 'Log shipping
alert job-backup' is already targetted at server. xxxxxx(SQL Instance) The
Job was not saved.
please advise how to chnage the Job owners, if we are getting these errors.
Thanks,
John
All, i am working with MS Support now for this error. we analyzed due to
sp_add_job and other related stored procedures does not take instance name
more than 30 chars (our servers have more than 30 chars).
so when ever we are setting up Log shipping or replication, shall we need
our SQL Intance should be lesthan 30 character? my friend is telling for
Oracle databases they dont have any problem with intance name length.
hope this scenario may help someone in future.
good lcuk to all, John
"John" wrote:

> Hi,
> When i am changing Log Shipping job owner in Monitor server, stand by server
> and primary server, i am getting error as "Error 14269:Job 'Log shipping
> alert job-backup' is already targetted at server. xxxxxx(SQL Instance) The
> Job was not saved.
> please advise how to chnage the Job owners, if we are getting these errors.
> Thanks,
> John
|||John,
You could create aliases with shorter names. Open the client network
utility and go to Aliases.
M