Symantec Email Submission Client (SESC) reports error "Provisioning error. The request failed. Unable to connect to the remote server." when Client Access Server (CAS) URL is unavailable

book

Article ID: 155932

calendar_today

Updated On:

Products

Mail Security for Microsoft Exchange Messaging Gateway

Issue/Introduction

SESC is unable to create folders or remove folders when CAS URL is unavailable.

  • The following error is displayed in the Windows Application Event log:

Log Name:      Application
Source:        Symantec Email Submission Client
Date:          2/16/2012 7:32:01 AM
Event ID:      14
Task Category: Subscription
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      sesc-3.2k8domain.test
Description:
Provisioning error.
The request failed. Unable to connect to the remote server.

 

  • The following error appears in the SESC debug log:

[::]2012-02-16 07:32:00,888, [38], ERROR, Symantec.Submission.Exchange.Client.ExchangeFolder, [email protected][::]
Microsoft.Exchange.WebServices.Data.ServiceRequestException: The request failed. Unable to connect to the remote server ---> System.Net.WebException: Unable to connect to the remote server ---> System.Net.Sockets.SocketException: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond 10.192.2.100:443
   at System.Net.Sockets.Socket.DoConnect(EndPoint endPointSnapshot, SocketAddress socketAddress)
   at System.Net.ServicePoint.ConnectSocketInternal(Boolean connectFailure, Socket s4, Socket s6, Socket& socket, IPAddress& address, ConnectSocketState state, IAsyncResult asyncResult, Int32 timeout, Exception& exception)
   --- End of inner exception stack trace ---
   at System.Net.HttpWebRequest.GetRequestStream(TransportContext& context)
   at System.Net.HttpWebRequest.GetRequestStream()
   at Microsoft.Exchange.WebServices.Data.ServiceRequestBase.Emit(HttpWebRequest& request)
   at Microsoft.Exchange.WebServices.Data.ServiceRequestBase.ValidateAndEmitRequest(HttpWebRequest& request)
   --- End of inner exception stack trace ---
   at Microsoft.Exchange.WebServices.Data.ServiceRequestBase.ValidateAndEmitRequest(HttpWebRequest& request)
   at Microsoft.Exchange.WebServices.Data.SimpleServiceRequestBase.InternalExecute()
   at Microsoft.Exchange.WebServices.Data.MultiResponseServiceRequest`1.Execute()
   at Microsoft.Exchange.WebServices.Data.ExchangeService.BindToFolder(FolderId folderId, PropertySet propertySet)
   at Microsoft.Exchange.WebServices.Data.ExchangeService.BindToFolder[TFolder](FolderId folderId, PropertySet propertySet)
   at Microsoft.Exchange.WebServices.Data.Folder.Bind(ExchangeService service, WellKnownFolderName name)
   at Symantec.Submission.Exchange.Client.ExchangeFolder.Bind()

 See the following article about SESC debug logging: How to Obtain Debug logs for Symantec Email Submission Client (SESC).

 

Cause

A socket connection cannot be opened to the server configured in the CAS URL.

Resolution

Check the name or IP address configured in the CAS URL.  Check a firewall is not blocking ports from the SESC server to the CAS server. Check that the URL is accessible outside of the SESC product: How to test the CAS URL configured in Symantec Email Submission Client (SESC).

Technical Information

The CAS URL is configured in the SESC console.

1. Open the SESC console.
2. Open the Exchange Servers pane.
3. The textbox CAS URL contains the URL used by SESC.

 


Applies To

  • SESC 1.X