Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
Question
Thursday, March 23, 2017 1:25 PM
We recently migrated our users from Exchange 2013 to Exchange 2016. I began to see these warnings shortly after the users were on the Exchange 2016 servers. They showed up after I rebooted for patching. I've been trying to find information on them but there doesn't seem to be a lot out there. Is anyone else seeing these on Exchange 2016 CU3? The nature of the error is making me worry about some type of corruption in the databases but all active databases are "Mounted" and the copies are "Healthy". The indexes are all "Healthy" as well.
Here is the full warning from event viewer: This warning is on a copy of a database.
Log Name: Application
Source: ESE
Date: 3/22/2017 12:18:01 PM
Event ID: 733
Task Category: Online Defragmentation
Level: Warning
Keywords: Classic
User: N/A
Computer: XXXXXX.contoso.com
Description:
Information Store - DBXXX (224) DBXXX: Online Maintenance Database Checksumming background task is not finishing on time for database 'D:\DBXXX\DBXXX.edb'. This pass started on 3/8/2017 and has been running for 1209600 seconds (over 14 days) so far.
For more information, click httpLink.
Event Xml:
<Event xmlns=httplink
<System>
<Provider Name="ESE" />
<EventID Qualifiers="0">733</EventID>
<Level>3</Level>
<Task>10</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2017-03-22T17:18:01.000000000Z" />
<EventRecordID>2189347</EventRecordID>
<Channel>Application</Channel>
<Computer>XXXXXX.contoso.com</Computer>
<Security />
</System>
<EventData>
<Data>Information Store - DBXXX</Data>
<Data>224</Data>
<Data>DBXXX: </Data>
<Data>D:\DBXXX\DBXXX.edb</Data>
<Data>3/8/2017</Data>
<Data>1209600</Data>
<Data>14</Data>
</EventData>
Any assistance would be greatly appreciated!
All replies (3)
Friday, March 24, 2017 8:19 AM
Hi,
This event indicates that database scanning checksums the database for more than 14 days. After this event, can you see other events indicate that the scanning is completed? Like 735,736,737? If yes, we can safely ignore this event.
Best Regards,
Lynn-Li
TechNet Community Support
Please remember to mark the replies as answers.
If you have feedback for TechNet Subscriber Support, contact [email protected].
Friday, March 24, 2017 4:13 PM
Thank you Lynn-Li! I filtered the App log by ESE (ESE) and found the following warnings only. It looks like we might have to increase the amount of time our online maintenance runs from the default?
Log Name: Application
Source: ESE
Date: 3/24/2017 3:40:12 AM
Event ID: 629
Task Category: Performance
Level: Warning
Keywords: Classic
User: N/A
Computer: XXXXXX.contoso.com
Description:
Information Store - DBXXXX (25384) DBXXXX: Database 'D:\DBXXXX\DBXXXX.edb': While attempting to move to the next or previous node in a B-Tree, the database engine took 2.154 milliseconds (waiting 0.000 milliseconds on faults) to skip over 11863 non-visible nodes in 47 pages (faulting in 0 pages). In addition, since this message was last reported 102 hours ago, 247 other incidents of excessive non-visible nodes were encountered (a total of 10685 nodes in 12350 pages were skipped) during navigation in this B-Tree. It is likely that these non-visible nodes are nodes which have been marked for deletion but which are yet to be purged. The database may benefit from widening the online maintenance window during off-peak hours in order to purge such nodes and reclaim their space. If this message persists, offline defragmentation may be run to remove all nodes which have been marked for deletion but have yet to be purged from the database.
Name: Events
Owning Table: Events
ObjectId: 12
PgnoRoot: 66
Type: 2
Unversioned Deletes: 0
Uncommitted Deletes: 0
Committed Deletes: 0
Non-Visible Inserts: 11863
Filtered: 0
Dbtime Distrib: 644505843, 644511851, 644517712 (635048604)
For more information, click http:.
Event Xml:
<Event xmlns="http">
<System>
<Provider Name="ESE" />
<EventID Qualifiers="0">629</EventID>
<Level>3</Level>
<Task>7</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2017-03-24T08:40:12.000000000Z" />
<EventRecordID>2210665</EventRecordID>
<Channel>Application</Channel>
<Computer>XXXXXX.contoso.com</Computer>
<Security />
</System>
<EventData>
<Data>Information Store - DBXXXX</Data>
<Data>25384</Data>
<Data>DBXXXX: </Data>
<Data>D:\DBXXXX\DBXXXX.edb</Data>
<Data>Events</Data>
<Data>Events</Data>
<Data>11863</Data>
<Data>47</Data>
<Data>12</Data>
<Data>66</Data>
<Data>2</Data>
<Data>0</Data>
<Data>0</Data>
<Data>0</Data>
<Data>11863</Data>
<Data>102</Data>
<Data>247</Data>
<Data>10685</Data>
<Data>12350</Data>
<Data>0</Data>
<Data>2.154</Data>
<Data>0.000</Data>
<Data>0</Data>
<Data>644505843, 644511851, 644517712 (635048604)</Data>
</EventData>
</Event>
Do you agree?
Thanks!
Suzy
Friday, March 31, 2017 6:50 PM
Suzy, I believe that the information in that eventlog message is outdated when it refers to adjusting the maintenance window- I'm pretty sure ex2013 and later does background maintenance 24x7 on its databases. For what it's worth, I get similar warnings on mine all the time. I'm hoping maybe they're going to fix it in a future update...