Can not create a new publication

Question

_{Monday, May 14, 2012 7:20 AM}

I ran into the following errors when I tried to create a new publication. There was a publication created on the server before. I guess that someone has been tried deleting the publication improperly, The error "dbo.syspublications is missing." raised when I try to disable the publisher. So I think it would be help if I could created another publication with the same publisher, but error happened to me. Please help me. 

Error===================================

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

===================================

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

Program Location:

   at Microsoft.SqlServer.Management.Common.ServerConnection.ExecuteNonQuery(String sqlCommand, ExecutionTypes executionType)
   at Microsoft.SqlServer.Management.Common.ServerConnection.ExecuteNonQuery(String sqlCommand)
   at Microsoft.SqlServer.Replication.ReplicationObject.ExecCommand(String commandIn)
   at Microsoft.SqlServer.Replication.ReplicationObject.CommonCreate()
   at Microsoft.SqlServer.Replication.Publication.Create()
   at Microsoft.SqlServer.Management.UI.CreatePublicationWizard.CreatePublicationThreadMethod()

===================================

Invalid column name 'originator_id'.
Object 'pubtest' does not exist or is not a valid object for this operation.
Changed database context to 'RAM'. (.Net SqlClient Data Provider)

For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&ProdVer=10.50.1617&EvtSrc=MSSQLServer&EvtID=207&LinkId=20476

All replies (3)

_{Monday, May 14, 2012 2:14 PM ✅Answered}

Hi,

If you do not have any other publication (tran, merge and snapshot) on this database, then you can run below SP to cleanup the replication completely:

sp_removedbreplication

and try to re-configure the Replication.

Thanks,

Santosh.

_{Tuesday, May 15, 2012 6:40 AM ✅Answered}

Hi Catherine0824,

Are you using merge replication? Based on my research this might be related to the subscriber database was previously a publisher.

As SantoshGoli mentioned you can try the  following on both the publisher and subscriber which deletes the relevant replication tables from the database including sysmergearticles.
sp_removedbreplication @dbname = 'PublicationDB'

And then you can re-create the publication again as well as the subscription, which should be without any issues.
Hopefully this works for you.

Regards, Amber zhang

_{Tuesday, May 15, 2012 9:34 AM}

This do resolve my problem, Thank you