Home Dashboard Directory Help

Hotfix 3460 (KB2977325) - only single log reader allowed at one time after installation by Andy Steinke


Status: 

Closed
 as Fixed Help for as Fixed


7
0
Sign in
to vote
Type: Bug
ID: 950118
Opened: 8/19/2014 8:12:30 AM
Access Restriction: Public
0
Workaround(s)
view
2
User(s) can reproduce this bug

Description

One of our licensee retail locations had their SQL 2012 Standard Edition set to automatically apply updates monthly. Hotfix 3640, KB2981580 was automatically downloaded and applied.

This SQL server is the source of several replication publications from several databases. After this update, we found that only one log reader agent at a time could be running. Any additional ones would error, saying another logreader agent for the subscription or subscriptions is running. Below is an example of the verbose output we received trying to start the log readers from the command line.

C:\Program Files\Microsoft SQL Server\110\COM>Logread.exe -Publisher [AFHS-ALBUN
MSQL\AFHS] -PublisherDB [CrossDock] -Distributor [AFHS-ALBUNMSQL\AFHS] -Distribu
torSecurityMode 1 -Continuous -Outputverboselevel 3

2014-08-18 14:33:27.633 Microsoft SQL Server Log Reader Agent 11.0.3460.0
2014-08-18 14:33:27.635 Copyright (c) 2008 Microsoft Corporation
2014-08-18 14:33:27.636
2014-08-18 14:33:27.636 The timestamps prepended to the output lines are express
ed in terms of UTC time.
2014-08-18 14:33:27.637 User-specified agent parameter values:
                        -Publisher AFHS-ALBUNMSQL\AFHS
                        -PublisherDB CrossDock
                        -Distributor AFHS-ALBUNMSQL\AFHS
                        -DistributorSecurityMode 1
                        -Continuous
                        -Outputverboselevel 3
2014-08-18 14:33:27.791 Status: 0, code: 1007, text: 'Another logreader agent fo
r the subscription or subscriptions is running, or the server is working on a pr
evious request by the same agent.'.
2014-08-18 14:33:27.792 Another logreader agent for the subscription or subscrip
tions is running, or the server is working on a previous request by the same age
nt.
2014-08-18 14:33:27.793 Status: 0, code: 22037, text: 'The last step did not log
any message!'.
2014-08-18 14:33:28.291 Disconnecting from OLE DB Publisher 'AFHS-ALBUNMSQL\AFHS
'

If we stopped the single working log reader agent, another one was able to work.

We went through several iterations of disabling publication and distribution and trying to set it back up, but we couldn't get past this point. When we tried to disable publication and distribution, we received an error saying "Only one Log Reader Agent or log-related procedure can connect to a database at a time..... (Error: 18752)", but the distribution database would be successfully destroyed.

Ultimately we were able to convince the licensee to uninstall the Hotfix.

After the Hotfix uninstallation, we were able to run multiple logreader agents again.

Details
Sign in to post a comment.
Posted by Microsoft on 8/29/2014 at 3:59 PM
The SQL Server 2012 SP1 hotfix (Build 11.0.3467.0) for this problem is now available for download at http://support.microsoft.com/kb/2975402.

Microsoft SQL Server Development Team
Posted by Microsoft on 8/20/2014 at 10:48 AM
Thank you for reporting this issue to Microsoft. We have confirmed this is an issue with SQL Server 2012 version 11.0.3460.0. To immediately fix this problem, you can upgrade the SQL Server instance to SQL Server 2012 Service Pack 2 (http://www.microsoft.com/en-us/download/details.aspx?id=43340). Another option is to wait for the SQL Server 2012 Service Pack 1 hotfix that will be released next week. This problem will also be fixed in the next Cumulative Update for SQL Server 2012 Service Pack 1.

Microsoft SQL Server Development Team
Posted by mkal55 on 8/19/2014 at 11:19 AM
This hotfix did exactly the same thing to us. Removing the hotfix immediately brought replication back online.

I had planned on removing it anyway but it was nice to have some confirmation.
Sign in to post a workaround.