asked on

Exchange 2010 Event ID 629 problems

Hi guys

We are seeing the following at a couple of clients sites with regards to Exchange 2010;

Log Name: Application
Source: ESE
Date: 23/01/2012 13:21:47
Event ID: 629
Task Category: Performance
Level: Warning
Keywords: Classic
User: N/A
Computer: Exchange_Server.Domain_Name.local
Description:
Information Store (3312) Mailbox Database: Database 'D:\Program Files\Microsoft\Exchange Server\V14\Mailbox\Mailbox Database 0421889199\Mailbox Database 0421889199.edb': While attempting to move to the next or previous node in a B-Tree, the database engine skipped over 17117996 non-visible nodes in 50789 pages. In addition, since this message was last reported 1 hours ago, 22 other incidents of excessive non-visible nodes were encountered (a total of 682859 nodes in 95750 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: MSysObjects
Owning Table: MSysObjects
ObjectId: 2
PgnoRoot: 4
Type: 2
Unversioned Deletes: 17117996
Uncommitted Deletes: 0
Committed Deletes: 0
Non-Visible Inserts: 0

Anyone seen this before ? It has the effect of increasing the database size by many Gb's.

It's a virtual server running Windows 2008 R2.

The maintenance window runs between 12-6am each night, so we think this should have enough time to complete ? The online backup didn't run until after this window & that's when it added another 9Gb to the database causing it to dismount (due to lack of disk space).

Any pointers would be appreciated.

saravana_the_expert

hi, see if you get the error message for all the databases or for just one particular database. If it is only for a particular database, run the following command

New-MailboxRepairRequest -Database <db name> -CorruptionType ProvisionedFolder,SearchFolder,AggregateCounts,Folderview

This will clear the corruptions that are present in that particular database

saravana_the_expert

refer link for mailbox repair request: http://technet.microsoft.com/en-us/library/ff625226.aspx

saravana_the_expert

are there any CRM users who are present in the databases??

tfinding

ASKER

Thanks for your response.

It mentions mailbox access it disrupted - does that mean no access or just slowness, do you know ?

All 3 clients who are experiencing this issue use CRM - is this a common issue ?

Many thanks

ASKER CERTIFIED SOLUTION

saravana_the_expert

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial

tfinding

ASKER

Many thanks for the above

I'll investigate the CRM clients & see what level they are at.

Regards

tfinding

ASKER

Thank you very much for the pointer with CRM - I believe this has been the culprit (although it's early days).

The 3rd party who look after the CRM for our clients have confirmed pretty much the same thing;

"The Exchange 2010 server can create huge log files that has the potential to bring it down. Please note this is a known issue with a known solution.

It is essential that the CRM applications server and all client PCs with the CRM Outlook client installed are on at least update rollup 17."

Therefore, there is much scrambling at the moment to ensure this is adhered to, whilst dodging the questions as to why they haven't been updated on a regular basis!

Will awards the points now - many thanks again.

tfinding

ASKER

This seems to be a know issue with the database having CRM clients,
found these articles

http://social.microsoft.com/Forums/en/crm/thread/6fba6c7f-c514-4e4e-8a2d-7e754b647014
http://social.technet.microsoft.com/Forums/hu/exchange2010/thread/f8157b1c-e30a-4ed9-9c82-accda93bccb1

- Update the CRM to update 20 or at least to update 17.