locked
Exchange server 2013 Application logic Errors RRS feed

  • Question

  • Dear Experts,

    We’re having some errors in Event viewer logs of our Exchange server. Please have a look into it advise us how we can solve it or what we have to do.

    EventID - 3018 MSExchangeApplicationLogic

    Scenario: GetKillBit.GetKillBit. The request failed. Mailbox:  Url: https://store.office.com/appinfo/query?rt=XML Exception: System.Net.WebException: The underlying connection was closed: An unexpected error occurred on a send. ---> System.IO.IOException: Unable to read data from the transport connection: An existing connection was forcibly closed by the remote host. ---> System.Net.Sockets.SocketException: An existing connection was forcibly closed by the remote host
       at System.Net.Sockets.Socket.EndReceive(IAsyncResult asyncResult)
       at System.Net.Sockets.NetworkStream.EndRead(IAsyncResult asyncResult)
       --- End of inner exception stack trace ---
       at System.Net.TlsStream.EndWrite(IAsyncResult asyncResult)
       at System.Net.ConnectStream.WriteHeadersCallback(IAsyncResult ar)
       --- End of inner exception stack trace ---
       at System.Net.HttpWebRequest.EndGetResponse(IAsyncResult asyncResult)
       at Microsoft.Exchange.Data.ApplicationLogic.Extension.BaseAsyncOmexCommand.<>c__DisplayClass2.<EndGetResponseCallback>b__1()

    EventID - 3025 MSExchangeApplicationLogic

    Scenario: GetKillBit. Failed to download killbit list from OMEX server. Exception: System.Net.WebException: The underlying connection was closed: An unexpected error occurred on a send. ---> System.IO.IOException: Unable to read data from the transport connection: An existing connection was forcibly closed by the remote host. ---> System.Net.Sockets.SocketException: An existing connection was forcibly closed by the remote host

       at System.Net.Sockets.Socket.EndReceive(IAsyncResult asyncResult)
       at System.Net.Sockets.NetworkStream.EndRead(IAsyncResult asyncResult)
       --- End of inner exception stack trace ---
       at System.Net.TlsStream.EndWrite(IAsyncResult asyncResult)
       at System.Net.ConnectStream.WriteHeadersCallback(IAsyncResult ar)
       --- End of inner exception stack trace ---
       at System.Net.HttpWebRequest.EndGetResponse(IAsyncResult asyncResult)
       at Microsoft.Exchange.Data.ApplicationLogic.Extension.BaseAsyncOmexCommand.<>c__DisplayClass2.<EndGetResponseCallback>b__1()


    • Edited by MISSC1972 Monday, March 9, 2020 11:01 AM
    Monday, March 9, 2020 7:23 AM

Answers

All replies

  • Details of Log:

    EventID - 3018 MSExchangeApplicationLogic

    Scenario: GetKillBit.GetKillBit. The request failed. Mailbox:  Url: https://store.office.com/appinfo/query?rt=XML Exception: System.Net.WebException: The underlying connection was closed: An unexpected error occurred on a send. ---> System.IO.IOException: Unable to read data from the transport connection: An existing connection was forcibly closed by the remote host. ---> System.Net.Sockets.SocketException: An existing connection was forcibly closed by the remote host
       at System.Net.Sockets.Socket.EndReceive(IAsyncResult asyncResult)
       at System.Net.Sockets.NetworkStream.EndRead(IAsyncResult asyncResult)
       --- End of inner exception stack trace ---
       at System.Net.TlsStream.EndWrite(IAsyncResult asyncResult)
       at System.Net.ConnectStream.WriteHeadersCallback(IAsyncResult ar)
       --- End of inner exception stack trace ---
       at System.Net.HttpWebRequest.EndGetResponse(IAsyncResult asyncResult)
       at Microsoft.Exchange.Data.ApplicationLogic.Extension.BaseAsyncOmexCommand.<>c__DisplayClass2.<EndGetResponseCallback>b__1()

    EventID - 3025 MSExchangeApplicationLogic

    Scenario: GetKillBit. Failed to download killbit list from OMEX server. Exception: System.Net.WebException: The underlying connection was closed: An unexpected error occurred on a send. ---> System.IO.IOException: Unable to read data from the transport connection: An existing connection was forcibly closed by the remote host. ---> System.Net.Sockets.SocketException: An existing connection was forcibly closed by the remote host

       at System.Net.Sockets.Socket.EndReceive(IAsyncResult asyncResult)
       at System.Net.Sockets.NetworkStream.EndRead(IAsyncResult asyncResult)
       --- End of inner exception stack trace ---
       at System.Net.TlsStream.EndWrite(IAsyncResult asyncResult)
       at System.Net.ConnectStream.WriteHeadersCallback(IAsyncResult ar)
       --- End of inner exception stack trace ---
       at System.Net.HttpWebRequest.EndGetResponse(IAsyncResult asyncResult)
       at Microsoft.Exchange.Data.ApplicationLogic.Extension.BaseAsyncOmexCommand.<>c__DisplayClass2.<EndGetResponseCallback>b__1()

    Monday, March 9, 2020 11:02 AM
  • Hi,

    What's the detailed version of your Exchange 2013? 

    Does your Exchange server have an internet connection?

    As is mentioned by the article provided by Udara Kaushalya (MSExchangeApplicationLogic Event 3018 in Exchange Server 2013 and 2016), you can check the proxy server to make sure the URL mentioned in the event log is enabled for access.

    Additionally, please set these two registry values then check if it works:

    [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\.NETFramework\v4.0.30319] "SystemDefaultTlsVersions"=dword:00000001 [HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\.NETFramework\v4.0.30319] "SystemDefaultTlsVersions"=dword:00000001

    Here is a similar issue for your reference: Event MSExchangeApplicationLogic 3025 & 3018

    Regards,

    Lydia Zhou


    Please remember to mark the replies as answers if they helped. If you have feedback for TechNet Subscriber Support, contact tnsf@microsoft.com.

    Tuesday, March 10, 2020 6:42 AM
  • Dear Lydia/Experts,

    Thank your for your valuable support.

    It's Exchange 2013 Version 15.0 ‎(Build 847.32).

    Yes, it has Internet connection. Our emails (local-remote inbound/outbound connections) are working fine. Please have a look into it advise us how we can solve it or what we have to do. Will this effect any kind of server issues?

    Tuesday, March 10, 2020 10:35 AM
  • Dear Lydia/Experts,

    Thank your for your valuable support.

    It's Exchange 2013 Version 15.0 ‎(Build 847.32).

    Yes, it has Internet connection. Our emails (local-remote inbound/outbound connections) are working fine. Please have a look into it advise us how we can solve it or what we have to do. Will this effect any kind of server issues?

    Are you sure about that build number? thats SP1 (CU4)  and is over 6 years old! If so, you need to upgrade to CU23. Alot of things have been fixed in the last 6 years.
    Tuesday, March 10, 2020 11:24 AM
  • Dear Andy/Experts,

    Thank you for your valuable feedback.

    I verified and confirmed the version via Exchange Admin panel and installation programs. 

    Can I directly install CU23 (https://support.microsoft.com/en-us/help/4489622/cumulative-update-23-for-exchange-server-2013) from current version, Exchange 2013 Version 15.0 ‎(Build 847.32) CU4.  

    Please confirm and steps to taken for this update.

    Tuesday, March 10, 2020 1:44 PM
  • Dear Andy/Experts,

    Thank you for your valuable feedback.

    I verified and confirmed the version via Exchange Admin panel and installation programs. 

    Can I directly install CU23 (https://support.microsoft.com/en-us/help/4489622/cumulative-update-23-for-exchange-server-2013) from current version, Exchange 2013 Version 15.0 ‎(Build 847.32) CU4.  

    Please confirm and steps to taken for this update.

    Yes.

    https://docs.microsoft.com/en-us/exchange/plan-and-deploy/prepare-ad-and-domains?view=exchserver-2019

    https://docs.microsoft.com/en-us/exchange/plan-and-deploy/supportability-matrix?view=exchserver-2019

    When upgrading Exchange from an unsupported CU to the current CU and no intermediate CUs are available, you should first upgrade to the latest version of .NET that's supported by Exchange and then immediately upgrade to the current CU. This method doesn't replace the need to keep your Exchange servers up to date and on the latest supported CU. Microsoft makes no claim that an upgrade failure will not occur using this method, which may result in the need to contact Microsoft Support Services.

    • Marked as answer by MISSC1972 Tuesday, March 17, 2020 1:57 PM
    Tuesday, March 10, 2020 2:47 PM
  • If you worry about the modification can cause more issues, you can back up the registry before you modify it. Then, you can restore the registry if a problem occurs.

    Additionally, please also take the suggestions provided by the official blog into consideration, if the registry values don't work.

    Regards,

    Lydia Zhou


    Please remember to mark the replies as answers if they helped. If you have feedback for TechNet Subscriber Support, contact tnsf@microsoft.com.

    Thursday, March 12, 2020 8:47 AM
  • Dear Lydia,

    Thank for your valuable support.

    It would be great if you can share the precaution to be taken care of such as backup of mailbox database, roles, registry values etc..

    Tuesday, March 17, 2020 1:57 PM
  • You can use Windows Server Backup to backup Exchange data. You can check this for more details: Using Windows Server Backup to back up and restore Exchange data.

    For more information about how to back up and restore the registry, view the following article: How to back up and restore the registry in Windows.

    Regards,

    Lydia Zhou


    Please remember to mark the replies as answers if they helped. If you have feedback for TechNet Subscriber Support, contact tnsf@microsoft.com.

    Wednesday, March 18, 2020 3:06 AM
  • It's great that you can get useful information in our forum. Here is a brief summary for replies above.

    Issue Symptom:

    We’re having some errors in Event viewer logs of our Exchange server.

    EventID - 3018 MSExchangeApplicationLogic & EventID - 3025 MSExchangeApplicationLogic

    Suggestions:

    As is mentioned by the article provided by Udara Kaushalya (MSExchangeApplicationLogic Event 3018 in Exchange Server 2013 and 2016), you can check the proxy server to make sure the URL mentioned in the event log is enabled for access.

    Additionally, please set these two registry values then check if it works:

    [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\.NETFramework\v4.0.30319] "SystemDefaultTlsVersions"=dword:00000001 [HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\.NETFramework\v4.0.30319] "SystemDefaultTlsVersions"=dword:00000001

    Since the Exchange server is an old version, it's suggested to upgrade to the latest version. Something may be fixed automatically.

    Reference Link:

    MSExchangeApplicationLogic Event 3018 in Exchange Server 2013 and 2016

    Event MSExchangeApplicationLogic 3025 & 3018

    Regards,

    Lydia Zhou


    Please remember to mark the replies as answers if they helped. If you have feedback for TechNet Subscriber Support, contact tnsf@microsoft.com.

    Monday, March 23, 2020 1:28 AM