Service MSExchangeMailSubmission. any way to ID issue?

All,

I have been getting this well known info alert in my event log, I have removed all retention polices from the mailboxes, stopped and restarted the managed folder assistant.. but still i get this every 15 minutes.

After some reading I saw others with the same notice, their fix was was to move the mailbox's to another mail store, I have 3 mail stores with around 28 boxes per store so that's not really an option. Is there way to ID what mailbox or mail store is having this problem so I can at least act on it?

I also checked the LegacyDN against the server  no user is showing up as the wrong server legacydn

Server is 2010 SP1 running under 2008 R2

------------------------------------------------------------------------------
Service MSExchangeMailSubmission. An exception has been handled on behalf of an assistant. A report will be sent for the following exception: Microsoft.Exchange.Assistants.AIGrayException ---> Microsoft.Exchange.Common.GrayException ---> Microsoft.Mapi.MapiExceptionPartialCompletion: MapiExceptionPartialCompletion: Unable to save watermarks. (hr=0x40680, ec=0)
Diagnostic context:
    Lid: 1494    ---- Remote Context Beg ----
    Lid: 10804   StoreEc: 0xFFFFF9BF
    Lid: 25094  
    Lid: 13710   StoreEc: 0x89B    
    Lid: 14672   StoreEc: 0x40680  
    Lid: 2031    StoreEc: 0x40680  
    Lid: 18009   StoreEc: 0x40680  
    Lid: 1750    ---- Remote Context End ----
    Lid: 32361   StoreEc: 0x40680  
   at Microsoft.Mapi.MapiExceptionHelper.ThrowIfErrorOrWarning(String message, Int32 hresult, Boolean allowWarnings, SafeExInterfaceHandle iUnknown, Exception innerException)
   at Microsoft.Mapi.MapiEventManager.SaveWatermarks(Watermark[] watermarks)
   at Microsoft.Exchange.Assistants.EventAccess.<>c__DisplayClassd.<SaveWatermarks>b__c()
   at Microsoft.Exchange.Assistants.EventAccess.CallEventManager(EventManagerFunction function)
   at Microsoft.Exchange.Assistants.EventControllerPrivate.UpdateIdleWatermarksForAssistant(Guid[] idleMailboxes, Guid assistantId)
   at Microsoft.Exchange.Assistants.EventControllerPrivate.DisposeOfIdleDispatchers()
   at Microsoft.Exchange.Assistants.EventController.<UpdateWatermarks>b__4()
   at Microsoft.Exchange.Assistants.Util.<>c__DisplayClass1.<CoreCatchMeIfYouCan>b__0()
   at Microsoft.Exchange.Common.IL.ILUtil.DoTryFilterCatch(TryDelegate tryDelegate, FilterDelegate filterDelegate, CatchDelegate catchDelegate)
   --- End of inner exception stack trace ---
   at Microsoft.Exchange.Common.GrayException.ExceptionCatcher(Object exception)
   at Microsoft.Exchange.Common.IL.ILUtil.DoTryFilterCatch(TryDelegate tryDelegate, FilterDelegate filterDelegate, CatchDelegate catchDelegate)
   at Microsoft.Exchange.Common.GrayException.MapAndReportGrayExceptions(UserCodeDelegate tryCode)
   at Microsoft.Exchange.Assistants.Util.CoreCatchMeIfYouCan(CatchMe function)
   at Microsoft.Exchange.Assistants.Util.CatchMeIfYouCan(CatchMe function)
   --- End of inner exception stack trace ---
   at Microsoft.Exchange.Assistants.Util.TraceAndThrow(CatchMe function, AIException aiException)
   at Microsoft.Exchange.Assistants.Util.CatchMeIfYouCan(CatchMe function)
   at Microsoft.Exchange.Assistants.Base.CatchMeIfYouCan(CatchMe function).
BMI-ITAsked:
Who is Participating?
 
BMI-ITAuthor Commented:
thanks, I would like t know more about using mfcmapi.exe, the eventlogs such as applications and the exchange log for mailboxdatabase failures show everything as fine.

would you be able to recommend a link for a newish admin to check the above mailboxes?
0
 
BMI-ITAuthor Commented:
no one has any idea what may be doing this or how I can pinpoint the source?
0
 
abhijitmdpCommented:
The MAPI error 0x40680 means it was unable to delete something. You can face this problem specially if there any problem with mailbox store and during defrag exchange noticed it and continusly trying to resolve the corruption, the best way to troubleshoot this problem is to remove the corruptions by mfcmapi.exe on per mailbox wise or create new databases and move the mailboxes with high badlimit. and then dismount old database, rename old .edb files and mount the database again. and then remove the old databases.
0
Ultimate Tool Kit for Technology Solution Provider

Broken down into practical pointers and step-by-step instructions, the IT Service Excellence Tool Kit delivers expert advice for technology solution providers. Get your free copy now.

 
BMI-ITAuthor Commented:
this thing is... how can i tell what mailbox has these issues? If i knew the offending box I could fix it.

0
 
abhijitmdpCommented:
This is difficult to point to a mailbox by provided data, but this issue useually comes with Discovery search mailbox, system mailbox, public folders and resource mailboxes. You can also run exbpa to find more detail of this error, check in event logs. these are the places where you can find the mailbox name which causing the issue.
0
 
BMI-ITAuthor Commented:
no answers - reboot fixed issue
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.