Re: problem running sp_addpublication
- From: Ramesh <Ramesh@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Wed, 18 Jan 2006 14:48:02 -0800
Hi Adam,
I do have the same issue like while buidling my replication using
scripts it is giving the following error
Server: Msg 14294, Level 16, State 1, Procedure sp_verify_job_identifiers,
Line 24
Supply either @job_id or @job_name to identify the job
even if I have created the job for 'REPL-LogReader', before creating
publication it is throwing the same error, is there any way that I can solve
this error.
Please help.
Thanks
Ramesh
"Adam" wrote:
> Thank you Paul for your response. Your solution does make sense, however in
> my case the server name has not changed. I had forgotten to run the script to
> create jobs, running it seems to have solve the problem. I am pasting a part
> of that script to give you the idea.
>
> if (select count(*) from msdb.dbo.syscategories where name =
> N'REPL-LogReader') < 1
> execute msdb.dbo.sp_add_category N'REPL-LogReader'
>
> Thanks.
> -A
>
> "Paul Ibison" wrote:
>
> > Adam,
> >
> > I suggest running profiler to see what are the parameters being sent to this
> > procedure and to debug where the process is going wrong. The most likely
> > cause is a changed servername, as the error is raised in several system
> > procedures and the code is usually of the form....
> >
> > select @distribution_jobid = job_id from msdb..sysjobs_view where
> > name = @name and
> > UPPER(originating_server) = UPPER(CONVERT(sysname,
> > SERVERPROPERTY('ServerName')))
> > if @distribution_jobid IS NULL
> > begin
> > -- Message from msdb.dbo.sp_verify_job_identifiers
> > RAISERROR(14262, -1, -1, 'Job', @name)
> > GOTO UNDO
> > end
> >
> > So, if your servername has changed, this could be the cause of the problem.
> > In this case:
> >
> > Use Master
> > go
> > Select @@Servername
> >
> > This should return your current server name but if it
> > returns NULL then try:
> > Use Master
> > go
> > Sp_DropServer 'OldName'
> > GO
> > Use Master
> > go
> > Sp_Addserver 'NewName', 'local'
> > GO
> > Stop and Start SQL Services
> >
> > Cheers,
> > Paul Ibison SQL Server MVP, www.replicationanswers.com
> > (recommended sql server 2000 replication book:
> > http://www.nwsu.com/0974973602p.html)
> >
> >
> >
.
- Prev by Date: Re: Sql serve clustering
- Next by Date: Re: Merge Replication limit running in continuous mode
- Previous by thread: Re: restore to new hardware
- Next by thread: Re: Merge Replication limit running in continuous mode
- Index(es):
Relevant Pages
|
