PRB: Stored Procedure Still Marked for Replication May Cause Stack Dumps (272115)

SYMPTOMS

If replication has been uninstalled, executing a stored procedure that is still marked for replicaton may cause a stack dump:

Short Stack Dump
0x006baeec Module(sqlservr+2baeec) (ReplicateProcExecution+c4)
0x00531843 Module(sqlservr+131843) (CMsqlExecContext::SetupRepl+3e)
0x00414084 Module(sqlservr+14084) (CMsqlExecContext::Execute+14e)
0x004139b1 Module(sqlservr+139b1) (CSQLSource::Execute+231)
0x00518c3b Module(sqlservr+118c3b) (CStmtExec::XretLocalExec+126)
0x00518afa Module(sqlservr+118afa) (CStmtExec::XretExecute+253)
0x004145f1 Module(sqlservr+145f1) (CMsqlExecContext::ExecuteStmts+11a)
0x0041409f Module(sqlservr+1409f) (CMsqlExecContext::Execute+16a)

CAUSE

This problem can occur if replication does not uninstall completely, and the stored procedure remains marked for replication. Each time that the stored procedure is executed, a stack dump appears in the error log.

WORKAROUND

To confirm the replication status, check the replinfo column in the sysobjects table. If the stored procedure is marked for replication, the replinfo column has the value 8; if the procedure is not marked for replication, the value is 0.

To correct this problem, use the following stored procedure to change the value in the replinfo column from 8 to 0:

sp_configure 'allow updates', 1
go
reconfigure with override
go
update sysobjects set replinfo = 0 where name = 'object name' /*The stored procedure name is object name*/ 
go
sp_configure 'allow updates', 0
go
reconfigure with override
go