none
Exchange 2013 multiple event id 10010 Mid-Tier Storage RRS feed

  • Question

  • I notice repeating events with the id 10010 for the source "MSExchange Mid-Tier Storage" on the Exchange server.

    In the description are different things like:

    • Process: MSExchangeSubmission (6496), Db:14f63545-f85d-45dd-a9cc-d457dbb7d046,C:1,BT:00:00:00,
    • Process: MSExchangeDelivery (3020), Db:14f63545-f85d-45dd-a9cc-d457dbb7d046,C:2,BT:00:00:00,
    • Process: Microsoft.Exchange.RpcClientAccess.Service (9248), Db:14f63545-f85d-45dd-a9cc-d457dbb7d046,C:2,BT:00:00:00,

    Is this normal or what is wrong?

    Friday, December 7, 2012 10:03 AM

All replies

  • Post the entire event ID.

    Gulab Prasad,
    gulab@exchangeranger.com
    My Blog | Z-Hire Employee Provisioning App

    Saturday, December 8, 2012 5:15 PM
  • The common is in the process-text ist all the time the "Db:14f63545-f85d-45dd-a9cc-d457dbb7d046" included, the process himself are many different.

    --------------------------------------------------------------------------------------------------------------------

    Log Name:      Application
    Source:        MSExchange Mid-Tier Storage
    Date:          08.12.2012 18:40:11
    Event ID:      10010
    Task Category: ResourceHealth
    Level:         Warning
    Keywords:      Classic
    User:          N/A
    Computer:      x
    Description:
    Process: MSExchangeDelivery (3676), Db:14f63545-f85d-45dd-a9cc-d457dbb7d046,C:1,BT:00:00:00,
    --------------------------------------------------------------------------------------------------------------------

    Log Name:      Application
    Source:        MSExchange Mid-Tier Storage
    Date:          08.12.2012 18:39:34
    Event ID:      10010
    Task Category: ResourceHealth
    Level:         Warning
    Keywords:      Classic
    User:          N/A
    Computer:      x
    Description:
    Process: w3wp (8020), Db:14f63545-f85d-45dd-a9cc-d457dbb7d046,C:1,BT:00:00:00,
    --------------------------------------------------------------------------------------------------------------------

    Log Name:      Application
    Source:        MSExchange Mid-Tier Storage
    Date:          08.12.2012 18:39:32
    Event ID:      10010
    Task Category: ResourceHealth
    Level:         Warning
    Keywords:      Classic
    User:          N/A
    Computer:      x
    Description:
    Process: noderunner (3800), Db:14f63545-f85d-45dd-a9cc-d457dbb7d046,C:2,BT:00:00:00,
    --------------------------------------------------------------------------------------------------------------------

    Log Name:      Application
    Source:        MSExchange Mid-Tier Storage
    Date:          08.12.2012 18:39:06
    Event ID:      10010
    Task Category: ResourceHealth
    Level:         Warning
    Keywords:      Classic
    User:          N/A
    Computer:      x
    Description:
    Process: MSExchangeSubmission (5628), Db:14f63545-f85d-45dd-a9cc-d457dbb7d046,C:1,BT:00:00:00,
    --------------------------------------------------------------------------------------------------------------------

    Log Name:      Application
    Source:        MSExchange Mid-Tier Storage
    Date:          08.12.2012 18:39:05
    Event ID:      10010
    Task Category: ResourceHealth
    Level:         Warning
    Keywords:      Classic
    User:          N/A
    Computer:      x
    Description:
    Process: MSExchangeMailboxAssistants (4568), Db:14f63545-f85d-45dd-a9cc-d457dbb7d046,C:0,BT:00:00:00,


    • Edited by mabau Saturday, December 8, 2012 6:06 PM
    Saturday, December 8, 2012 6:05 PM
  • Hello,

    Would you please create a new mailbox store and monitor if the new warning event also indicates the new one.

    Thanks,

    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com


    Simon Wu
    TechNet Community Support

    Tuesday, December 11, 2012 1:54 AM
    Moderator
  • I have the same issue on a brand new Windows 2012 with exchange 2013 server. Why would I need to create a new mailbox store if the machine does not even have any mailboxes yet?

    This solution is not going to work for me. Microsoft needs to figure out why two pieces of their own software cannot work together without throwing warnings.

    Log Name:      Application
    Source:        MSExchange Mid-Tier Storage
    Date:          12/11/2012 12:00:36 PM
    Event ID:      10010
    Task Category: ResourceHealth
    Level:         Warning
    Keywords:      Classic
    User:          N/A
    Computer:      Buckwheat.******.local
    Description:
    Process: MSExchangeDelivery (2928), Db:a9556c53-897f-4448-a945-b271eb77b890,C:1,BT:00:00:00,
    Event Xml:
    <Event xmlns="***">
      <System>
        <Provider Name="MSExchange Mid-Tier Storage" />
        <EventID Qualifiers="32768">10010</EventID>
        <Level>3</Level>
        <Task>6</Task>
        <Keywords>0x80000000000000</Keywords>
        <TimeCreated SystemTime="2012-12-11T19:00:36.000000000Z" />
        <EventRecordID>51039</EventRecordID>
        <Channel>Application</Channel>
        <Computer>Buckwheat.******.local</Computer>
        <Security />
      </System>
      <EventData>
        <Data>Process: MSExchangeDelivery (2928), Db:a9556c53-897f-4448-a945-b271eb77b890,C:1,BT:00:00:00,</Data>
      </EventData>
    </Event>

    Tuesday, December 11, 2012 7:10 PM
  • I've got exactly the same problem and I'm curious what the cause is. Exchange 2013 on Windows Server 2012.

    - System
    - Provider
    [
    Name]
    MSExchange Mid-Tier
    Storage
    - EventID 10010
    [
    Qualifiers]
    32768
    Level 3
    Task 6
    Keywords 0x80000000000000
    - TimeCreated
    [
    SystemTime]
    2012-12-13T09:43:15.000000000Z
    EventRecordID 43859
    Channel Application
    Computer ITSPECSRV.itspec.local
    Security
    - EventData
    Process:
    Microsoft.Exchange.ServiceHost (3576),
    Db:7c199919-f6e3-4838-a79d-adaed2dbfaca,C:1,BT:00:00:00,

    ----------------------------------------------------------------

    - System
    - Provider
    [
    Name]
    MSExchange Mid-Tier
    Storage
    - EventID 10010
    [
    Qualifiers]
    32768
    Level 3
    Task 6
    Keywords 0x80000000000000
    - TimeCreated
    [
    SystemTime]
    2012-12-13T09:10:20.000000000Z
    EventRecordID 43802
    Channel Application
    Computer ITSPECSRV.itspec.local
    Security
    - EventData

    Process:
    Microsoft.Exchange.RpcClientAccess.Service (66064),
    Db:7c199919-f6e3-4838-a79d-adaed2dbfaca,C:2,BT:00:00:00,

    -----------------------------------------------------------

    - System
    - Provider
    [
    Name]
    MSExchange Mid-Tier
    Storage
    - EventID 10010
    [
    Qualifiers]
    32768
    Level 3
    Task 6
    Keywords 0x80000000000000
    - TimeCreated
    [
    SystemTime]
    2012-12-13T09:08:16.000000000Z
    EventRecordID 43788
    Channel Application
    Computer ITSPECSRV.itspec.local
    Security
    - EventData
    Process: w3wp (7544),
    Db:7c199919-f6e3-4838-a79d-adaed2dbfaca,C:0,BT:00:00:00,
    • Edited by leof Thursday, December 13, 2012 9:55 AM
    Wednesday, December 12, 2012 5:22 PM
  • Hi Wu

    I create a new mailbox store. This mailbox store produce the same log entries. How is look is not depend of the mailbox store.


    • Edited by mabau Friday, December 14, 2012 2:10 PM
    Friday, December 14, 2012 2:09 PM
  • I also have these errors and I also have an Exchange server that can't be communicated with by Outlook clients (but can be communicated via OWA). Are you gentlemen having any issues with your mail stores or is everything working fine and you simply have error messages?
    Sunday, December 16, 2012 3:59 PM
  • I have the same issue as well, my Outlook clients cannot connect, mail is being delayed, and get the same Mid_tier Issue.. This has to be fixed....

    Monday, January 7, 2013 3:32 PM
  • I also have these errors and I also have an Exchange server that can't be communicated with by Outlook clients (but can be communicated via OWA). Are you gentlemen having any issues with your mail stores or is everything working fine and you simply have error messages?

    That's right. Everything works fine. I only get a lot of these errors among others. Recent ones:

    • ITSPECSRV
    • 10010
    • Waarschuwing
    • MSExchange Mid-Tier Storage
    • Application
    • 11-1-2013 13:32:49
    • ITSPECSRV
    • 6002
    • Waarschuwing
    • MSExchange Mid-Tier Storage
    • Application
    • 11-1-2013 13:31:25
    • ITSPECSRV
    • 10010
    • Waarschuwing
    • MSExchange Mid-Tier Storage
    • Application
    • 11-1-2013 13:29:58
    • ITSPECSRV
    • 1035
    • Waarschuwing
    • MSExchangeFrontEndTransport
    • Application
    • 11-1-2013 13:29:03
    • ITSPECSRV
    • 10010
    • Waarschuwing
    • MSExchange Mid-Tier Storage
    • Application
    • 11-1-2013 13:26:25
    • ITSPECSRV
    • 10010
    • Waarschuwing
    • MSExchange Mid-Tier Storage
    • Application
    • 11-1-2013 13:26:23
    • ITSPECSRV
    • 10010
    • Waarschuwing
    • MSExchange Mid-Tier Storage
    • Application
    • 11-1-2013 13:25:59
    • ITSPECSRV
    • 10010
    • Waarschuwing
    • MSExchange Mid-Tier Storage
    • Application
    • 11-1-2013 13:21:13
    • ITSPECSRV
    • 10010
    • Waarschuwing
    • MSExchange Mid-Tier Storage
    • Application
    • 11-1-2013 13:21:09
    • ITSPECSRV
    • 10010
    • Waarschuwing
    • MSExchange Mid-Tier Storage
    • Application
    • 11-1-2013 13:20:10
    • ITSPECSRV
    • 1035
    • Waarschuwing
    • MSExchangeFrontEndTransport
    • Application
    • 11-1-2013 13:14:03
    • ITSPECSRV
    • 1111
    • Fout
    • Microsoft-Windows-TerminalServices-Printers
    • System
    • 11-1-2013 13:04:44
    • ITSPECSRV
    • 1111
    • Fout
    • Microsoft-Windows-TerminalServices-Printers
    • System
    • 11-1-2013 13:04:43
    • ITSPECSRV
    • 1111
    • Fout
    • Microsoft-Windows-TerminalServices-Printers
    • System
    • 11-1-2013 13:04:43
    • ITSPECSRV
    • 1035
    • Waarschuwing
    • MSExchangeFrontEndTransport
    • Application
    • 11-1-2013 12:54:03
    • ITSPECSRV
    • 6002
    • Waarschuwing
    • MSExchange Mid-Tier Storage
    • Application
    • 11-1-2013 12:43:53
    • ITSPECSRV
    • 10010
    • Waarschuwing
    • MSExchange Mid-Tier Storage
    • Application
    • 11-1-2013 12:39:17
    • ITSPECSRV
    • 1035
    • Waarschuwing
    • MSExchangeFrontEndTransport
    • Application
    • 11-1-2013 12:39:02
    • ITSPECSRV
    • 6002
    • Waarschuwing
    • MSExchange Mid-Tier Storage
    • Application
    • 11-1-2013 12:36:23
    • ITSPECSRV
    • 10010
    • Waarschuwing
    • MSExchange Mid-Tier Storage
    • Application
    • 11-1-2013 12:32:49
    • ITSPECSRV
    • 10010
    • Waarschuwing
    • MSExchange Mid-Tier Storage
    • Application
    • 11-1-2013 12:29:58
    • ITSPECSRV
    • 10010
    • Waarschuwing
    • MSExchange Mid-Tier Storage
    • Application
    • 11-1-2013 12:26:25
    • ITSPECSRV
    • 10010
    • Waarschuwing
    • MSExchange Mid-Tier Storage
    • Application
    • 11-1-2013 12:26:23
    • ITSPECSRV
    • 10010
    • Waarschuwing
    • MSExchange Mid-Tier Storage
    • Application
    • 11-1-2013 12:26:00
    • ITSPECSRV
    • 1035
    • Waarschuwing
    • MSExchangeFrontEndTransport
    • Application
    • 11-1-2013 12:24:02
    • ITSPECSRV
    • 10010
    • Waarschuwing
    • MSExchange Mid-Tier Storage
    • Application
    • 11-1-2013 12:21:14
    • ITSPECSRV
    • 10010
    • Waarschuwing
    • MSExchange Mid-Tier Storage
    • Application
    • 11-1-2013 12:21:09
    • ITSPECSRV
    • 10010
    • Waarschuwing
    • MSExchange Mid-Tier Storage
    • Application
    • 11-1-2013 12:20:10
    • ITSPECSRV
    • 1035
    • Waarschuwing
    • MSExchangeFrontEndTransport
    • Application
    • 11-1-2013 12:09:02
    • ITSPECSRV
    • 6002
    • Waarschuwing
    • MSExchange Mid-Tier Storage
    • Application
    • 11-1-2013 12:05:59
    • ITSPECSRV
    • 1035
    • Waarschuwing
    • MSExchangeFrontEndTransport
    • Application
    • 11-1-2013 11:54:01
    • ITSPECSRV
    • 6002
    • Waarschuwing
    • MSExchange Mid-Tier Storage
    • Application
    • 11-1-2013 11:51:22
    • ITSPECSRV
    • 6002
    • Waarschuwing
    • MSExchange Mid-Tier Storage
    • Application
    • 11-1-2013 11:47:53
    • ITSPECSRV
    • 10010
    • Waarschuwing
    • MSExchange Mid-Tier Storage
    • Application
    • 11-1-2013 11:39:17
    • ITSPECSRV
    • 1035
    • Waarschuwing
    • MSExchangeFrontEndTransport
    • Application
    • 11-1-2013 11:39:01
    • ITSPECSRV
    • 10010
    • Waarschuwing
    • MSExchange Mid-Tier Storage
    • Application
    • 11-1-2013 11:32:50
    • ITSPECSRV
    • 10010
    • Waarschuwing
    • MSExchange Mid-Tier Storage
    • Application
    • 11-1-2013 11:29:58
    • ITSPECSRV
    • 10010
    • Waarschuwing
    • MSExchange Mid-Tier Storage
    • Application
    • 11-1-2013 11:26:25
    • ITSPECSRV
    • 10010
    • Waarschuwing
    • MSExchange Mid-Tier Storage
    • Application
    • 11-1-2013 11:26:24
    • ITSPECSRV
    • 10010
    • Waarschuwing
    • MSExchange Mid-Tier Storage
    • Application
    • 11-1-2013 11:26:00
    • ITSPECSRV
    • 1035
    • Waarschuwing
    • MSExchangeFrontEndTransport
    • Application
    • 11-1-2013 11:24:01
    • ITSPECSRV
    • 10010
    • Waarschuwing
    • MSExchange Mid-Tier Storage
    • Application
    • 11-1-2013 11:21:14
    • ITSPECSRV
    • 10010
    • Waarschuwing
    • MSExchange Mid-Tier Storage
    • Application
    • 11-1-2013 11:21:09
    • ITSPECSRV
    • 10010
    • Waarschuwing
    • MSExchange Mid-Tier Storage
    • Application
    • 11-1-2013 11:20:10
    • ITSPECSRV
    • 6002
    • Waarschuwing
    • MSExchange Mid-Tier Storage
    • Application
    • 11-1-2013 11:16:22
    • ITSPECSRV
    • 6002
    • Waarschuwing
    • MSExchange Mid-Tier Storage
    • Application
    • 11-1-2013 11:11:11
    • ITSPECSRV
    • 1035
    • Waarschuwing
    • MSExchangeFrontEndTransport
    • Application
    • 11-1-2013 11:09:01
    • ITSPECSRV
    • 6002
    • Waarschuwing
    • MSExchange Mid-Tier Storage
    • Application
    • 11-1-2013 10:56:03
    • ITSPECSRV
    • 1035
    • Waarschuwing
    • MSExchangeFrontEndTransport
    • Application
    • 11-1-2013 10:54:00
    • ITSPECSRV
    • 10010
    • Waarschuwing
    • MSExchange Mid-Tier Storage
    • Application
    • 11-1-2013 10:39:18
    • ITSPECSRV
    • 1035
    • Waarschuwing
    • MSExchangeFrontEndTransport
    • Application
    • 11-1-2013 10:39:00
    • ITSPECSRV
    • 10010
    • Waarschuwing
    • MSExchange Mid-Tier Storage
    • Application
    • 11-1-2013 10:32:50
    • ITSPECSRV
    • 6002
    • Waarschuwing
    • MSExchange Mid-Tier Storage
    • Application
    • 11-1-2013 10:31:26
    • ITSPECSRV
    • 10010
    • Waarschuwing
    • MSExchange Mid-Tier Storage
    • Application
    • 11-1-2013 10:29:58
    • ITSPECSRV
    • 10010
    • Waarschuwing
    • MSExchange Mid-Tier Storage
    • Application
    • 11-1-2013 10:26:25
    • ITSPECSRV
    • 10010
    • Waarschuwing
    • MSExchange Mid-Tier Storage
    • Application
    • 11-1-2013 10:26:24
    • ITSPECSRV
    • 10010
    • Waarschuwing
    • MSExchange Mid-Tier Storage
    • Application
    • 11-1-2013 10:26:00
    • ITSPECSRV
    • 1035
    • Waarschuwing
    • MSExchangeFrontEndTransport
    • Application
    • 11-1-2013 10:24:00
    • ITSPECSRV
    • 10010
    • Waarschuwing
    • MSExchange Mid-Tier Storage
    • Application
    • 11-1-2013 10:21:14
    • ITSPECSRV
    • 10010
    • Waarschuwing
    • MSExchange Mid-Tier Storage
    • Application
    • 11-1-2013 10:21:09
    • ITSPECSRV
    • 10010
    • Waarschuwing
    • MSExchange Mid-Tier Storage
    • Application
    • 11-1-2013 10:20:10
    • ITSPECSRV
    • 6002
    • Waarschuwing
    • MSExchange Mid-Tier Storage
    • Application
    • 11-1-2013 10:11:23
    • ITSPECSRV
    • 1035
    • Waarschuwing
    • MSExchangeFrontEndTransport
    • Application
    • 11-1-2013 10:09:00
    • ITSPECSRV
    • 1035
    • Waarschuwing
    • MSExchangeFrontEndTransport
    • Application
    • 11-1-2013 9:54:00
    • ITSPECSRV
    • 6002
    • Waarschuwing
    • MSExchange Mid-Tier Storage
    • Application
    • 11-1-2013 9:40:57
    • ITSPECSRV
    • 10010
    • Waarschuwing
    • MSExchange Mid-Tier Storage
    • Application
    • 11-1-2013 9:39:18
    • ITSPECSRV
    • 1035
    • Waarschuwing
    • MSExchangeFrontEndTransport
    • Application
    • 11-1-2013 9:38:59
    • ITSPECSRV
    • 10010
    • Waarschuwing
    • MSExchange Mid-Tier Storage
    • Application
    • 11-1-2013 9:32:50
    • ITSPECSRV
    • 10010
    • Waarschuwing
    • MSExchange Mid-Tier Storage
    • Application
    • 11-1-2013 9:29:59
    • ITSPECSRV
    • 3028
    • Waarschuwing
    • MSExchangeApplicationLogic
    • Application
    • 11-1-2013 9:26:50
    • ITSPECSRV
    • 3028
    • Waarschuwing
    • MSExchangeApplicationLogic
    • Application
    • 11-1-2013 9:26:50
    • ITSPECSRV
    • 10010
    • Waarschuwing
    • MSExchange Mid-Tier Storage
    • Application
    • 11-1-2013 9:26:25
    • ITSPECSRV
    • 10010
    • Waarschuwing
    • MSExchange Mid-Tier Storage
    • Application
    • 11-1-2013 9:26:24
    • ITSPECSRV
    • 10010
    • Waarschuwing
    • MSExchange Mid-Tier Storage
    • Application
    • 11-1-2013 9:26:00
    • ITSPECSRV
    • 1035
    • Waarschuwing
    • MSExchangeFrontEndTransport
    • Application
    • 11-1-2013 9:23:59
    • ITSPECSRV
    • 106
    • Fout
    • MSExchange Common
    • Application
    • 11-1-2013 9:23:30
    • ITSPECSRV
    • 10010
    • Waarschuwing
    • MSExchange Mid-Tier Storage
    • Application
    • 11-1-2013 9:21:14
    • ITSPECSRV
    • 10010
    • Waarschuwing
    • MSExchange Mid-Tier Storage
    • Application
    • 11-1-2013 9:21:10
    • ITSPECSRV
    • 10010
    • Waarschuwing
    • MSExchange Mid-Tier Storage
    • Application
    • 11-1-2013 9:20:11
    • ITSPECSRV
    • 6002
    • Waarschuwing
    • MSExchange Mid-Tier Storage
    • Application
    • 11-1-2013 9:11:25
    • ITSPECSRV
    • 1035
    • Waarschuwing
    • MSExchangeFrontEndTransport
    • Application
    • 11-1-2013 9:08:59
    • ITSPECSRV
    • 1035
    • Waarschuwing
    • MSExchangeFrontEndTransport
    • Application
    • 11-1-2013 8:53:59
    • ITSPECSRV
    • 10010
    • Waarschuwing
    • MSExchange Mid-Tier Storage
    • Application
    • 11-1-2013 8:39:18
    • ITSPECSRV
    • 1035
    • Waarschuwing
    • MSExchangeFrontEndTransport
    • Application
    • 11-1-2013 8:38:59
    • ITSPECSRV
    • 10010
    • Waarschuwing
    • MSExchange Mid-Tier Storage
    • Application
    • 11-1-2013 8:32:50
    • ITSPECSRV
    • 1033
    • Waarschuwing
    • MSExchange ActiveSync
    • Application
    • 11-1-2013 8:32:34
    • ITSPECSRV
    • 10010
    • Waarschuwing
    • MSExchange Mid-Tier Storage
    • Application
    • 11-1-2013 8:29:59
    • ITSPECSRV
    • 10010
    • Waarschuwing
    • MSExchange Mid-Tier Storage
    • Application
    • 11-1-2013 8:26:26
    • ITSPECSRV
    • 10010
    • Waarschuwing
    • MSExchange Mid-Tier Storage
    • Application
    • 11-1-2013 8:26:24
    • ITSPECSRV
    • 10010
    • Waarschuwing
    • MSExchange Mid-Tier Storage
    • Application
    • 11-1-2013 8:26:00
    • ITSPECSRV
    • 1035
    • Waarschuwing
    • MSExchangeFrontEndTransport
    • Application
    • 11-1-2013 8:23:58
    • ITSPECSRV
    • 5013
    • Waarschuwing
    • Microsoft-Windows-WAS
    • System
    • 11-1-2013 8:22:33
    • ITSPECSRV
    • 5138
    • Waarschuwing
    • Microsoft-Windows-WAS
    • System
    • 11-1-2013 8:22:33
    • ITSPECSRV
    • 106
    • Fout
    • MSExchange Common
    • Application
    • 11-1-2013 8:21:35
    • ITSPECSRV
    • 10010
    • Waarschuwing
    • MSExchange Mid-Tier Storage
    • Application
    • 11-1-2013 8:21:14
    • ITSPECSRV
    • 10010
    • Waarschuwing
    • MSExchange Mid-Tier Storage
    • Application
    • 11-1-2013 8:21:10
    • ITSPECSRV
    • 10010
    • Waarschuwing
    • MSExchange Mid-Tier Storage
    • Application
    • 11-1-2013 8:20:11
    • ITSPECSRV
    • 6002
    • Waarschuwing
    • MSExchange Mid-Tier Storage
    • Application
    • 11-1-2013 8:17:47
    • ITSPECSRV
    • 1035
    • Waarschuwing
    • MSExchangeFrontEndTransport
    • Application
    • 11-1-2013 8:08:58
    • ITSPECSRV
    • 10010
    • Waarschuwing
    • MSExchange Mid-Tier Storage
    • Application
    • 11-1-2013 8:04:02
    • ITSPECSRV
    • 1035
    • Waarschuwing
    • MSExchangeFrontEndTransport
    • Application
    • 11-1-2013 7:53:58
    • ITSPECSRV
    • 6002
    • Waarschuwing
    • MSExchange Mid-Tier Storage
    • Application
    • 11-1-2013 7:41:43
    • ITSPECSRV
    • 10010
    • Waarschuwing
    • MSExchange Mid-Tier Storage
    • Application
    • 11-1-2013 7:39:18
    • ITSPECSRV
    • 1035
    • Waarschuwing
    • MSExchangeFrontEndTransport
    • Application
    • 11-1-2013 7:38:57
    • ITSPECSRV
    • 10010
    • Waarschuwing
    • MSExchange Mid-Tier Storage
    • Application
    • 11-1-2013 7:29:59
    • ITSPECSRV
    • 10010
    • Waarschuwing
    • MSExchange Mid-Tier Storage
    • Application
    • 11-1-2013 7:26:26
    • ITSPECSRV
    • 10010
    • Waarschuwing
    • MSExchange Mid-Tier Storage
    • Application
    • 11-1-2013 7:26:24
    • ITSPECSRV
    • 10010
    • Waarschuwing
    • MSExchange Mid-Tier Storage
    • Application
    • 11-1-2013 7:26:00
    • ITSPECSRV
    • 1035
    • Waarschuwing
    • MSExchangeFrontEndTransport
    • Application
    • 11-1-2013 7:23:57
    • ITSPECSRV
    • 6002
    • Waarschuwing
    • MSExchange Mid-Tier Storage
    • Application
    • 11-1-2013 7:21:18
    • ITSPECSRV
    • 10010
    • Waarschuwing
    • MSExchange Mid-Tier Storage
    • Application
    • 11-1-2013 7:21:15
    • ITSPECSRV
    • 10010
    • Waarschuwing
    • MSExchange Mid-Tier Storage
    • Application
    • 11-1-2013 7:21:10
    • ITSPECSRV
    • 10010
    • Waarschuwing
    • MSExchange Mid-Tier Storage
    • Application
    • 11-1-2013 7:20:11
    • ITSPECSRV
    • 6002
    • Waarschuwing
    • MSExchange Mid-Tier Storage
    • Application
    • 11-1-2013 7:11:25
    • ITSPECSRV
    • 1035
    • Waarschuwing
    • MSExchangeFrontEndTransport
    • Application
    • 11-1-2013 7:08:57
    • ITSPECSRV
    • 10010
    • Waarschuwing
    • MSExchange Mid-Tier Storage
    • Application
    • 11-1-2013 7:04:02
    • ITSPECSRV
    • 1035
    • Waarschuwing
    • MSExchangeFrontEndTransport
    • Application
    • 11-1-2013 6:53:57
    • ITSPECSRV
    • 6002
    • Waarschuwing
    • MSExchange Mid-Tier Storage
    • Application
    • 11-1-2013 6:53:46

    Leo


    • Edited by leof Friday, January 11, 2013 12:42 PM
    Friday, January 11, 2013 12:40 PM
  • I'm also seeing these 10010 errors on my Windows
    server 2012 and Exchange 2013

    I'm also having problems with my Exchange server IIS
    app pool... It sometimes stop working, so my clients are unable to connect to
    Exchange... A restart of IIS do not help.... I need to restart the server...
    I'm getting WAS 5138 and 5013 errors in my log

    Martin



    • Edited by Martin_157 Thursday, January 17, 2013 7:47 AM
    Thursday, January 17, 2013 7:47 AM
  • I am having same issue.  I find an iisreset from command prompt seems to fix the issue for about 24 hours.

    Event 10010 and event 5013 and 5138 are displayed.

    Wednesday, January 23, 2013 3:24 PM
  • I get these errors too.

    When accessing OWA on the local network everything appears to work correctly.

    When accessing OWA from outside sometimes I get a login page but I never ever complete a login. Sometimes the login page never loads. I just get timeouts.

    These error messages 10010 and 6002 are the only errors I am seeing in server logs.

    It makes no sense. I'm seriously considering asking Microsoft if I can downgrade and install 2010 as my project is now running significantly behind schedule. I was supposed to have users online by now!

    Monday, January 28, 2013 2:19 PM
  • Same issue here as leof. tons of warnings, though things tend to kind of work. The issue that got me looking into this is when users send messages through OWA, they go directly to the drafts folder instead of sending out.
    Wednesday, February 6, 2013 8:14 PM
  • Hi

    I have the same Warnings (ID 10010) on my Exchange 2013. Also I get the 6002 and ASP.NET warnings (ID 1309).

    Any solutions so far?

    dechecker




    • Edited by dechecker Friday, February 8, 2013 11:05 AM
    Friday, February 8, 2013 9:19 AM
  • Hi there,

    same problem here - actually setting up a Lync/Exchange 2013 Proof of Concept in a testing environment.

    IDs showing up: 100010, 106 on the Mailbox Servers. A lot.

    On the CAS Servers asp.net warnings, as already stated above by someone else.

    It is a freshly installed Exchange 2013 system on Windows 2012 - I really wonder what is going on there ...


    Friday, February 8, 2013 12:50 PM
  • I've removed exchange using setup.exe /uninstall. I'm rebuilding the server that Exchange was installed on. I'm going to see if the error persists, and will report back in a few days. I hope this resolves my issues and my errors. Fingers crossed!
    Friday, February 8, 2013 3:23 PM
  • I've removed exchange using setup.exe /uninstall. I'm rebuilding the server that Exchange was installed on. I'm going to see if the error persists, and will report back in a few days. I hope this resolves my issues and my errors. Fingers crossed!
    I would not bet on it, because I saw the errors and warnings starting from Day 1, without any Mailboxes created or any further configuration. But anyway - good luck :)
    Friday, February 8, 2013 5:17 PM
  • I would not bet on it, because I saw the errors and warnings starting from Day 1, without any Mailboxes created or any further configuration. But anyway - good luck :)

    I had the issue before there were any production mailboxes. The basic testing is where the issues came up when sending from dummy accounts to the internet and from one dummy account to another. So, this is a default build not running in production that had the errors generated prior to testing, but were noticed after testing commenced. So, I'm still hopeful that something went sideways during the configuration or deployment. We'll see. 
    • Edited by TH2TECH Friday, February 8, 2013 7:06 PM tense mixed up
    Friday, February 8, 2013 7:05 PM
  • experiencing same issues, outlook clients cannot connect but owa works

    this is on a brand new windows domain, first exchange server installed

    pitiful that microsoft released exchange 2013 in this state

    Wednesday, February 13, 2013 10:51 AM
  • Hi Guys, 

    Anyone solved this issue yet?, i am also getting these warnings.


    Sainyam Aggarwal MCTS

    Friday, February 15, 2013 12:23 PM
  • Same thing, brand new install, new domain, new forest, new server....

    Log Name:      Application
    Source:        MSExchange Mid-Tier Storage
    Date:          2/18/2013 3:25:57 PM
    Event ID:      10010
    Task Category: ResourceHealth
    Level:         Warning
    Keywords:      Classic
    User:          N/A
    Computer:      *********
    Description:
    Process: w3wp (14024), Db:9ef709fd-2ff2-4771-bc23-d1674b02f616,C:0,BT:00:00:00,
    Event Xml:
    <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
      <System>
        <Provider Name="MSExchange Mid-Tier Storage" />
        <EventID Qualifiers="32768">10010</EventID>
        <Level>3</Level>
        <Task>6</Task>
        <Keywords>0x80000000000000</Keywords>
        <TimeCreated SystemTime="2013-02-18T20:25:57.000000000Z" />
        <EventRecordID>114230</EventRecordID>
        <Channel>Application</Channel>
        <Computer>******</Computer>
        <Security />
      </System>
      <EventData>
        <Data>Process: w3wp (14024), Db:9ef709fd-2ff2-4771-bc23-d1674b02f616,C:0,BT:00:00:00,</Data>
      </EventData>
    </Event>

    Monday, February 18, 2013 8:41 PM
  • Just finished our rebuild. Everything from scratch, same things here as well. I was very careful this time to make sure to reboot often and apply updates at each step in the build. Server seems to be running fine, no anomalies so far. Hope someone at MS looks into this.
    Tuesday, February 19, 2013 4:57 AM
  • I just set up a brand new server for a customer with windows 2012 and
    exchange 2013. Same problems with the events like i described in the
    beginning.

    I could understand if this happens on one server, but
    how is look is a general problem. Gives me a bit the impression of an
    unfinished product.

    Hope MS will fix the problems soon.

    Tuesday, February 19, 2013 7:11 AM
  • We also have the MSExchange Mid-Tier Storage 10010 error.

    Everything appears to be working correctly, but Exchange constantly throws up this error.

    Brand new hardware with Server 2012.

    Hope Microsoft can pull their finger out and get this one sorted soon.

    Monday, February 25, 2013 10:04 PM
  • We are seeing the same issue on a brand new install.
    Monday, February 25, 2013 10:20 PM
  • Again - same here: completely new build Windows 2012 and Exchange 2013. Also needing to restart the Microsoft Exchange Transport service periodically - it doesn't stop, just stops working, and restarting that services kicks is back into life again. Would be nice to have a stable mail server :)

    Chris

    Tuesday, February 26, 2013 10:57 AM
  • I bypassed the antimalaware agent on our server and the transport crashes seem to have stopped, its been 24 hours without it seizing up. Still getting the 10010 events.

    Set-MalwareFilteringServer -BypassFiltering $true

    Wednesday, February 27, 2013 5:29 PM
  • Same problem here... Event 10010 and 6002 - multiple times daily, the server could not receive or send external mails.

    An iisreset solves the problem for a few hours. Because nobody (especially Microsoft) could not provide a solution for this issue, we will configure a scheduled task bound on one of these Event ID to run an IISRESET automatically. Hopefully CU1 will provide an acceptable solution very soon. Exchange 2013 seems more unfinished as expected... The bad thing is, that we realized this just in the production environment and not in our labs and not in our own EXC-organization...

    Hope for a real solution!

    Cheers,

    André

    Monday, March 4, 2013 2:33 PM
  • Opening a ticket with MS today. We'll see how it goes. We're having intermittent outbound mail issues, especially when users send out large batches of emails. They come back from the Exchange server with:

    #550 4.4.7 QUEUE.Expired; message expired ##

    Hard to say for sure these errors are related, but I'll try and get the tech's opinion and point him to the thread as well. The server can resolve and telnet to the distant servers without issue using command line, so I know DNS and firewalls aren't the issue. I've tried restarting some services as a resolution, but bounce backs happen fairly quickly after so I don't think it's helping like the other person in the thread.

    Something interesting to note, at least interesting to me, is bounce backs are always to big names, like Yahoo, Google, and Hotmail. Messages they've sent to us have never been bounced back. They don't mail us with their high volume messages though, so it's hard to say if that would continue to be the case under those circumstances. Our company is on Office365 for mail.

    I'll update as soon as I know something!


    • Edited by TH2TECH Thursday, March 7, 2013 4:13 PM typo
    Thursday, March 7, 2013 4:10 PM
  • Opened a ticket as well, they did just tell me to change a customer receive connector we had for a relay for our CRM server to use the FrontendTransport role rather than the HubTransport role due to a bug.  This is due to having a single server topology.  I actually think I read that somewhere in the forums or elsewhere.  I've made the change and will monitor this and report back if this solves it (for me at least).
    • Edited by TRI-JA Thursday, March 7, 2013 9:41 PM
    Thursday, March 7, 2013 9:34 PM
  • My support rep is also convinced the issues are distant. I know for a fact they aren't because we upgraded from Exchange 2003, everything else is the same, and these issues didn't exist before. In addition, the NDRs come back for a single message sent to many domains, so I'll get an NDR from the local server saying it can't connect to Yahoo, Gmail or Hotmail, all for the same message. There is no way it's distant.

    He did change the order of my NICs. I laughed, because, sure, it may cause delays, but having them out of order wouldn't cause a 48 hour delay. In the mean time, messages to other addresses in the same distant domain will go through before the server gives an NDR for a messages that's been sitting God knows where for 2 days. Finally, this occasionally happens even when sending to a recipient ON THE LOCAL SERVER. In that case, I'm in agreement that it's not best to rule out distant end. ;) 

    On a more interesting note, it does seem the 10010's could be unrelated. We are getting occasional real transport errors, but we're still working on the why. The flood of 10010, 600x, 10xx etc warnings caused by malware scanner and mid-tier storage was pushing the transport errors into obscurity. We've dialed the transport logging way up, and are going to let it monitor for a little while before getting back on. Assuming they don't go away from the "fix" of putting the NICs in the right order. *rolls eyes*

    I suppose, one final note; it doesn't seem as though the messages that come back with NDRs are in the queues before coming back. We were looking at the queues earlier, and there wasn't anything queued to my domain, but a few hours later the client got an NDR for a message sent to my boss (our domain). So, it's as though the messages are hiding somewhere else while waiting to time out. The message was sent 48 hours prior, so there should have been a stalled message in the queue to my domain. Additionally, she was able to send me several messages hours prior, so it wasn't a distant end issue or a routing/DNS issue.

    Friday, March 8, 2013 1:12 AM
  • Opened a ticket as well, they did just tell me to change a customer receive connector we had for a relay for our CRM server to use the FrontendTransport role rather than the HubTransport role due to a bug.  This is due to having a single server topology.  I actually think I read that somewhere in the forums or elsewhere.  I've made the change and will monitor this and report back if this solves it (for me at least).
    We're still getting the 10010 and 6002 errors but our external mail has been flowing without issue since my original post.  It looks like, in this case, it was the bug in the custom receive connectors that caused the issue.  Fingers crossed and good luck.
    Friday, March 8, 2013 3:37 PM
  • Is there a solution for the MSexchange Mid-Tier storage 10010 and 6002 errors. I also have a basic install of windows 2012 with exchange 2013 (AD server is on a other server)
    Wednesday, March 13, 2013 1:18 PM
  • I've opened up another ticket specific to multiple app log events and will update as soon as I hear back.
    Tuesday, March 26, 2013 4:15 PM
  • I am having the same situation. Server 2012 with Exchange 2013. Brand new domain, our entire windows infrastructure is brand new. Everything seems solid, we don't have much put in just yet. The only issues we have seen are with exchange. We are having a ton of MSExchange Mid-Tier Storage "Event ID 10010 and 6002". These are all marked with Warning and seem to happen every 4-6 minutes. The relevance of what these are, I have no idea. Definitely have some homework to do on what exactly is going on behind the scenes. The actual Symptoms we are seeing with Exchange 2013 (whether it has anything to do with the 10010 and 6002 errors, I have no idea) We were seeing a ton of messages getting stuck in our submission que and would receive the delivery failure notification message about 2 days later, (per that setting). Microsoft seems to have been really stuck on the following 3 settings via the exchange management shell"

    Set-RemoteDomain -Identity * -TNEFEnabled $null - appears to have had no effect, messages keep getting stuck

    Set-RemoteDomain -Identity * -TNEFEnabled $false - setting it to this seemed to resolve the issue of messages getting stuck in our submission que (with the error "A Storage Transient error has occurred during content conversion") but once this was set. All attachements were showing up as winmail.dat for the recipients.

    Set-RemoteDomain -Identity * -TNEFEnabled $true - messages still get stuck.

    Anyways, I just wanted to post my findings and experience. I have had NO luck getting a straight answer or response from Microsoft in regards to the MSExchange Mid-Tier Storage warnings are and why I'm having so many of them. And IF they are related to the other issues with exchange we have been having.

    Monday, April 1, 2013 1:41 PM
  • Still waiting for a response from MS, apparently I should have said all my systems are down.
    Friday, April 5, 2013 6:49 PM
  • So, I've finished troubleshooting with MS. My guy more or less refused to look into the Mid-Tier storage issues, saying it wasn't related at all. I asked him if he could look into them anyway, because I feel like a brand new install on a brand new domain shouldn't be getting them, as well as pointing him here. He said he would send it over to the team that would look at it. When I asked him later he said he never said he would do that, and that he wasn't going to. 'The issue is unrelated, and outside the scope of the ticket' bla bla bla. It was very frustrating.

    As it turns out though, they are unrelated. The NDRs I was getting were because there is a known issue in Exchange 2013 that prevents Rich-Text messages. The problem with this is several of our clients messages come in as RT, so the workaround is to have them change the message to HTML. Support said the issue would be addressed in the first service pack, but couldn't provide a projected date. All of this is making me feel more and more like Exchange 2013 isn't ready, and that MS really shot themselves in the foot when they released Server 2012 without the ability to deploy Exchange 2010. I usually wait until SP1 comes out before installing a newer version of Exchange, but have never done that for the OS. I didn't know Ex2010 wasn't compatible until I went to install it and it wouldn't. Now all this.

    Anyway, I hope the fact that there is a known issue with Rich-Text messages will help someone. What a joke this whole process has been. Sorry for taking so long to get back, but I really don't have anything helpful to say in regards to the topic.

    TL;DR - My issue sending mail resolved, unrelated to mid-tier storage events. Support refused to look into them.
    • Edited by TH2TECH Friday, April 5, 2013 7:30 PM
    Friday, April 5, 2013 7:27 PM
  • Hey Jacob, see my reply. The winmail.dat attachment means you're also sending as Rich-Text. I had the same issues as you, and hopefully teaching users to send in HTML will resolve it for you as for me. Expect a fix in SP1 for Exchange 2013. Sucks, right?
    Friday, April 5, 2013 7:33 PM
  • Sorry to hear that, support team denied to help you in this issue. You should have asked for escalation on the same.

    winmail.dat is know issue and most of the time it happened when you have BB in the environment and when content conversion comes in picture. I don't agree what they said about it. Hopefully someone will find out more about the issue with 2013 and update the thread.


    Gulab Prasad,
    Exchange Ranger
    Z-Hire Employee Provisioning App

    Friday, April 5, 2013 7:46 PM
  • Same issues here - brand new servers, WS2012, Exchange 2013, installed, wiped out, and re-installed again, with constant updates and restarts.  The 10010 and 6002 events are getting really annoying.

    .

    This thread is 4 months old, and no progress has been made in solving this?

    .

    Doc


    Computers verified since 1972

    Tuesday, April 9, 2013 12:25 AM
  • Has anyone tried the CU1 update for Exchange 2013 server.  It can be found here: http://www.microsoft.com/en-us/download/details.aspx?id=38176

    Bradley

    • Proposed as answer by BradleySCS Tuesday, April 9, 2013 12:29 AM
    Tuesday, April 9, 2013 12:28 AM
  • this is the new standard of support for microsoft, sadly

    they really think having half-educated indians spam boilerplate responses to technet forums is as hard as they need to work

    I submitted a daylight savings time bug and the MS support guy refused to work on it because he didn't know how to reproduce the time change

    you know, the time change that happens on a specific date and time on a computer with a user-configurable date and time

    at that point I realized that encountering a bug in windows means you are on your own...so plan accordingly

    Tuesday, April 9, 2013 12:29 AM
  • BradleySCS, THANKS!

    Although the download is huge, and the time required to update is significant, the decrease in memory usage is shocking and the cpu utilization is reduced.  And, the errors are fewer.  Not eliminated, but fewer.

    .

    The 10010 seems to be gone.  I'll let it run for a bit and report back.  Still, this is a very nice improvement!

    .

    Doc


    Computers verified since 1972


    Tuesday, April 9, 2013 4:32 AM
  • Dr Strangelove, glad that worked! We plan to install it on one of our servers this week.  Hopefully it does the trick for us also.

    Please mark my post as the "proposed answer" since it looks like someone else marked it as "Abuse" for some crazy reason.  Must have been that guy who's pissed off at MS support. :)

    • Edited by BradleySCS Tuesday, April 9, 2013 4:51 AM Add request to mark as proposed answer
    • Proposed as answer by Dr. Strangelove Tuesday, April 9, 2013 5:00 AM
    Tuesday, April 9, 2013 4:50 AM
  • Ok, after 30 minutes up, 10010 has not occurred. 6002 has only occurred once (at startup).  1309 has not occurred.

    So, these repeating errors appear to have been addressed quite nicely by this update.

    Before CU1, on a ws2012 member server, with only exchange 2013, cpu was hovering around 6 to 7%.

    Now, it is hovering around 2 to 3%.

    And, memory usage before was roughly 5gb (total).  Now it is 3.8gb (roughly). 

    These are not exact numbers.  Just observations from task manager.

    .

    Doc


    Computers verified since 1972



    Tuesday, April 9, 2013 4:53 AM
  • I could not mark your post as proposed answer, probably because of the abuse report.  However, I did mark as helpful and proposed as answer your last post.

    When you do install it, check the memory and cpu, before and after. 

    .

    Also, I may have spoken too soon about 6002.  Looks like it occurs about every 30 minutes or so.  Still, an improvement, eh?<G>

    Cheers,

    Doc


    Computers verified since 1972


    Tuesday, April 9, 2013 5:02 AM
  • Exchange 2013 CU1 fix the most of the event logs. I updated 2 installations, the 10010 errors are gone. There is still the 6002 warning, which occurs every 30 min, like doc described:

    Ping of mdb 'xxx' timed out after '00:00:00' minutes.  Last successful ping was at '09.04.2013 05:37:52' UTC.
    How the other mention, reserve some time for the update, it tooks at me for every installation around 1-2 hours (!). Looking forward to CU2 to fix the 6002 event.
    Tuesday, April 9, 2013 5:52 AM
  • Tried and now even worse :( I had a script that detected SMTP receive hang and rebooted the server automatically. Not pretty, but has kept our brand new 2013 server running for the last month. Tried the CU1 but it failed - see http://social.technet.microsoft.com/Forums/en-US/exchangesvrdeploy/thread/a8f0d480-f844-4a1f-87b8-7b0df9fa06e3?prof=required. Essentially error on a step whilst updating the mailbox role transport service. Now I can't uninstall or complete the install - I have *no* exchange server at all...

    Chris

    Tuesday, April 9, 2013 9:16 AM
  • I'm downloading now. I'll install tonight, and report back tomorrow. Taking CLMSSP's experience into consideration, I will double check backups before pulling the trigger though. I'll also post other performance metrics for comparison to other's experiences.
    Tuesday, April 9, 2013 3:52 PM
  • I have installed CU1 and There is still the 6002 error. The 10010 error seems to be gone.

    When you start the update and there are some requirements not fixed you must fix these and continue, you cannot abort the installation for a later time because Exchange wont be working any more. ( in my case) After completing the update ( takes about 1 hour) all worked again after reboot

     
    Thursday, April 11, 2013 1:31 PM
  • I have installed CU1 and There is still the 6002 error. The 10010 error seems to be gone.

    When you start the update and there are some requirements not fixed you must fix these and continue, you cannot abort the installation for a later time because Exchange wont be working any more. ( in my case) After completing the update ( takes about 1 hour) all worked again after reboot

     
    I have come across the same thing. I did the CU1 the 10010 is gone but I still get the 6002. 
    Friday, August 16, 2013 3:54 PM
  • Install CU2, that might solve you problems: http://www.microsoft.com/en-us/download/details.aspx?id=39609

    Friday, August 16, 2013 5:03 PM
  • I installed CU2v2 and these events seem to have vanished.

    I've got other ones in stead, but that's a different thread.


    Leo

    Sunday, August 18, 2013 8:39 AM
  • I installed CU2v2 and these events seem to have vanished.

    I've got other ones in stead, but that's a different thread.


    Leo

    We have recently done the CU2v2 update but are still getting a range of these errors. Anyone else?

    Thanks


    RKD993

    Monday, August 26, 2013 5:37 AM
  • I am experiencing the same issue with 2 Exchange 2013 servers CU2 build, running in a dag with cas/hub on same boxes.

    I've been trying to focus on the 6002 errors to see if there is some kind of pattern to the events. and its looks to me that the logs starts by hitting the event log 5 times per hour, then it increases with 1 every hour until it reaches 10 where the cycle restarts.

    This was originally a RC1 install that I removed with a complete AD cleanup and then reinstalled both servers with CU2.

    Thanks

    Sebastian


    • Edited by Sadlercreutz Thursday, September 19, 2013 9:48 PM spelling error
    Thursday, September 19, 2013 9:46 PM
  • For what it is worth our problems have been resolved by rebuilding all the connectors using the very specific 2013 patterns and specs. 2010 type connectors only "sort of" work. Search for:

    social.technet.microsoft.com/Forums/exchange/en-US/cd03793b-9e99-474e-8f25-11275652882f/exchange-2013-stops-receiving-external-email-after-about-8-hours

    The problem was sporadic enough that it took a lot of effort to track it down.

    Happy hunting.

    Thursday, September 19, 2013 10:50 PM
  • I started having the issue after creating an internal receive connector using port 25 for email relay for a Rancid server.

    The problem starts when we set the port to 25 for SMTP but when an exchange server is setup with all roles on the same server the FrontEnd Receive Connectors use port 25 and the Hub connectors use port 2525.

    You have to make FrontEnd Transport Receive connectors for mail relay in these dual roll situations as they use port 25. This seems not the "normal way" of building a relay receive connector because Microsoft assume you run the roles on different servers. / Cheers, Morten, Denmark itnotes.eu


    • Edited by Dintid Monday, October 28, 2013 7:04 AM
    • Proposed as answer by Dintid Monday, October 28, 2013 7:04 AM
    Monday, October 28, 2013 7:01 AM