How to troubleshoot Exchange Web Services error message when attempting to contact the Symantec Email Submission Client (SESC) service: "A notification for subscription...couldn't be sent

Article:HOWTO73171  |  Created: 2012-02-24  |  Updated: 2014-06-30  |  Article URL http://www.symantec.com/docs/HOWTO73171
Article Type
How To



SESC is configured to communicate with the Exchange Client Access Server (CAS).  On the CAS server one of the following events appears in the Windows Application Event log:

Log Name:      Application
Source:        MSExchange Web Services
Date:          1/31/2012 9:29:59 AM
Event ID:      5
Task Category: Core
Level:         Warning
Keywords:      Classic
User:          N/A
Computer:      WIN-P5723T9FPJQ.benexchange2010.internal
Description:
A notification for subscription [KAB3aW4tcDU3MjN0OWZwanEuYmVuZXhjaGFuZ2UyMDEwLmludGVybmFsEAAAAC72uCHhwK1OqGxdTmWUxeKcf3hqcq3OCA==] against endpoint [http://sesc1.benexchange2010.internal:8081/service.asmx] couldn't be sent. The operation will be retried. Details: WebException: Unable to connect to the remote server Status: ConnectFailure    at System.Net.HttpWebRequest.EndGetRequestStream(IAsyncResult asyncResult, TransportContext& context)
   at System.Net.HttpWebRequest.EndGetRequestStream(IAsyncResult asyncResult)
   at Microsoft.Exchange.Services.Core.NotificationServiceClient.CreateSendNotificationRequestAsync(IAsyncResult requestAsyncResult)

The message above is reported the first time that the Exchange EWS service is unable to send a Push notification for an SESC subscription.  Note that the message indicates the Push notification will be tried again.

Log Name:      Application
Source:        MSExchange Web Services
Date:          1/31/2012 9:30:59 AM
Event ID:      6
Task Category: Core
Level:         Warning
Keywords:      Classic
User:          N/A
Computer:      WIN-P5723T9FPJQ.benexchange2010.internal
Description:
A notification for subscription [KAB3aW4tcDU3MjN0OWZwanEuYmVuZXhjaGFuZ2UyMDEwLmludGVybmFsEAAAAC72uCHhwK1OqGxdTmWUxeKcf3hqcq3OCA==] against endpoint [http://sesc1.benexchange2010.internal:8081/service.asmx] couldn't be sent. (Send attempts: 2) Details: WebException: Unable to connect to the remote server Status: ConnectFailure    at System.Net.HttpWebRequest.EndGetRequestStream(IAsyncResult asyncResult, TransportContext& context)
   at System.Net.HttpWebRequest.EndGetRequestStream(IAsyncResult asyncResult)
   at Microsoft.Exchange.Services.Core.NotificationServiceClient.CreateSendNotificationRequestAsync(IAsyncResult requestAsyncResult)

The message above is reported after the first time that the Exchange EWS service is unable to send a Push notification for an SESC subscription.  Note the message indicates the number of attempts made.  EWS will attempt additional notifications.

Log Name:      Application
Source:        MSExchange Web Services
Date:          2/1/2012 7:37:41 PM
Event ID:      7
Task Category: Core
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      WIN-P5723T9FPJQ.benexchange2010.internal
Description:
After 13 unsuccessful attempts to send a notification for subscription [KAB3aW4tcDU3MjN0OWZwanEuYmVuZXhjaGFuZ2UyMDEwLmludGVybmFsEAAAACBMnYiPEtdCr7Diqmq6EfGcf3hqcq3OCA==] against endpoint [http://sesc1.benexchange2010.internal:8081/service.asmx], the subscription has been removed. Details: WebException: Unable to connect to the remote server Status: ConnectFailure    at System.Net.HttpWebRequest.EndGetRequestStream(IAsyncResult asyncResult, TransportContext& context)
   at System.Net.HttpWebRequest.EndGetRequestStream(IAsyncResult asyncResult)
   at Microsoft.Exchange.Services.Core.NotificationServiceClient.CreateSendNotificationRequestAsync(IAsyncResult requestAsyncResult)

The message above is reported after all attempts at sending the notification fail.  The subscription is then removed by EWS.  SESC will receive no further notifications for the subscription.

The error message contains the details of why the notification could not be sent.  In the cases above it is "Unable to connect to the remote server Status: ConnectFailure".

You may notice one of the following symptoms:

  • Email put into an email submission folder is never removed
  • The email submission folder is not recreated if the user deletes it.

Here are some troubleshooting steps:

1. Perform a search in the Symantec knowledge base for the error message.

Click here for the Symantec Mail Security for Microsoft Exchange knowledgebase.
Click here for the Symantec Brightmail Gateway knowledgebase.

2. Attempt to use the URL from a browser and troubleshoot the error reported. 

NOTE:  The browser may prompt for an authentication dialog.  Enter the SESC service account information.

Environment

  • SESC 1.X

 




Article URL http://www.symantec.com/docs/HOWTO73171


Terms of use for this information are found in Legal Notices