I would really like to get rid of these events! Everything I read says they can be safely ignored. Thats all fine and dandy, but if they are safe and can be ignored then why cant they be removed from displaying at all.My logging is turned off so my next question is, can i disable or suppress these alerts in the regitry somewhere? I understand doing so may not recommended but I dont want to be seeing these alerts.

Clarify: exchange server got event 1173 in application log Collect info: 1. Version: Windows Server, Exchange 2. Is your error as same described in KB 913126? Explanation for event: Theres an Error 0x6BB that shows in Description section of the event. Error 0x6BB corresponds to ecObjectLocked it definitely looks like the warnings are logged when online maintenance is trying to delete a restricted view that is locked [unused views will be deleted if not used for a specified amount of time]. We also can't tell whos locking the current view; background threads could be locking the folder This lock symptom may be caused by that the folder is in use by other processes, because users still access store while server is doing the maintenance, so view may be locked by these users and cannot be maintained, then server will try to delete in next maintenance if none access. And then if maintenance completes successfully, the views should be deleted and we wouldnt see event after that Workaround: (The only way to get them not logged at all would be to request a change for Product, which would not be the option unless it was causing a serious issue in environment) Perform an offline defragment to avoid more such event logging 1. Dismount store 2. Start->run->command->cd PathOfEseutilTool 3. Esetuil /d "X:\Program Files\Exchsrvr\mdbdata\priv1.edb" 4. Mount again

Hi, CanadaIT, does it do for the issue?

Hi James,Sorry for the delay in responding. I have not had a chance to try this yet however the error I am receiving is the same one you have described here. So hopefully after performing an offline defragmentation we will see these errors disapear from the logs.Thanks again

Great! Please bear in mind that it isn't a really malfunction for Exchange