.NET Tutorials, Forums, Interview Questions And Answers
Welcome :Guest
Sign In
Win Surprise Gifts!!!

Top 5 Contributors of the Month
Gaurav Pal
Post New Web Links

transcation replication failing -- log reader

Posted By:      Posted Date: September 20, 2010    Points: 0   Category :Sql Server
our replication is failing and error message is as below. We used to get this one fixed by increasing the query timeout value and reducing the read batch size value. But it did not work the last two times we tired. our version is sql server standard edition sp3. any idea on this would be of great help.

Error messages:
The process could not execute 'sp_replcmds' on 'server name'. (Source: MSSQL_REPL, Error number: MSSQL_REPL20011)
Get help: http://help/MSSQL_REPL20011
A system assertion check has failed. Check the SQL Server error log for details. Typically, an assertion failure is caused by a software bug or data corruption. To check for database corruption, consider running DBCC CHECKDB. If you agreed to send dumps to Microsoft during setup, a mini dump will be sent to Microsoft. An update might be available from Microsoft in the latest Service Pack or in a QFE from Technical Support.  (Source: MSSQLServer, Error number: 3624)
Get help: http://help/3624
The process could not execute 'sp_replcmds' on 'server name'. (Source: MSSQL_REPL, Error number: MSSQL_REPL22037)
Get help: http://help/MSSQL_REPL22037

View Complete Post

More Related Resource Links

Replication Failing, because log file is full


I am having a problem with replication between 2 databases.  Here is some context on the setup.

I have 2 database servers, which are both running SQL Server 2005.  Each database server contains a database called CRIS_TEST_ARCHIVE, these databases are setup as replication subscriber and publisher and replication has been running flawlessly so far.

As part of a project, we are archiving a lot of data, ie, removing it from the CRIS_TEST_ARCHIVE database and putting it into a different database.  the export went fine, and I am partway through the step of deleting the redundant data from the current database.  This involves deleting a lot of rows from the source database and then running replication to ensure that the deleted rows also get deleted from the other replicated database.

I am running the deletes for each table one by one, and then running replication manually.

After one particularly large delete (about 9 million rows) i again started replication and got the following error in the replication manager:


Error messages:
The Merge Agent was unable to update information about the last synchronization at the Subscriber. Ensure that the subscription exists at the Subscriber, and restart the Merge Agent.  (Source: MSSQL_REPL, Error number: MSSQL_REPL-2147199481)

Replication issue - Log Reader stuck on Initializing urgent!!


Log Reader stuck on Initializing, I have SQL server 2008, and the transactions are not getting replicated to subscriber. Any ideas!!


log reader agent stopped in transactional replication


hello frnds

I got this error in transactional replication in sql server

Error:The process could not execute 'sp_repldone/sp_replcounters' on 'FS001XSSQL110'. (Source: MSSQL_REPL, Error number: MSSQL_REPL20011)

Get help: http://help/MSSQL_REPL20011

The log scan number (54862:18189:10) passed to log scan in database 'Affinity' is not valid. This error may indicate data corruption or that the log file (.ldf) does not match the data file (.mdf). If this error occurred during replication, re-create the publication. Otherwise, restore from backup if the problem results in a failure during startup. (Source: MSSQLServer, Error number: 9003)

Get help: http://help/9003

The process could not set 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 'FS001XSSQL110'. (Source: MSSQL_REPL, Error number: MSSQL_REPL22037)

Get help: http://help/MSSQL_REPL22037

this is what i am getting when i viewed the log reader agent in replication monitor.



Updatable Transactional replication, Queue Reader error


I have just started getting the following error from the queue reader but I can't see why.


The Queue Reader Agent has encountered the error ''Row handle is invalid.'' when connecting to ''Database'' on ''ServerName''. Ensure that the publication and subscription are defined properly and that both servers are running.


Does anybody know what it means / how I can fix the problem?



Replication Log Reader Agent Error - No Information


SQL Server 2005 SP3, I have created an Oracle Publication for transactional replication.  All seems to be working, even getting transaction updates from Oracle. In replication monitor Log Reader Agent status is "Error".  Last action is "applying retries....".  When I view details, window is empty - though once before (when I saw details), details told me to check job history.  Job history shows - "The replication agent encountered an error and is set to restart within the job step retry interval. See the previous job step history message or Replication Monitor for more information."

I understand that the Log Reader is moving data change info to distribution and it seems important to understand the errors.  The Log Reader agent is using the SQL Agent Service Account.

Log Reader Agent profile properties are default.

Here are details of error:

Details in job step message:

Date  10/29/2010 11:23:54 AM
Log  Job History (PULPDEV-PULPDEV-19)

Step ID  2
Step Name  Run agent.
Duration  01:06:07
Sql Severity  0
Sql Message ID  0
Operator Emailed  
Operator Net sent  

SQL Server Mobile 2005 Merge replication failing over SSL, but can browse through pocket IE.


Hi All, this system is scheduled to go live in near to a day... but i have hit an issue when switching on SSL.  Any help would be greatly appreciated.


Device Env:

Windows Mobile 5.0 + Messaging and Security Feature Pack

SQL Server Mobile 2005.


Merge replication works fine without SSL.  After running the Configure Web Sync wizzard to setup SSL merge replication no longer works.  Note i checked using pocket IE by browsing to https://mycompany.com/pub/sqlcesa30.dll?diag and all worked fine.  There was no prompt saying the cert was bad etc.


The certificate is a:

Equifax secure global ebusiness CA-1 cert.

Signature algorithm md5RSA

public key RSA(1024 bits)

thumbprint algorithm sha1


Stacktrace given is:

-  ex {"A request to send data to the computer running IIS has failed. For more information, see HRESULT."} System.Data.SqlServerCe.SqlCeException
-  Errors {System.Data.SqlServerCe.SqlCeErrorCollection} System.Data.SqlServerCe.SqlCeErrorCollection
  Count 1 Integer

Use Camera as Barcode Reader

some important links



reader.getordinal("column_may_not_exist") how to catch the exception?



would any body please help me to catch the exception if the column doesnot exist as my table columns are not static.

sometimes its throwing me indexoutofrange exception as the column doesnot exist

thanks for the help guys

Web Deployment - Setup failing - aspnetca.exe


I have created websetup in windows 7 environment, asp.net 3.5, IIS 7.

Client System is windows 7 and IIS 7

Our client configuration is Windows 7, IIS7 dotNet Framework 3.5.
Following error raising below...
Faulting application name: aspnetca.exe, version: 7.5.7600.16385, time stamp: 0x4a5bcd3c
Faulting module name: aspnetca.exe, version: 7.5.7600.16385, time stamp: 0x4a5bcd3c
Exception code: 0xc0000005
Fault offset: 0x0001d912
Faulting process id: 0xe80
Faulting application start time: 0x01cb3604624975cd
Faulting application path: C:\Windows\system32\inetsrv\aspnetca.exe
Faulting module path: C:\Windows\system32\inetsrv\aspnetca.exe
Report Id: a05d368d-a1f7-11df-8336-4487fc612414
PFA Here I"m attaching custom action script. 

Concurrent Affairs: Reader/Writer Locks and the ResourceLock Library


If multiple threads concurrently execute code that writes to or modifies a resource, then obviously the resource must be protected with a thread synchronization lock to ensure that the resource doesn't get corrupted.

Jeffrey Richter

MSDN Magazine June 2006

Editor's Note: Reader E-mail


Here at MSDN Magazine, we get a lot of mail from readers. As you can imagine, much of it involves fulsome praise for our content, our eye-catching covers, or the handsome photo that now graces this page.

Joshua Trupin

MSDN Magazine June 2005

ASMX ws: An unexpected error occurred on a receive; failing intermittently



we I have asmx web service, this seems to be working fine for 25 client machines but one site keeps failing. The client gets a small dataset and tries to send it across to server to process. The dataset saved in XML file only makes 450 - 550kB. The web service is contacted twice in a short time every half an hour. The other smaller dataset (50kB) goes across everytime without any troubles. This site is not trying to send the biggest dataset, other site are sending much bigger datasets without problem. The catch is this failing site keeps retrying for 20 times (10 hours) in average and then eventually goes across. I don't think the service webmethod is erroring out as that is all wrapped up in the try and catch and the exception is not getting thrown, also every other try for the exact same webmethod used by any other client site seems to be working fine.

System.Net.WebException: The underlying connection was closed: An unexpected error occurred on a receive. ---> System.IO.IOException: Unable to read data from the transport connection: An existing connection was forcibly closed by the remote host. ---> System.Net.Sockets.SocketException: An existing connection was forcibly closed by the remote host
   at System.Net.Sockets.Socket.Receive(Byte[] buffer, Int32 offset, Int32 size, SocketFlags socketFlags)
   at System.Ne

Linq2Sql error: "Invalid attempt to call Read when reader is closed."


I've read up on this error from other posts and on other sites, but haven't found a solid resolution to the issue yet. My setup is as follows:

I have a RepositoryBase class that fields certain db calls that all repositories need to perform. In one such call, "GetSecurityGroup", it works most of the time, but will seemingly at random throw an exception with the error "Invalid attempt to call Read when reader is closed." All other Repository classes inherit from this one, and they all use the same DataContext object, which I understand isn't thread safe. Since there could be multiple calls to the DataContext object on the same page, perhaps one is using the DataContext when the next tries to do so. I'm not sure. What can I do to ensure this doesn't happen?

SQL Server 2008 - Job Activity Monitor Failing

I recently began migrating to Windows 2008. One of the first servers is a server which we install our tools on. This is a new server which currently is only running the SQL Server management tools. On this server I installed the SQL Server 2008 R2 management tools, prior to this install there were no other SQL Server tools installed on this server. The majority of the functionality works and I can connect and manage multiple databases servers from SQL Server version 2000 through 2008. But when I try to bring up the Job Activity monitor I get an error ==> Can not show requested dialog. From Windows XP Windows Server 2003 SP2 this functionality works. I get this error if I connect to a SQL Server 2005 or 2008 database instance. I have tried re-installing the client tools but I still get this error..... any ideas?

SQL Server Network Interfaces Error 26 - while failing over SQL Server 2008 R2

Before I explain the issue I am facing, I would like to say that I did read the post at  http://blogs.msdn.com/b/sql_protocols/archive/2007/05/13/sql-network-interfaces-error-26-error-locating-server-instance-specified.aspx but in my case the problem is transient (lasts for approximately two minutes after a failover) so items 1-3 in the list of troubleshooting steps do not seem to make sense. As to 4 and 5, the named instances use non-default ports (2433 and 3433 respectively), so I do not know how to tailor the PortQry command for that. I tried  portqry.exe -n ServerA,2433-p UDP -e 1434 and  portqry.exe -n ServerA,2433 -p UDP -e 2434 and it failed both times with a "Failed to resolve name to IP address" while the server was up and serving database requests The same thing happened when I tried it with the failover server as well. ***The issue I am facing*** I am using Enterprise Library 4.1 to connect to a SQL Server 2008 R2 database with a mirror. My connection string itself is as below (with dummy values for all fields): "Data Source=ServerA;Failover Partner=ServerB;Initial Catalog=DBName;User ID=uid;Password=pwd;Connect Timeout=5" Sample .NET code is as below (with modifications to instantiate all variables locally to provide context): SqlDatabase db = new SqlDatabase(ConnectionString); SqlConnection cn = (SqlConnection)db
ASP.NetWindows Application  .NET Framework  C#  VB.Net  ADO.Net  
Sql Server  SharePoint  Silverlight  Others  All   

Hall of Fame    Twitter   Terms of Service    Privacy Policy    Contact Us    Archives   Tell A Friend