from Microsft eventhough they are not realted. :)
Hilary Cotter wrote:
> Did you configure the administrative link password correctly?
>
> If so, try to create a local distributor on the current publisher to make
> sure it is working correctly. Then disable it and use the remote publisher.
>
> --
> Hilary Cotter
> Director of Text Mining and Database Strategy
> RelevantNOISE.Com - Dedicated to mining blogs for business intelligence.
>
> This posting is my own and doesn't necessarily represent RelevantNoise's
> positions, strategies or opinions.
>
> 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 >
>
>
> "laststubborn" <arafatsalih@gmail.com> wrote in message
> news:1151485789.766322.190730@75g2000cwc.googlegroups.com...
> > Dear All,
> > I am trying to put distirbuter and subscriber on the same SQL Server
> > Machine. I achieved to enable the remote distributer on my server 2.I
> > was able to enable server1 as a publisher. I wanted to create my
> > publication on my server 1 and use the server 2 as a distributer and
> > the subscriber. However I have recieved a series of error messages
> > while I was creating the publication.
> > Here are the error messages :
> >
> > SQL Server Enterprise Manager could not enable database 'aaaaa' for
> > snopshot or transactional publications.
> > Error 20028 : The distributer has not been installed correctly. Could
> > not enable database for publishing.
> > The replication option 'publish' of database 'aaaaa' has been set to
> > false.
> > Can somebody help on this issue please?
> >
> > Regards
> >