Error Number 20669
(Русский)ישראל (עברית)المملكة العربية السعودية (العربية)ไทย (ไทย)대한민국 (한국어)中华人民共和国 (中文)台灣 (中文)日本 (日本語) HomeLibraryLearnDownloadsTroubleshootingCommunityForums Ask a question Quick access Forums home Browse forums users FAQ Search related threads Remove From My Forums Answered by: Error number: 20669 Synchronisation Won't Run SQL Server > SQL Server Replication Question 0 Sign in to vote hi Guys, I'm hoping someone may be able to help me with a problem I am having with SQL Server 2005 SP2 merge replication. The subscriber is also running SQL 2005 SP2. This was working without isssue until recently. It now gives me the following message each time I restart the synchronisation Error messages:Object referenced by the given @article or @artid '83E9E744-8D3D-47CA-8C07-08CA2589E6EA' could not be found. (Source: MSSQLServer, Error number: 20669) Get help: http://help/20669 Any assistance / direction would be most welcome. Thanks, Adam Thursday, August 13, 2009 3:48 AM Reply | Quote Answers 0 Sign in to vote Pls look in to http://social.msdn.microsoft.com/forums/en-US/sqlreplication/thread/0b72403b-06de-4990-992d-a3dbd3a759ce/ . This might give a picture of what the problem isThanks, Leks Marked as answer by Mark Han [MSFT] Tuesday, August 18, 2009 3:46 AM Friday, August 14, 2009 3:37 AM Reply | Quote Microsoft is conducting an online survey to understand your opinion of the Msdn Web site. If you choose to participate, the online survey will be presented to you when you leave the Msdn Web site.Would you like to participate? Privacy statement © 2016 Microsoft. All rights reserved.Terms of Use|Trademarks|Privacy Statement|Site Feedback
Recent PostsRecent Posts Popular TopicsPopular Topics Home Search Members Calendar Who's On Home » SQL Server 2008 » SQL Server 2008 - General » Scary Merge Replication issue Scary Merge Replication issue Rate Topic Display Mode Topic Options Author Message @SixStringSQL@SixStringSQL Posted Thursday, November 3, 2011 6:09 AM SSC Journeyman Group: General Forum Members Last Login: Tuesday, October 11, 2016 10:21 AM Points: 81, Visits: 366 Has anyone seen something like this before?I'm creating a replication infrastructure https://social.msdn.microsoft.com/Forums/sqlserver/en-US/d2d2aaab-6df5-42a7-b8a9-878cbc99fc8b/error-number-20669-synchronisation-wont-run?forum=sqlreplication almost identical to our successful 2005 implementation, using scripts generated from the '05 imp. Topology: One master, 6 republishers, 100 end-point CE subscribers. Two publications (one effectively download-only, one bi-directional).After applying the scripts and re-initializing the subscribers, I sit back and watch. After four hours, I have 30% of the devices synced up, and its looking good.Then, without warning, the following http://www.sqlservercentral.com/Forums/Topic1199835-391-1.aspx error: Object referenced by the given @article or @artid '1A616B5D-0C11-4CD1-A020-8A8D68874A19' could not be found. (Source: MSSQLServer, Error number: 20669). As I watch, the republishers start losing articles from the publication. In the end (perhaps half-an-hour), all six republishers are left with the two publications, but without any articles in them.Its happened twice now. Any ideas? I'm going to check the default trace, then pour over the scripts for any anomolies...TIA,Grubb Post #1199835 NJ-DBANJ-DBA Posted Thursday, November 3, 2011 7:04 AM SSC Eights! Group: General Forum Members Last Login: Wednesday, January 6, 2016 12:36 PM Points: 911, Visits: 1,546 Grubb (11/3/2011)Has anyone seen something like this before?I'm creating a replication infrastructure almost identical to our successful 2005 implementation, using scripts generated from the '05 imp. Topology: One master, 6 republishers, 100 end-point CE subscribers. Two publications (one effectively download-only, one bi-directional).After applying the scripts and re-initializing the subscribers, I sit back and watch. After four hours, I have 30% of the devices synced up, and its looking good.Then, without warning, the following error: Object referenced by the given @article or @artid '1A616B5D-0C11-4CD1
productResults.length + resourceResults.length > 0 ? 'See all Search Results' : 'Full site search'}} > > CA Support Online > Support by Product > Support by Product Post To WIP fails with Error 'REVMGR-20669:Error inserting matching records' Document ID:TEC571454 Last Modified Date:12/15/2015 {{active ? 'Hide' : 'Show'}} Technical Document Details Products CA http://www.ca.com/us/support/ca-support-online/product-content/knowledgebase-articles/tec571454.aspx?intcmp=searchresultclick&resultnum=1 PPM Releases CA PPM:Release:12.0 CA PPM:Release:12.1 CA PPM:Release:13.0 CA PPM:Release:14.3 On Premise CA PPM:Release:14.2 On Premise CA PPM:Release:14.1 On Premise CA PPM:Release:13.3 On Premise CA PPM:Release:13.1 On Premise CA PPM:Release:13.0 On Premise CA PPM:Release:13.1 CA PPM:Release:13.2 CA PPM:Release:13.2 On Premise CA PPM:Release:13.3 CA PPM:Release:14.1 CA PPM:Release:14.2 CA PPM:Release:12.1 On Premise Components CLARITY ON DEMAND FINANCIALS, TIME & DATA MANAGEMENT:ODTXCL CLARITY PPM FINANCIALS, TIME & DATA MANAGEMENT:PPMTRX Symptoms: error number When attempting to post transactions into WIP, an error message is generated. Steps to Reproduce: Login to the applicationas a Financial user Home, Post to WIP Click 'Apply' button Expected Result: The transactions should be posted without this error message. Actual Result: Post To WIP fails with Error 'REVMGR-20669:Error inserting matching records'. Cause: We queried the PPA_WIP table and found 2 records for the same transaction ; only error number 20669 difference is in the 'batch' number. Then we queried the PPA_WIP_VALUES table to see if both transactions have the matching 5 records. Only one of the PPA_WIP records had matching 5 records. We removed the orphaned PPA_WIP record and the posting action was successful for the valid record. This issue can be caused in a Microsoft SQL Server environment if the 'Post Transactions to Financials' job is interrupted due to Database problems such as out of space, transaction logs filling up or the job itself is interrupted. The job creates the header record and may be interrupted during the time that it needs to create the 5 matching records. Resolution: Orphan PPA_WIP record: The following query will show any record that is in PPA_WIP table, but no matching records in the PPA_WIP_VALUES table. No results indicate no problem. select wip.*from ppa_wip wip where wip.transno not in (select transno from ppa_wip_values) Incorrect Ratio of Records: Here is a query that shows there might be records in the PPA_WIP_VALUES table, but not all 5 records in the table. For the application to function properly, there must be a 1:5 ratio between PPA_WIP and PPA_WIP_VALUES tables. No results indicate no problem. select w.tra