I was reviewing our Exchange server event logs and came across the following event

Log Name:      Application
Source:        MSExchangeIS
Date:          8/13/2015 11:58:56 AM
Event ID:      10030
Task Category: Logical Data Model
Level:         Warning
Keywords:      Classic
User:          N/A
Computer:      SERVERNAME
Description:
Microsoft Exchange Information Store removed following properties (Contacts, Companies, LogType, TaskOwner) for mailbox (71635806-56f6-4462-9d51-db040eadf5ba) from search folder criteria.
  <System>
    <Provider Name="MSExchangeIS" />
    <EventID Qualifiers="32772">10030</EventID>
    <Level>3</Level>
    <Task>4</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2015-08-13T15:58:56.000000000Z" />
    <EventRecordID>11913061</EventRecordID>
    <Channel>Application</Channel>
    <Computer>EXCMBX01.Ourdomain.com</Computer>
    <Security />
  </System>
  <EventData>
    <Data>Contacts, Companies, LogType, TaskOwner</Data>
    <Data>71635806-56f6-4462-9d51-db040eadf5ba</Data>

I saw this entry a few times so I filtered on it and found that we had 70 instances of this in the last 24 hours. I am not sure if this is saying that we are having database corruption or that it is just updating some kind of search index. 

I went into powershell and ran the following command to help identify the user and database.

Get-Mailbox "GUIDFromEvent" | fl name, database

I noticed that all the users were from the same database. So I am not sure if this is saying something is wrong with that database or not.  I found the following link.

https://social.technet.microsoft.com/Forums/exchange/en-US/5e5f4837-6a9b-44af-bc33-e5a4b1839eeb/exchange-2013-server-1-down-in-sudden-and-event-id-10030-were-found?forum=exchangesvradmin

We are currently on Exchange 2013 Version 15.0 SP1

Has anyone else run into this? If so can you help shed some light on it?

Thanks

I would start updating with CU9 as CU4/SP1 is quite old now, was released in Feb last year. If you continue receiving same error after that then I would start looking further....

MS also recommends to update it asap or at least withing three months after the release of next cumulative update...

---- 

Q: How long is a CU supported?

A: A CU will be supported for a period of three (3) months after the release date of the next CU. For example, if CU1 is released on 3/1 and CU2 is released on 6/1, CU1 support will end on 9/1.

---- 

Servicing Exchange 2013 - http://blogs.technet.com/b/exchange/archive/2013/02/08/servicing-exchange-2013.aspx

Hi,

If this event persists after updating, please run the following commands to repair these mailboxes.

New-MailboxRepairRequest -Identity Mailbox -CorruptionType ProvisionedFolder,SearchFolder,AggregateCounts,Folderview

If this doesnt work, move these mailboxes to another new Mailbox Database to check this issue.

Best Regards.

In a perfect world I would be on the latest CU. Unfortunately, we don't live there yet. We have some custom applications that have not been updated yet so we are unable to install a more current CU. Does anyone have any idea what this message has to do with or whether this is something we need to address now?

Thanks

You can try Lynn's suggestion on repairing mailbox and see if it helps!

Does Anyone know what this message means?