Re: Remote Dist - Snpsht / Trans Replication Fails to Create

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance



Has anyone created any previous publications on the publisher or
distributor?

Issue the Select @@servername query on the publisher and distributor.

You might also want to query on 14294 in this newsgroup to get reports on
other users who have encountered this error and how they solved it.

--
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html

Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"Mark Harris" <MarkHarris@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:55B6B40A-9561-43B2-9FFC-63C08268CA3A@xxxxxxxxxxxxxxxx
> you'll have to clarify a little ... "previous publications" of what?? from
> the same database, ANY other database??
>
> and which server am i running "select @@servername" against... baring in
> mind that the whole point is that i'm testing Remote distribution and
> therefore have two of the little devils ... and why is this relevant??
>
> "Hilary Cotter" wrote:
>
> > There have been reports of this error being caused by previous
publications
> > not being cleaned up correctly.
> >
> > The best way to fix this is to disable publisher and replication on the
> > publisher and try to reenable it.
> >
> > Also what does select @@servername return?
> >
> > --
> > Hilary Cotter
> > Looking for a SQL Server replication book?
> > http://www.nwsu.com/0974973602.html
> >
> > Looking for a FAQ on Indexing Services/SQL FTS
> > http://www.indexserverfaq.com
> > "Mark Harris" <MarkHarris@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
> > news:43481428-5374-42E2-9955-3E74D921880C@xxxxxxxxxxxxxxxx
> > > Hi All
> > >
> > > I'm currently "Proof of Concept"ing our new server architecture, which
is
> > > going to contain a Master SQL Server with a Remote Distributor. After
> > > ploughing through the initial permission probs, i've hit another
problem
> > that
> > > i dont know how to get around.
> > >
> > > If i try to create a Publication that is either Snapshot or
Transaction,
> > > Enterprise Manager comes up with :
> > >
> > > " ... Could not create publication ...
> > > Error 14294 : Supply either @jobID or @JobName to Identify the job"
> > >
> > > ... which i'm finding a little strange as nowhere on the Wizard has it
> > asked
> > > me anything about jobs!? lol
> > >
> > > The same thing does NOT occur if i setup a Merge Publication ... and
this
> > is
> > > created correctly with both Publisher and Remote Distributor being
> > perfectly
> > > happy!
> > >
> > > As mentioned, i'm just proving things out at the minute so this isn't
> > > desperately urgent ... but i will be needing the capability to create
any
> > > type of Publication that will use the Remote Distributor ... so all
help
> > > appreciated!
> > >
> > > Cheers
> > >
> > >
> > > Mark
> >
> >
> >


.



Relevant Pages

  • Re: Inactive Publisher??????
    ... MSdistpublishers table in msdb on the distributor server shows the ... Shouldn't the publisher server have is_publisher=1? ... I then imported data from the publisher to the subscriber so that the ...
    (microsoft.public.sqlserver.replication)
  • Re: Inactive Publisher??????
    ... The publisher name is in ALL CAPS. ... disabling distribution on the distributor and then rebooting ... made sure the other server was set up for publication. ... I then imported data from the publisher to the subscriber so that the ...
    (microsoft.public.sqlserver.replication)
  • Re: Error: 21670 SQL Server could not connect to the Distributor using the specified password. (Conf
    ... Connection to server failed. ... 2- Right click on the replication folder and select distributor ... If you have already entered your publisher ... the distrubution properties ...
    (microsoft.public.sqlserver.replication)
  • Re: Snapshots, Validation, Resynchronization with Merge Replicatio
    ... be deposited there instead of the distributor although you could place them ... Looking for a SQL Server replication book? ... If the distribution database is on our publisher, ... If the snapshot is a "snapshot of the publication", ...
    (microsoft.public.sqlserver.replication)
  • Re: Merge Replication
    ... On failover your new publication database should continue to write to ... the remote distributor and replicate to your subscribers. ... Is there anything particular about the missing publications? ... publications shows on new server. ...
    (microsoft.public.sqlserver.replication)