Turned off Circular Logging within an DAG Environment - now getting an Event ID 2137 (Exchange 2010)

Question

We haven't reboot each node yet, so we are thinking that might correct this warning, it appears that the passive copies are working correctly.
The event ID 2137 is the following:
Log Name:      Application
Source:        MSExchangeRepl
Date:          4/19/2011 9:01:31 PM
Event ID:      2137
Task Category: Service
Level:         Warning
Keywords:      Classic
User:          N/A
Computer:      XXXXXXXXXXX
Description:
RPC request to the Microsoft Exchange Information Store service for log truncation failed for database XXXXXX\XXXXXXX. Error: 4294965485.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="MSExchangeRepl" />
    <EventID Qualifiers="32772">2137</EventID>
    <Level>3</Level>
    <Task>1</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2011-04-20T01:01:31.000000000Z" />
    <EventRecordID>240357</EventRecordID>
    <Channel>Application</Channel>
    <Computer>XXXX.XXX.XXX</Computer>
    <Security />
  </System>
  <EventData>
    <Data>XXXXX\XXXXXX</Data>
    <Data>4294965485</Data>
  </EventData>
</Event>

Answer 1

FWIW, we had the same exact issue and running a full backup resolved it. To clarify the exact steps a bit, disabling circular logging was the only activity performed. We did
not have to dismount any databases, activate passive copies, restart IS, reseed, modify the registry or anything of the sort. Following this, we ran a full backup using a 3rd party solution with an Exchange agent (Backup Exec), not Windows
Server Backup, so I can't vouch whether or not there's a difference there. The backup job was configured to auto-select the best copy available, which ended up targetting a passive copy, so there doesn't seem to be a dependency on backing up specifically from
an active vs a passive copy. After the full backup completed, the warnings never re-emerged.