July 19, 2006 at 12:57 pm
I have a Sql Server 2000 (SP3) and I'm trying to setup a transactional Replication to be used with MSDE subscribers. Same server is defined as distributor and publisher. I don't have any subscribers yet. Sql Server/Sql Server Agent services run under domain administrator's account. As soon as I create one publication with single article just for testing, I get this error. Any idea would be greatly appreciated, I can't do anything unless I resolve this.
Entela
July 19, 2006 at 1:20 pm
MSDE can't be used as Publisher or Distributor of Transactional Replication!
Cheers,
* Noel
July 19, 2006 at 1:27 pm
MSDE will be used as Subscriber only. Publisher/Distributor is Sql Server 2000 (SP3a). Any idea of the error?
Thanks,
July 19, 2006 at 2:04 pm
Make sure the Distributor is using the correct account!
* Noel
July 19, 2006 at 2:14 pm
What do you exactly mean, can you elaborate. Thanks,
July 19, 2006 at 2:41 pm
Under 'Configure Publishers, Subscribing, Distribution' then the Publishers Tab, hit the ellipsis button for 'distribution' and find what account is being used.
Make sure that if it is 'sa' you entered the right password otherwise ensure you have the correct windows account !
* Noel
July 19, 2006 at 2:56 pm
It's my believe that all Replication agents (Log reader included) are running under Sql Server Agent account. On the Publisher/Distributor box, Sql Server Agent is running under an account that is part of domain administrators group, so I don't see any permission issue in here.
July 19, 2006 at 3:07 pm
did you check it ?
* Noel
July 20, 2006 at 7:15 am
Yes, I did and Sql Server Agent is running under domain administrator account.
July 20, 2006 at 12:41 pm
Sorry for not comming back earlier. Let's try this again, shall we ?
is the DISTRIBUTOR running under the SQL Server Agent account?
Like I said check :
Go to 'Configure Publishers, Subscribing, Distribution' then the Publishers Tab, hit the ellipsis button for 'distribution'
What does that says ?
* Noel
July 21, 2006 at 7:31 am
Distributor runs under trusted connection (Impersonate Sql Server account ...). Just to let you know, I changed it to Sql Server authentication and used "sa" account and I did get exactly the same error. This is a server that was configured some time back for Replication and never had any problem. Replication was not used, it was more of a test so later on it was deleted to be recreated now. Except windows updates I'm pretty sure nothing else was installed on the server.
Would you have any idea, if reapplying service pack (currently it has SP3a) would help?
thanks,
Viewing 11 posts - 1 through 10 (of 10 total)
You must be logged in to reply to this topic. Login to reply