Error Number 22017
Contents |
(Русский)ישראל (עברית)المملكة العربية السعودية (العربية)ไทย (ไทย)대한민국 (한국어)中华人民共和国 (中文)台灣 (中文)日本 (日本語) HomeLibraryLearnDownloadsTroubleshootingCommunityForums Ask a question Quick access Forums home Browse forums users FAQ Search related threads Remove From My Forums Answered by: Log Reader Error: The process could not execute 'sp_repldone/sp_replcounters' SQL Server the process could not set the last distributed transaction. > SQL Server Replication Question 0 Sign in to vote I have transactional sp_replrestart replication going between servers A and B. SQL Server 2005 64 bit A is Publisher B is Distributor and
Sp_repldone Example
Subscriber Now I am getting the following Log reader Agent Error Msg The process could not execute 'sp_repldone/sp_replcounters' on 'A'. (Source: MSSQL_REPL, Error number: MSSQL_REPL20011) Get help: http://help/MSSQL_REPL20011 Only one Log
The Process Could Not Execute 'sp_repldone/sp_replcounters' On
Reader Agent or log-related procedure (sp_repldone, sp_replcmds, and sp_replshowcmds) can connect to a database at a time. If you executed a log-related procedure, drop the connection over which the procedure was executed or execute sp_replflush over that connection before starting the Log Reader Agent or executing another log-related procedure. (Source: MSSQLServer, Error number: 18752) Get help: http://help/18752 The process could not set sp_replrestart running long the last distributed transaction. (Source: MSSQL_REPL, Error number: MSSQL_REPL22017) Get help: http://help/MSSQL_REPL22017 The process could not execute 'sp_repldone/sp_replcounters' on 'A'. (Source: MSSQL_REPL, Error number: MSSQL_REPL22037) Get help: http://help/MSSQL_REPL22037 Can anybody help me in solving this issue? I read that we have to delete the existing publication and subscription. Is there any way to solve this problem without deleting the existing subscription and publication Any help would be appreciated Thanks Wednesday, January 24, 2007 7:53 AM Reply | Quote Answers 0 Sign in to vote Yes. You need to kill the process as only one logreader should work again a certain publication database. If that process is started by SQLagent, you might need to find the job and delete the job. Thanks, Peng Wednesday, January 24, 2007 9:48 PM Reply | Quote All replies 0 Sign in to vote Hi Vjai, I think the error message is very clear. Have you or other people run any of the log-related procedure at the same time? Thanks, Peng Wednesday, January 24, 2007 7:53 PM Reply | Quote 0 Sign in to vote No Peng, we didnt run any log related
Download (Sql Server Error Number 22017) Repair Tool Step 2: Click the "Scan" button
Source: Mssql_repl, Error Number: Mssql_repl20011
Step 3: Click 'Fix All' and you're done! Compatibility: Windows sp_replflush 7, 8, Vista, XP Download Size: 6MB Requirements: 300 MHz Processor, 256 MB Ram, 22 MB HDD Limitations: the specified lsn for repldone log scan is not a replicated commit record This download is a free evaluation version. To unlock all features and tools, a purchase is required. Sql Server Error Number 22017 Error Codes are caused in one way or https://social.msdn.microsoft.com/Forums/sqlserver/en-US/77165186-b53d-401f-8f7f-f92019e160c8/log-reader-error-the-process-could-not-execute-sprepldonespreplcounters?forum=sqlreplication another by misconfigured system files in your windows operating system. If you have Sql Server Error Number 22017 errors then we strongly recommend that you Download (Sql Server Error Number 22017) Repair Tool. This article contains information that shows you how to fix Sql Server Error Number 22017 both (manually) and (automatically) , In addition, this article will help you troubleshoot http://sql.server.error.number.22017.winwizards.org/ some common error messages related to Sql Server Error Number 22017 error code that you may receive. Note: This article was updated on 2016-10-08 and previously published under WIKI_Q210794 Contents 1.What is Sql Server Error Number 22017 error? 2.What causes Sql Server Error Number 22017 error? 3.How to easily fix Sql Server Error Number 22017 errors What is Sql Server Error Number 22017 error? The Sql Server Error Number 22017 error is the Hexadecimal format of the error caused. This is common error code format used by windows and other windows compatible software and driver vendors. This code is used by the vendor to identify the error caused. This Sql Server Error Number 22017 error code has a numeric error number and a technical description. In some cases the error may have more parameters in Sql Server Error Number 22017 format .This additional hexadecimal code are the address of the memory locations where the instruction(s) was loaded at the time of the error. What causes Sql Server Error Number 22017 error? The Sql Server Error Number 220
up Recent PostsRecent Posts Popular TopicsPopular Topics Home Search Members Calendar Who's On Home » SQL Server 7,2000 » Replication http://www.sqlservercentral.com/Forums/Topic105590-7-1.aspx » The process could not execute... 12 posts,Page 1 of 212»» The process could not execute sp_repldone/sp_replcounters Rate Topic Display Mode Topic Options Author Message bozo7bozo7 Posted Thursday, March 11, 2004 9:26 AM SSC Veteran Group: General Forum Members Last Login: Thursday, March 15, 2007 9:22 AM Points: 238, Visits: 1 We are getting the following error on all of the repliction from one server:The process error number could not execute 'sp_repldone/sp_replcounters' Is there a good way to fix it? It all worked until last night when someone executed an update the affected 7 million rows. We have since taken replication off that database. But all the other databases have since had this error.The agent is also giving this error:The process could not set the last distributed transaction.Please help!Thanks,Ross Post #105590 TriggerMeTriggerMe Posted Thursday, March the process could 11, 2004 4:29 PM SSC Eights! Group: General Forum Members Last Login: Thursday, September 8, 2016 7:13 PM Points: 872, Visits: 328 Did the UPDATE on 7 million rows work?If it didn't, did the transaction log run out of space? Also check the transaction log on the Distribution Databases. Kindest Regards, Post #105698 bozo7bozo7 Posted Friday, March 12, 2004 9:04 AM SSC Veteran Group: General Forum Members Last Login: Thursday, March 15, 2007 9:22 AM Points: 238, Visits: 1 The update did work. The problem now is that we have so many transactions that the log reader agents are timing out trying to read them. We have been on the phone with MS PSS and they have been somewhat of a help, but so far there ideas have not worked.Ross Post #105848 bozo7bozo7 Posted Monday, March 15, 2004 9:52 AM SSC Veteran Group: General Forum Members Last Login: Thursday, March 15, 2007 9:22 AM Points: 238, Visits: 1 Well we go our issue taken care of. It was not pretty. Here is the lowdown. Essentially we overloaded replication with an update that affected 7 million rows, along with several other process that were updating lots of rows