When executing sp_replicationdboption 'database_name','merge publish','true',
The Distributor has not been installed correctly. Could not enable database
for publishing.
"Hilary Cotter" wrote:
> Its unclear to me whether the problem is with management studio or
> replication itself.
>
> Can you try to create a publication using the stored procedures. try this
> for example.
>
> create database sp1replicationtest
>
> go
>
> use sp1replicationtest
>
> go
>
> sp_replicationdboption 'sp1replicationtest','publish','true'
>
> go
>
> sp_addpublication 'test',@status='active'
>
> go
>
> sp_addpublication_snapshot 'test'
>
> go
>
> create table test(pk int not null primary key, charcol char)
>
> go
>
> sp_addarticle 'test','test','test'
>
> go
>
> --
> 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 >
>
>
> "Jacob Page" <Jacob Page@discussions.microsoft.com> wrote in message
> news:B8645104-0E68-4134-9062-C63D3B561601@microsoft.com...
> > After applying service pack 1 to SQL Server 2005, I can no longer set up
> > publications. Here's what I'm attempting:
> >
> > Under the Object Explorer of SQL Server Management Studio, I'm
> > right-clicking on [INSTANCE]/Replication/Local Publications and selecting
> > "New Publication..." After clicking on that menu item, the mouse cursor
> > turns to an hourglass, but nothing happens afterward. For a minute or so
> > afterward, if I attempt any other actions in Management Studio, I'm given
> > a
> > message that SQL Server is currently busy.
> >
> > There is an entry in the error log that occurs in the same timeframe as my
> > attempted action. It reads, "Replication-(null): agent (null) scheduled
> > for
> > retry. Could not clean up the distribution history tables."
>
>