Replication error: 21040 Publication does not exist

[NilsBevaart]

Hi,

I am starting with SQL Replication. I set up a distributer and a publisher on two different servers. I enabled a database on the publisher for replication.
When I use the wizzard to make a new publication, I get the following error:
Server Enterprise Manager could not create publication 'dbPW' from database 'dbPW'
Error 21040: Publication dbPW does not exist

The wizzard does not complete. If I cancel the oparation (the only option left), I do see an entry for this publication in the distribution database on the distributer.

I configured the publisher and the distributer again, but with the same result. Also if I use a name for the publication that has never been used.

Can anyone tell me how to solve this problem?
Thanks

Nils Bevaart

 

[Catadmin]

First, did you configure the Distributor first or second when you configured replication? It has to be first, or replication will be completely messed up.

Second, did you check to verify you (or the account used for replication) have all necessary permissions to table/database the publication is created from? If not, that would create problems.



Catadmin - MCDBA, MCSA
Remember, "Work" is a four letter word. And you know what your mother told you about using four letter words!

 

[NilsBevaart]

I configured the distributer first. Everything is configured under an account with SA rights. I also have these rights...

Nils Bevaart

 

[Catadmin]

Are SQL Server & SQL Server Agent set up under the local system account? I read somewhere that they need to be set up on a regular domain user account with "Log on as Part of the Operating System", "Log on as a Service" and "..Change Process Level Token..." user rights (can be found in Domain Security Policy or Local System Policy).



Catadmin - MCDBA, MCSA
Remember, "Work" is a four letter word. And you know what your mother told you about using four letter words!

 

[NilsBevaart]

They are set up as a domain account with sufficient rights.
It has worked in the past, but was disabled after a while. I am now reconfiguring replication on the same servers and cannnot get it working again.


Nils Bevaart