Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
dkimbrell
Starting Member
9 Posts |
 Posted - 2010-08-20 : 04:45:22
|
| I added a table tblJoinCustBlastList to a merge replicated database and now I'm getting this failure error during replication:Error messages:The schema script 'if object_id(N'[dbo].[tblJoinCustBlastlist]') is not null exec('ALTER TABLE [dbo].[tblJoinCustBlastlist] ADD CONSTRAINT PK_tblJoinCustBlastlist PRIMARY KEY CLUSTERED ( JoinID ) WITH( STATISTICS_NORECOMPUTE = OFF, IGNORE_DUP_KEY = OFF, ALLOW_ROW_LOCKS = ON, ALLOW_PAGE_LOCKS = ON) ON [PRIMARY]')' could not be propagated to the subscriber. (Source: MSSQL_REPL, Error number: MSSQL_REPL-2147201001) Get help: http://help/MSSQL_REPL-2147201001 Table 'tblJoinCustBlastlist' already has a primary key defined on it. (Source: MSSQLServer, Error number: 1779) Get help: http://help/1779 Could not create constraint. See previous errors. (Source: MSSQLServer, Error number: 1750) Get help: http://help/1750All of the help links are dead. The table which caused the replication to fail (rblJoinCustBlastList) only has 3 fields:JoinID -int- Primary Key - no nullsfkCustID - int- no nullsfkBlastListID - int- no nullsand the system-created field Rowguid - uniqueidentifierI did not do what the error messages are saying I did, which is mess with constraints or try to add a duplicate primary key.For my own troubleshooting and as an attempt to fix the problem quickly, I removed this table from the articles to be replicated and then I even deleted the entire table from the database. When took a new snapshot on the publisher and tried to synch again to see if the error cleared out, I got the exact same message! Why is it giving me an error on a table that's not even supposed to be replicating, and is even deleted? And how do I fix this? Please help a newbie, none of my users can synch now and I'll be lynched... |
|
|
dkimbrell
Starting Member
9 Posts |
Posted - 2010-08-20 : 10:16:18
|
| I fixed it by removing the table tbljoincustblastlist from the subscriber. I had removed this table from the publisher, but not from the subscriber and it was causing an error somehow, I presume it had something to do with a primary key constraint. whew! |
 |
|
|
|
|
|
|
|
SQL Server generating error during merge replicati