August 10, 2009 at 9:50 am
Hi,
We got Publisher and Subscrber on W2003 R2 with SQL Server 2005 Ent. SP3 CU#1
This is simple replication were Distributor as well Log Reader agents are on Subscriber.
Yesterday we got following errors in Log Reader, and it unable to start it.
Status: 0, code: 20011, text: 'The process could not execute 'sp_replcmds' on 'PUBLISHER'.'.
Status: 0, code: 18773, text: 'Could not locate text information records for the column "COLUMN_NAME", ID 16 during command construction.'.
Status: 0, code: 18805, text: 'The Log Reader Agent failed to construct a replicated command from log sequence number (LSN) {00034a38:000002d4:0055}. Back up the publication database and contact Customer Support Services.'.
Status: 0, code: 22037, text: 'The process could not execute 'sp_replcmds' on 'PUBLISHER'.'
We found a lot of KB articles, but non of them are for this version or patch level.
- KB 952330 as a Product bug and resolved in Service Pack 2 Cumulative Update 8. We got higher version of SQL Server
- KB 276281 as a Product bug but in SQL Server 7.0. Resolved by a hot fix. We got different version of SQL Server.
- KB 958684 as a Product bug and resolved by apply CU1 for SQL Server 2005 SP3. We already got that version.
- KB 933519 as a Product bug and resolved by apply CU2 for SQL Server 2005 SP2. We got higher version.
- KB 971136 as a Product bug and resolved by apply SP1 for SQL Server 2008. We got different version of SQL Server.
Any ideas? 🙂
August 11, 2009 at 7:18 am
Way out of my league. I think you should contact Microsoft Support.
-Roy
June 2, 2010 at 8:50 am
Did you ever find a fix for this? It is happening for us now.
Owner & Principal SQL Server Consultant
Im Your DBA, Inc.
https://www.imyourdba.com/
June 2, 2010 at 10:32 am
Yes, we got cure fot that from Microsoft Support as I remember that was a Product Bug, I will try to find out how we resolve it, give me few hours or contact Support.
June 3, 2010 at 1:53 am
April 18, 2012 at 10:46 pm
lazarusek (6/3/2010)
Hi again,He got holidays here, so apologize for a delay. I found the workaround on my blog that I created a long time ago. Hope it will help you with the issue.
http://sqldba.pl/2009/10/log-reader-error-20011-18773-18805/[/url]
I am unable to get this this link above. I am experiencing the same issue. It occurred after I dropped then readded a single article from a Publication in a transactional replication environment.
Does anyone have any suggestions???
______________________________________________________________________________Never argue with an idiot; Theyll drag you down to their level and beat you with experience
Viewing 6 posts - 1 through 5 (of 5 total)
You must be logged in to reply to this topic. Login to reply