Hi Since we upgraded a few of our Exchange 2010 servers to SP1, the MSExchangeMailSubmission service crashes every 24 hours on each of the upgraded servers, logging the following event: Log Name: Application Source: MSExchange Common Date: 13/09/2010 10:04:21 a.m. Event ID: 4999 Task Category: General Level: Error Keywords: Classic User: N/A Computer: EXC2010.domain.com Description: Watson report about to be sent for process id: 9108, with parameters: E12, c-RTL-AMD64, 14.01.0218.015, MSExchangeMailSubmission, M.Exchange.StoreProvider, M.M.MapiEventManager.SaveWatermarks, M.Mapi.MapiExceptionArgument, 69c9, 14.01.0218.011. ErrorReportingEnabled: False How can I fix this? Thanks Olli

Hi Does ExBPA report anything? Do you have any monitoring like SCOM?Jonas Andersson MCTS: Microsoft Exchange Server 2007/2010 | MCITP: EMA 2007/2010 | MCSE/MCSA Blog: http://www.testlabs.se/blog

Hi Jonas I ran ExBPA but it doesn't show anything related to mail submission. A few errors and warning related to backups not being run and circular logging enabled (because a few of our servers are DAG members) and a few issues related to Exchange 2003 leftovers. We have SCOM but the systems management team hasn't fully deployed the Exchange 2010 MP yet. It's not yet monitoring the servers that have been upgraded to Exchange 2010 SP1. From the looks of it, crashing every 24 hours with an exception while saving watermarks, that sounds like a timer or counter overflow that isn't handled properly. Should be easy to find and fix. Regards Olli

Hi Rob No, not really. Because it crashes every 24 hours it looks like a simple timer or counter overflow error to me, or maybe something related to hardcoded date or time formats. Our servers are using en-NZ, maybe someone hardcoded something to en-US and gets confused by the swapped day and month every 24 hours. Because it's a Watson-style crash it's very likely a bug and not a config issue, that's what it looks like to me. Regards Olli

Hey Olli, I have this issue too. Were you able to find anything about it?

Hi Jonas I ran ExBPA but it doesn't show anything related to mail submission. A few errors and warning related to backups not being run and circular logging enabled (because a few of our servers are DAG members) and a few issues related to Exchange 2003 leftovers. We have SCOM but the systems management team hasn't fully deployed the Exchange 2010 MP yet. It's not yet monitoring the servers that have been upgraded to Exchange 2010 SP1. From the looks of it, crashing every 24 hours with an exception while saving watermarks, that sounds like a timer or counter overflow that isn't handled properly. Should be easy to find and fix. Regards Olli Have you read through the link below regarding the SP1 issues? http://msexchangeteam.com/archive/2010/09/01/456094.aspxJonas Andersson MCTS: Microsoft Exchange Server 2007/2010 | MCITP: EMA 2007/2010 | MCSE/MCSA Blog: http://www.testlabs.se/blog

Hi Jonas Yes, I have. Nothing in it with regards to the MSExchangeMailSubmission service and event 4999. So what's the story here? This service crashes consistently every 24 hours on all three upgraded servers, and I am about to upgrade another four servers (all members of a cross-site DAG) to SP1 next monday. Clearly this is a bug of some kind, maybe related to hardcoded date or time formats? Olli

Hi, Just installed a Exchange 2010 SP1 in a exchange 2003 organization and seeing same error. Any idea what is causing this problem, I have not seen an problem... Regards Ronny

Hello? Jonas? Anybody? It's affecting all our servers that have been upgraded to SP1. The service restarts itself after 5 seconds, which is good, but clearly a crash like that is not supposed to happen consistently every 24 hours. Please get back to me with any findings. Thanks Olli

Sounds like you should open a ticket with Microsoft support.

I am having this issue as well since updating to Exchange 2010 SP1.

Did anyone ever open a case on this?

Hello, We are having the same issue with Mail Submission crashing every 24hrs. The service is able to restart sucessfully, and I do not see any impact to mail flow. My environment is the following: Exchange 2010, back end HT, CA, MBOX and a front-end server as Transport/Edge SYNC. Microsoft Windows Server 2008 R2 x64. Vmware ESXI 4.1. Thanks, Matthew

I am having the same problem is there any solution,hotfix maybe???Dragan Penkov MCSA,VCP

The same here also. Any solution, hotfix etc...... ? Exchange 2010 with SP1 and Rollup-1 Stefan

Same issue here, SP1 UR1. Any solutions?

Same Issue in our environment with SP1 after upgrading from Exchange 2003. Any solution?

Hi... I have this issue too. Someone found a resolution? Thanks!

Hi I have the same problem. :-( JakubJakub

Same issue on 2 new 2010 mailbox servers. We have opened a ticket with Microsoft and provided them with procdumps from both servers. Will post the resolution here if/when we receive it.

Same issue on a new single server install of Exchange 2010 with SP1.

Same issue on 2 new 2010 mailbox servers. We have opened a ticket with Microsoft and provided them with procdumps from both servers. Will post the resolution here if/when we receive it. We received an Interim Update (IU) from Microsoft that supposedly fixes the MailSubmission Service restarting every 24 hours. The issue with the IU is that it has to be uninstalled before any official rollup/upgrade is installed, or before any new IU is installed. We tried installing the IU after applying Rollup 2 for Exchange 2010 SP1 but the IU installation fails. If we uninstall Rollup 2 the IU will install (don't know if it fixes the MailSubmission Service problem), but our environment requires Rollup 2 (lagged DAGs), so at this point we won't be installing the IU. An IU that needs to be uninstalled before any official rollup/update is installed isn't feasible. Hopefully Microsoft will address the 4999 and 7031 errors in an official rollup -- will keep you posted of our fate.

Same issue here on two Exchange 2010 Sp1 servers.

Hi Olli Do you have any kind of feedback or how did you solve the problem?Jonas Andersson MCTS: Microsoft Exchange Server 2007/2010 | MCITP: EMA 2007/2010 | MCSE/MCSA Blog: http://www.testlabs.se/blog | Follow me on twitter: jonand82

I am am looking for fix as well.

Same here. Mail Submission service crashes on only one of our 2010 Maibox servers, but not the other one.

We have the same issue. Exchange 2010 Sp1 UR2 on Windows 2008 R2. No A/V, nothing I can think of to crash the service... We'll see if MS has something for us I suppose. Brent Piercey, MCSE, MCITP:EA, VCP, CCNA Senior Engineer Waypoint Business Solutions

Someone could find any solution to this problem ? Thanks!

I am also having the same issue. Exchange 2010 SP1 UR2 on Windows 2008 R2. Anyone figured this one out yet?

We have 2010 SP1 RU3. Same error on the mailbox servers in both our TEST and PROD environments so two completely different networks/environments. Has anyone heard back from MS after opening a ticket? It happens at 3pm every day but looking back at the event logs it started doing it at 9am, then a days gap happened and then 11am and now 3pm every day since then for the past week. We are running in a 2003/2010 co-existence at the moment with only a few test users running on 2010. Are other people here running in co-existence? We are hesitant to move all users to 2010 given these errors. One thing I have noticed with posts above is people seem to be using 2008 R2 with 2010? We are the same here. Could this be the cause? Are people using IPv6 or have they disabled it to use IPv4? EDIT: I have done some more research into this error and apparently this can be caused by having an active (ie mounted) database but no mailboxes on it. We have a user and executive database in both environments and only have mailboxes on the user databases. I have moved some test users to the executive databases so all exchange databases have mailboxes. Apparently an exchange task runs every 24 hrs and if a database is empty this will fail causing the error. I will report back tomorrow if it works...

I have moved some test users to the executive databases so all exchange databases have mailboxes. Apparently an exchange task runs every 24 hrs and if a database is empty this will fail causing the error. I will report back tomorrow if it works... It seems that this "solves" our problem :) Thanks a lot!Best regards, Alexander Zirbes

I can confirm that moving a mailbox to the blank database worked as the error didn't come up today at 3pm when it normally does. Giving it a few more days before I celebrate too much though!

I called Microsoft and the fix is to get rid of any blank databases. It is a bug in SP1 RU 2.

This is fixed in SP1 RU3 v3 looking at the change logs