We help IT Professionals succeed at work.
Get Started

Replication Issue

937 Views
Last Modified: 2012-08-27
Hi, I am facing an issue while configuring replication on one of the databases on server getiing replicated.
All the other replication are working normally.

Recently data type of one of the column of the table involved in replication was changed from varchar(32) to nvarchar(32)
and a unique non clustered index was added to the same table.

But since yesterday the log reader fails to start and gives the below error.

The process could not execute 'sp_replcmds' on 'servername'.

I tried recreating publication and the subscriber but to no success.

I also decreased the Query Timeout and the Batch Read value still am getting the same error.

I ran dbcc checkdb on the database but there were no errors.

We have SQL Server 2008 R2 Standard edition with latest service pack.

Error messages:
The process could not execute 'sp_replcmds' on 'servername'. (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 'servername'. (Source: MSSQL_REPL, Error number: MSSQL_REPL22037)
Get help: http://help/MSSQL_REPL22037.

It creates a SQL dump file :

External dump process return code 0x20002001.
The error information has been submitted to Watson error reporting.2012-08-16 02:33:15.14 spid87      Error: 17066, Severity: 16, State: 1.
2012-08-16 02:33:15.14 spid87      SQL Server Assertion: File: <replrowset.cpp>, line=2184 Failed Assertion = '(LSN)m_curLSN < (LSN)(pSchemas->schema_lsn_begin)'. This

error may be timing-related. If the error persists after rerunning the statement, use DBCC CHECKDB to check the database for structural integrity, or restart the

server to ensure in-memory data structures are not corrupted.
2012-08-16 02:33:15.14 spid87      Error: 3624, Severity: 20, State: 1.
2012-08-16 02:33:15.14 spid87      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.

Please advise
ERRORLOG.txt
Comment
Watch Question
IT Consultant
Commented:
This problem has been solved!
Unlock 1 Answer and 8 Comments.
See Answer
Why Experts Exchange?

Experts Exchange always has the answer, or at the least points me in the correct direction! It is like having another employee that is extremely experienced.

Jim Murphy
Programmer at Smart IT Solutions

When asked, what has been your best career decision?

Deciding to stick with EE.

Mohamed Asif
Technical Department Head

Being involved with EE helped me to grow personally and professionally.

Carl Webster
CTP, Sr Infrastructure Consultant
Ask ANY Question

Connect with Certified Experts to gain insight and support on specific technology challenges including:

  • Troubleshooting
  • Research
  • Professional Opinions
Did You Know?

We've partnered with two important charities to provide clean water and computer science education to those who need it most. READ MORE