Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

Cannot recreate publication - 'dbo.sysmergepublications' missing.

3,504 views
Skip to first unread message

soren

unread,
Aug 23, 2006, 5:42:01 AM8/23/06
to
I am trying without success to recreate a publication that I have previously
removed.

I have tried both to recreate it from script and from the create publication
wizard.

I can't even create a new publication with a different name.

The problem seems to be related to a missing ''dbo.sysmergepublications'
table.

I get the error message below:

Messages
SQL Server could not create publication 'test_pub'. (New Publication Wizard)

------------------------------
ADDITIONAL INFORMATION:

An exception occurred while executing a Transact-SQL statement or batch.
(Microsoft.SqlServer.ConnectionInfo)

------------------------------

Invalid object name 'dbo.sysmergepublications'.

Hilary Cotter

unread,
Aug 23, 2006, 7:52:52 AM8/23/06
to
Can you do a
sp_replicationdboption 'databasename','merge publish','false'
GO
sp_replicationdboption 'databasename','merge publish','True'
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

"soren" <Henri...@newsgroup.nospam> wrote in message
news:687ECB80-3DA0-423B...@microsoft.com...

soren

unread,
Aug 23, 2006, 8:22:01 AM8/23/06
to
Hi Hilary

In response to executing a sp_replicationdboption 'databasename','merge
publish','false' I get the following message:

Msg 208, Level 16, State 1, Procedure sp_MSmergepublishdb, Line 103
Invalid object name 'dbo.sysmergesubscriptions'.

When executing sp_replicationdboption 'databasename','merge publish','true'
I get :

The replication option 'merge publish' of database 'mydatabasename' has
already been set to true.

Thank you

Soren

Hilary Cotter

unread,
Aug 23, 2006, 10:37:26 AM8/23/06
to
Check to see if this table (sysmergesubscriptions) exists, if it does not
create it like this create table sysmergesubscriptions (bogus int).

Then try to unpublish your database again. You may have to go through a few
bogus table and view creation statements to clear this error.

--
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

"soren" <Henri...@newsgroup.nospam> wrote in message

news:8ECCAA41-1DBB-4F80...@microsoft.com...

soren

unread,
Aug 24, 2006, 7:13:02 AM8/24/06
to
Hi Hillary

Thank you for your help so far. I managed to get a step further by scipting
some system table from a development server, but the problem now seems to be
a system view called 'sysmergeextendedarticlesview' which I have no idea of
how to create or copy from another server.

Any suggestions?

/Soren

Hilary Cotter

unread,
Aug 24, 2006, 8:51:28 AM8/24/06
to
create view sysmergeextendedarticlesview
as
select * from sysobjects

If that doesn't work script the view out from another publication and copy
it there.

--
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

"soren" <Henri...@newsgroup.nospam> wrote in message

news:ED9EDDA6-3CB3-4BC5...@microsoft.com...

privatenews

unread,
Aug 25, 2006, 2:04:36 AM8/25/06
to
Hello Soren,

If the issue perists, you may want to consider use sp_removedbreplication
system stored procedure to remove all the replication objects from a
database without updating the data at the distributor.

324401 How to manually remove a replication in SQL Server 2000 or in SQL
Server 2005
http://support.microsoft.com/default.aspx?scid=kb;EN-US;324401

I would recommend first removing the objects which gave errors in the
remove replication SP, then rerunning. Please note that you must back up
the database before any test as suggested.

Best Regards,

Peter Yang
MCSE2000/2003, MCSA, MCDBA
Microsoft Online Community Support
==================================================
Get notification to my posts through email? Please refer to
http://msdn.microsoft.com/subscriptions/managednewsgroups/default.aspx#notif
ications
<http://msdn.microsoft.com/subscriptions/managednewsgroups/default.aspx>.
Note: The MSDN Managed Newsgroup support offering is for non-urgent issues
where an initial response from the community or a Microsoft Support
Engineer within 1 business day is acceptable. Please note that each follow
up response may take approximately 2 business days as the support
professional working with you may need further investigation to reach the
most efficient resolution. The offering is not appropriate for situations
that require urgent, real-time or phone-based interactions or complex
project analysis and dump analysis issues. Issues of this nature are best
handled working with a dedicated Microsoft Support Engineer by contacting
Microsoft Customer Support Services (CSS) at
<http://msdn.microsoft.com/subscriptions/support/default.aspx>.
==================================================
This posting is provided "AS IS" with no warranties, and confers no rights.

chr...@datacom.co.nz

unread,
Sep 13, 2006, 9:58:35 PM9/13/06
to
How many people are on SP1 for SQL2005? (A painful process!)

I've had no problems adding and removing Publications until I installed
SP1 on Monday.

Now ... I get the same thing ...

chr...@datacom.co.nz

unread,
Sep 13, 2006, 10:08:14 PM9/13/06
to
Just to add a bit more ...

SSMS shows no Publications and yet an attempt to delete the database
failed saying the database could not be deleted while a publication
exists ... so I hit it will a big stick as follows ...

sp_removedbreplication '<Database name>'

... and then I could delete the database.

This approach ain't goin'ta cut it a production environment though!

Hilary Cotter

unread,
Sep 13, 2006, 11:25:20 PM9/13/06
to
I haven't had problems yet. Is this merge or transactional?

--
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

<chr...@datacom.co.nz> wrote in message
news:1158199115.0...@h48g2000cwc.googlegroups.com...

John A Grandy

unread,
Oct 25, 2006, 5:05:01 PM10/25/06
to
I'm having the same problem. It occurs when deleting and recreating a merge
replication publication with SQL Mobile 2005 clients.

I was able to recreate the publication a few times with no problems, but now
I receive the "Invalid object name dbo.sysmergepublications" error.


"Hilary Cotter" <hilary...@gmail.com> wrote in message
news:%238s7t06...@TK2MSFTNGP03.phx.gbl...

Wasim Akhtar

unread,
Nov 26, 2006, 7:36:33 PM11/26/06
to
This happens when you delete a merge substription outside the main
"Publisher Properties..." tool. So, run the following against that
database before setting it up again for Merge Replication:

---------------------------
Use [DataBaseName]

EXEC sp_removedbreplication

go
---------------------------

*** Sent via Developersdex http://www.developersdex.com ***

Michael Kane

unread,
Jan 25, 2007, 12:19:34 AM1/25/07
to
Here's a really great trick!

Backup the database before you setup the publication in the first place
(Usually, mine are from the development server).

Before killing the current publication...
Backup the data files and such from the current Db if you want to keep
all of the data.

To kill the current publication:
Right-click the database you want to remove the publication for and
select Tasks->Restore.

Select your restore media to be the backup from before the publication
was made. Next, Goto the options page (right Pane) and select the 1st
radio button. This will get rid of all signs of the publication in SQL
Server 2005's sense of the matter.

Allow Sql Server to restore the database.

Now that this process is complete, a quick refresh of Management
Studio's Right Pane will show that there are no longer any publications
for that database under the Replication folder.

Now, restore the data from the most current database in the same manner
- or with some creative queries.

Finally, you can recreate the publication with the usual wizard or
queries.

0 new messages