FIX: Logreader Tasks Not Upgraded from SQL Server 6.5 to 7.0 (217036)

SYMPTOMS

Logreader tasks are skipped during the upgrade process and transferred without upgrading. This does not result in a failed upgrade or any task misbehaviors, but it does affect Replication Monitoring in SQL Server 7.0.

CAUSE

The problem is caused by an incorrect value in a CASE statement in the sp_MSfix_6x_tasks stored procedure. The word "logReader" should be spelled out in lowercase letters.

WORKAROUND

To work around this problem, correct the spelling of "logreader". Open the sp_MSfix_6x_tasks stored procedure in the master database on the SQL Server 7.0 server. Look for the following section in sp_MSfix_6x_tasks:

-- Get Distribution category name (assumes category_id = 10)
                                select @category_id =
                                        case lower(@sSubsystem) 
                                                when 'snapshot' then 15
                                                when 'distribution' then 10
                                                when 'logReader' then 13           
                                                else 0
                                        end

Change "logReader" to "logreader", drop and re-create the procedure, and then run it to update Logreader tasks to be properly controlled using Replication Monitor.

STATUS

Microsoft has confirmed this to be a problem in SQL Server 7.0. This problem has been corrected in U.S. Service Pack 1 for Microsoft SQL Server 7.0. For more information, click the following article number to view the article in the Microsoft Knowledge Base:

232570INF: How to Obtain Service Pack 1 for Microsoft SQL Server 7.0 and Microsoft Data Engine (MSDE) 1.0

For more information, contact your primary support provider.