none
Need help desperately on my exchange 2013 issue!! Pls

    Question

  • Hi Team,

    I am looking for desperate help on the exchange 2013 issue I am facing for almost 10-15 days I am really running out of ideas.

    I have around 150 users and have internal exchange server where all the roles are deployed on same server. Even have latest CU installed. Recently almost a month back I started facing issue where suddenly exchange stops the complete mail flow and mail accumulates on my MX. I dont rememeber the error but when I try to telnet it exchange from my mx it gives me Proxy 504 error.

    Restarting the server defintiely solves the issue but again after 2-3 days issue recoccurs. Even EMS does not get connected.

    Hence after much troubleshooting we decided to go with 2016 since we can not afford Microsoft Online help. So we built parallel server and built 2016. However then we noticed that some of the users aren't receiving couple of mails and users starts getting disconnected automatically/randomly. Hence we had to shut down the server and we took mapi debug logs and here are those.

    Can someone please help me on the issue???

    2018.04.04 11:21:37 <<<< Logging Started (level is LTF_TRACE) >>>>
    2018.04.04 11:21:37 HELPER::Initialize called
    2018.04.04 11:21:37 Initializing: Finding a Transport
    2018.04.04 11:21:37 MAPI XP Call: XPProviderInit in EMSMDB.DLL, hr = 0x00000000
    2018.04.04 11:21:38 MAPI Status: (-- -- ---/--- -- ---)
    2018.04.04 11:21:38 MAPI XP Call: TransportLogon, hr = 0x00000000
    2018.04.04 11:21:38 Initializing: Found a transport, Error code = 0x00000000
    2018.04.04 11:21:38 MAPI XP Call: AddressTypes, hr = 0x00000000, cAddrs = 3, cUids = 1
    2018.04.04 11:21:38 MAPI Status: (IN -- ---/OUT -- ---)
    2018.04.04 11:21:38 MAPI XP Call: TransportNotify(BEGIN_IN|BEGIN_OUT), hr = 0x00000000
    2018.04.04 11:21:38 HELPER::Initialize done, Error code = 0x00000000
    2018.04.04 11:21:38 HELPER::GetCapabilities called, Error code = 0x00000000


    ...............................................



    2018.04.04 11:28:03 <<<< Logging Started (level is LTF_TRACE) >>>>
    2018.04.04 11:28:04 HELPER::Initialize called
    2018.04.04 11:28:04 Initializing: Finding a Transport
    2018.04.04 11:28:04 MAPI XP Call: XPProviderInit in EMSMDB.DLL, hr = 0x00000000
    2018.04.04 11:28:04 MAPI Status: (-- -- ---/--- -- ---)
    2018.04.04 11:28:04 MAPI XP Call: TransportLogon, hr = 0x00000000
    2018.04.04 11:28:04 Initializing: Found a transport, Error code = 0x00000000
    2018.04.04 11:28:04 MAPI XP Call: AddressTypes, hr = 0x00000000, cAddrs = 3, cUids = 1
    2018.04.04 11:28:04 MAPI Status: (IN -- ---/OUT -- ---)
    2018.04.04 11:28:04 MAPI XP Call: TransportNotify(BEGIN_IN|BEGIN_OUT), hr = 0x00000000
    2018.04.04 11:28:04 HELPER::Initialize done, Error code = 0x00000000
    2018.04.04 11:28:04 HELPER::GetCapabilities called, Error code = 0x00000000
    2018.04.04 11:32:23 HELPER::Uninitialize called
    2018.04.04 11:32:23 MAPI Status: (-- -- ---/--- -- ---)
    2018.04.04 11:32:23 MAPI XP Call: TransportNotify(END_IN|END_OUT), hr = 0x00000000
    2018.04.04 11:32:23 MAPI XP Call: TransportLogoff in EMSMDB.DLL, hr = 0x00000000
    2018.04.04 11:32:23 



    2018.04.04 11:32:23 Resource manager terminated


    2018.04.04 11:32:51 <<<< Logging Started (level is LTF_TRACE) >>>>
    2018.04.04 11:32:51 HELPER::Initialize called
    2018.04.04 11:32:51 Initializing: Finding a Transport
    2018.04.04 11:32:51 MAPI XP Call: XPProviderInit in EMSMDB.DLL, hr = 0x00000000
    2018.04.04 11:33:06 MAPI Status: (-- -- ---/--- -- ---)
    2018.04.04 11:33:06 MAPI XP Call: TransportLogon, hr = 0x00000000
    2018.04.04 11:33:06 Initializing: Found a transport, Error code = 0x00000000
    2018.04.04 11:33:06 MAPI XP Call: AddressTypes, hr = 0x00000000, cAddrs = 3, cUids = 1
    2018.04.04 11:33:06 MAPI XP Call: TransportNotify(BEGIN_IN|BEGIN_OUT), hr = 0x00000000
    2018.04.04 11:33:06 HELPER::Initialize done, Error code = 0x00000000
    2018.04.04 11:33:06 HELPER::GetCapabilities called, Error code = 0x00000000
    2018.04.04 11:33:07 HELPER::Uninitialize called
    2018.04.04 11:33:07 MAPI XP Call: TransportNotify(END_IN|END_OUT), hr = 0x00000000
    2018.04.04 11:33:07 MAPI XP Call: TransportLogoff in EMSMDB.DLL, hr = 0x00000000
    2018.04.04 11:33:07 MAPI XP Call: Shutdown, hr = 0x00000000
    2018.04.04 11:33:07 Resource manager terminated


    2018.04.04 11:34:16 <<<< Logging Started (level is LTF_TRACE) >>>>
    2018.04.04 11:34:16 HELPER::Initialize called
    2018.04.04 11:34:16 Initializing: Finding a Transport
    2018.04.04 11:34:16 MAPI XP Call: XPProviderInit in EMSMDB.DLL, hr = 0x00000000
    2018.04.04 11:36:44 MAPI Status: (-- -- ---/--- -- ---)
    2018.04.04 11:36:44 MAPI XP Call: TransportLogon, hr = 0x00000000
    2018.04.04 11:36:44 Initializing: Found a transport, Error code = 0x00000000
    2018.04.04 11:36:44 MAPI XP Call: AddressTypes, hr = 0x00000000, cAddrs = 3, cUids = 1
    2018.04.04 11:36:44 MAPI XP Call: TransportNotify(BEGIN_IN|BEGIN_OUT), hr = 0x00000000
    2018.04.04 11:36:44 HELPER::Initialize done, Error code = 0x00000000
    2018.04.04 11:36:44 HELPER::GetCapabilities called, Error code = 0x00000000
    2018.04.04 11:38:44 MAPI Status: (IN -- ---/OUT -- ---)
    2018.04.04 11:55:31 v.p@xyz.com: Synch operation started (flags = 00000001)
    2018.04.04 11:55:31 v.p@xyz.com: UploadItems: 1 messages to send
    2018.04.04 11:55:31 EXECUTING Put MAPI TASK
    2018.04.04 11:55:31 Starting the Spooling Cycle
    2018.04.04 11:55:31 MAPI Status: (IN -- ---/OUT fl ---)
    2018.04.04 11:55:31 MAPI XP Call: FlushQueues, hr = 0x00000000, ulFlushFlags = 0x0000001a
    2018.04.04 11:55:31 Sending one message
    2018.04.04 11:55:31 Progress: Sending message 'TPX ( X004ORG )' (size 6167.68 KBytes)
    2018.04.04 11:55:31 MAPI Status: (IN -- ---/OUT fl act)
    2018.04.04 11:56:15 MAPI Status: (IN -- ---/OUT fl ---)
    2018.04.04 11:56:15 MAPI XP Call: SubmitMessage, hr = 0x00000000
    2018.04.04 11:56:15 MAPI XP Call: EndMessage, hr = 0x00000000
    2018.04.04 11:56:15 FINISHED MAPI TASK
    2018.04.04 11:56:15 v.p@xyz.com: ReportStatus: RSF_COMPLETED, hr = 0x00000000
    2018.04.04 11:56:15 v.p@xyz.com: Synch operation completed
    2018.04.04 11:56:15 Sending done, Error code = 0x00000000
    2018.04.04 11:56:15 Sending done, Error code = 0x8004010f
    2018.04.04 11:56:15 MAPI Status: (IN -- ---/OUT -- ---)
    2018.04.04 11:56:15 Finishing the Spooling Cycle, Error code = 0x00000000
    2018.04.04 11:57:31 HELPER::Uninitialize called
    2018.04.04 11:57:31 MAPI Status: (-- -- ---/--- -- ---)
    2018.04.04 11:57:31 MAPI XP Call: TransportNotify(END_IN|END_OUT), hr = 0x00000000
    2018.04.04 11:57:31 MAPI XP Call: TransportLogoff in EMSMDB.DLL, hr = 0x00000000
    2018.04.04 11:57:31 MAPI XP Call: Shutdown, hr = 0x00000000
    2018.04.04 11:57:31 Resource manager terminated


    2018.04.04 12:10:11 <<<< Logging Started (level is LTF_TRACE) >>>>
    2018.04.04 12:10:11 HELPER::Initialize called
    2018.04.04 12:10:11 Initializing: Finding a Transport
    2018.04.04 12:10:11 MAPI XP Call: XPProviderInit in EMSMDB.DLL, hr = 0x00000000
    2018.04.04 12:10:12 MAPI Status: (-- -- ---/--- -- ---)
    2018.04.04 12:10:12 MAPI XP Call: TransportLogon, hr = 0x00000000
    2018.04.04 12:10:12 Initializing: Found a transport, Error code = 0x00000000
    2018.04.04 12:10:12 MAPI XP Call: AddressTypes, hr = 0x00000000, cAddrs = 3, cUids = 1
    2018.04.04 12:10:12 MAPI Status: (IN -- ---/OUT -- ---)
    2018.04.04 12:10:12 MAPI XP Call: TransportNotify(BEGIN_IN|BEGIN_OUT), hr = 0x00000000
    2018.04.04 12:10:12 HELPER::Initialize done, Error code = 0x00000000
    2018.04.04 12:10:12 HELPER::GetCapabilities called, Error code = 0x00000000



    Thanks, Blason R

    Sunday, April 15, 2018 1:39 PM

All replies

  • I am certainly no expert with exchange. But i would offer the following.

    https://blogs.technet.microsoft.com/exchange/2004/06/18/repairing-exchange-databases-with-eseutil-when-and-how/

    You have to dismount the database first, but you can make a copy of edb file and immediately remount it to keep exchange offline for shortest time possible.

    Then run the utilities on your copy. If errors are found and corrected, then replace your original file with the repaired one. Keep a copy of the original unaltered file of course, just in case. 

    Sunday, April 15, 2018 2:04 PM
  • hmm may be I need to try that since I am really frustrated with the issue.

    Thanks, Blason R

    Sunday, April 15, 2018 2:12 PM
  • Hi

    So you built a new server, did you import your SSL cert and assign services to it? did you change your urls on exchange?

    Do you have any AV on the server? are the exclusions set correctly?

    Did you check your transport agents to see if one of them is not causing the mailflow issue?

    @Jim, ESEUTIL if not run correctly can result in complete dataloss. 


    Hope this helps. Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

    Monday, April 16, 2018 5:05 AM
    Moderator
  • Can you confirm that you have enough diskspace for all your drives? 

    Please mark as helpful if you find my contribution useful or as an answer if it does answer your question. That will encourage me - and others - to take time out to help you. Thank you! Off2work

    Monday, April 16, 2018 5:50 AM
  • Hi

    So you built a new server, did you import your SSL cert and assign services to it? did you change your urls on exchange?

    Do you have any AV on the server? are the exclusions set correctly?

    Did you check your transport agents to see if one of them is not causing the mailflow issue?

    @Jim, ESEUTIL if not run correctly can result in complete dataloss. 


    Hope this helps. Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

    Correct I did build a new server have imported cert and haven't changed the URLs since my 2013 is already production.

    I do have AV on server however that should not be any issue as I am seeing in the logs.


    Thanks, Blason R

    Monday, April 16, 2018 10:27 AM