Wsus Sync Failed. WebException: The underlying connection was closed: An unexpected error occurred on a send. --- System.IO.IOException: Received an unexpected EOF or 0 bytes from the transport stream.

Hi I have installed wsus 3 sp2 on a win 2008 R2 Sp1
before the installation , I have updated the windows
I can open easily browse internet , but when I try to configure synchronization .but it fails.
No firewall , no proxy ............. I am behind a nat.
Wsus version is 3.2.7600.256.
I have searched and searched .....
Can any body help me
WebException: The underlying connection was closed: An unexpected error occurred on a send. ---> System.IO.IOException: Received an unexpected EOF or 0 bytes from the transport stream.
at System.Web.Services.Protocols.WebClientProtocol.GetWebResponse(WebRequest request)
   at System.Web.Services.Protocols.HttpWebClientProtocol.GetWebResponse(WebRequest request)
   at Microsoft.UpdateServices.ServerSync.ServerSyncCompressionProxy.GetWebResponse(WebRequest webRequest)
   at System.Web.Services.Protocols.SoapHttpClientProtocol.Invoke(String methodName, Object[] parameters)
   at Microsoft.UpdateServices.ServerSyncWebServices.ServerSync.ServerSyncProxy.GetAuthConfig()
   at Microsoft.UpdateServices.ServerSync.ServerSyncLib.InternetGetServerAuthConfig(ServerSyncProxy proxy, WebServiceCommunicationHelper webServiceHelper)
   at Microsoft.UpdateServices.ServerSync.ServerSyncLib.Authenticate(AuthorizationManager authorizationManager, Boolean checkExpiration, ServerSyncProxy proxy, Cookie cookie, WebServiceCommunicationHelper webServiceHelper)
   at Microsoft.UpdateServices.ServerSync.CatalogSyncAgentCore.SyncConfigUpdatesFromUSS()
   at Microsoft.UpdateServices.Serve

Hi
yes . it is alloweded.
Nat rule permits any ip traffic . No problem with https...
also my windows is fully updated.
here is my netstat -an , maybe usefull.
TCP    0.0.0.0:135            0.0.0.0:0              LISTENING
TCP    0.0.0.0:445            0.0.0.0:0              LISTENING
TCP    0.0.0.0:8530           0.0.0.0:0              LISTENING
TCP    0.0.0.0:8531           0.0.0.0:0              LISTENING
TCP    0.0.0.0:47001          0.0.0.0:0              LISTENING
TCP    0.0.0.0:49152          0.0.0.0:0              LISTENING
TCP    0.0.0.0:49153          0.0.0.0:0              LISTENING
TCP    0.0.0.0:49154          0.0.0.0:0              LISTENING
TCP    0.0.0.0:49155          0.0.0.0:0              LISTENING
TCP    0.0.0.0:49156          0.0.0.0:0              LISTENING
TCP    --------------------:139       0.0.0.0:0              LISTENING
TCP    --------------------:8530      172.16.2.201:53317     ESTABLISHED
TCP    --------------------:49362     23.65.244.185:443      ESTABLISHED
TCP    --------------------:49363     23.65.244.185:443      ESTABLISHED
TCP    --------------------:49367     23.65.244.185:443      ESTABLISHED
TCP    --------------------:49377     23.65.244.185:443      ESTABLISHED
TCP    --------------------:49414     131.253.34.141:443     ESTABLISHED
TCP    --------------------:49416     216.239.32.20:80       ESTABLISHED
TCP    --------------------:49417     216.239.32.20:80       ESTABLISHED
TCP    --------------------:49418     173.194.70.113:80      ESTABLISHED
TCP    --------------------:49419     173.194.70.113:80      ESTABLISHED
TCP    --------------------:49420     65.52.103.78:80        ESTABLISHED
TCP    --------------------:49421     65.52.103.78:80        ESTABLISHED
TCP    --------------------:49424     88.221.93.31:80        ESTABLISHED
TCP    --------------------:49425     88.221.93.30:80        ESTABLISHED
TCP    --------------------:49426     88.221.93.30:80        ESTABLISHED
TCP    --------------------:49427     88.221.93.31:80        ESTABLISHED
TCP    --------------------:49428     88.221.93.31:80        ESTABLISHED
TCP    --------------------:49429     88.221.93.31:80        ESTABLISHED
TCP    --------------------:49430     88.221.93.30:80        ESTABLISHED
TCP    --------------------:49431     88.221.93.30:80        ESTABLISHED
TCP    --------------------:49432     88.221.93.31:80        ESTABLISHED
TCP    --------------------:49433     88.221.93.31:80        ESTABLISHED
TCP    --------------------:49434     88.221.93.30:80        ESTABLISHED
TCP    --------------------:49435     88.221.93.31:80        ESTABLISHED
TCP    --------------------:49436     88.221.93.30:80        ESTABLISHED
TCP    --------------------:49437     88.221.93.30:80        ESTABLISHED
TCP    --------------------:49438     88.221.93.30:80        ESTABLISHED
TCP    --------------------:49439     88.221.93.30:80        ESTABLISHED
TCP    --------------------:49440     88.221.93.31:80        ESTABLISHED
TCP    --------------------:49441     88.221.93.30:80        ESTABLISHED
TCP    --------------------:49442     88.221.93.30:80        ESTABLISHED
TCP    --------------------:49443     88.221.93.54:80        ESTABLISHED
TCP    --------------------:49444     88.221.93.54:80        ESTABLISHED
TCP    --------------------:49445     88.221.93.63:80        ESTABLISHED
TCP    --------------------:49446     88.221.93.63:80        ESTABLISHED
TCP    --------------------:49447     88.221.93.63:80        ESTABLISHED
TCP    --------------------:49448     88.221.93.63:80        ESTABLISHED
TCP    --------------------:49449     88.221.93.63:80        ESTABLISHED
TCP    --------------------:49450     88.221.93.31:80        ESTABLISHED
TCP    --------------------:49451     88.221.93.31:80        ESTABLISHED
TCP    --------------------:49453     88.221.93.30:80        ESTABLISHED
TCP    --------------------:49456     65.55.58.184:80        ESTABLISHED
TCP    --------------------:49457     65.55.58.184:80        ESTABLISHED
TCP    --------------------:49460     131.253.34.142:80      ESTABLISHED
TCP    --------------------:49461     131.253.34.142:80      ESTABLISHED
TCP    --------------------:49462     65.52.103.78:80        ESTABLISHED
TCP    --------------------:49463     65.52.103.78:80        ESTABLISHED
TCP    --------------------:49464     63.251.85.33:80        ESTABLISHED
TCP    --------------------:49466     131.253.40.50:80       ESTABLISHED
TCP    --------------------:49467     131.253.40.50:80       ESTABLISHED

Similar Messages

WSUS Sync is not working Sync failed: UssCommunicationError: WebException: The underlying connection was closed: Could not establish trust relationship for the SSL/TLS secure channel. --- System.Security.Authentication.AuthenticationException: The remote

I know there are loads of posts with same issue and most of them were related to proxy and connectivity .
This was case for me as well (few months back). Now the same error is back. But I've confirmed that FW ports and proxy are fine this time around.
server is configured on http port 80
ERROR
Sync failed: UssCommunicationError: WebException: The underlying connection was closed: Could not establish trust relationship for the SSL/TLS secure channel. ---> System.Security.Authentication.AuthenticationException: The remote certificate is invalid
according to the validation procedure.~~at System.Web.Services.Protocols.WebClientProtocol.GetWebResponse(WebRequest request). Source: Microsoft.SystemsManagementServer.SoftwareUpdatesManagement.WSyncAction.WSyncAction.SyncWSUS
I've checked proxy server connectivity. I'm able browse following site from WSUS server
http://catalog.update.microsoft.com/v7/site/Home.aspx?sku=wsus&version=3.2.7600.226&protocol=1.8
I did telnet proxy server on the particular port (8080) and that is also fine.
I've doubt on certificates, any idea which are the certificates which we need to look? And if certificate is expired then (my guess) we won't be able open the above mentioned windows update catalog site?
Any tips appreciated !
Anoop C Nair (My Blog www.AnoopCNair.com)
- Twitter @anoopmannur -
FaceBook Forum For SCCM

Hi Lawrence ! - Many thanks for looking into this thread and replying. Appreciate your help.
Your reply ("SSL is enabled/configured, and the certificate being used is invalid
(or the cert does not exist or cannot be obtained), or the SSL connection could not be established.") is very helpful.
I've already tested CONTENT DOWNLOAD and it's working fine. WSUS Sync was also working fine for years with proxy server configured on port (8080) and WSUS server on port 80.
My Guess (this is my best guess ;)) is this something to do with Firewall or Proxy side configuration rather than WSUS. However, I'm not finding a way to prove this to proxy/firewall team. From their perspective all the required port communication open and
proxy server is also reachable. More over we're able to access internet (Microsoft Update Catalog site) over same port (8080).
Any other hints where I can prove them it's a sure shot problem from their side.
Thanks again !!
Anoop C Nair (My Blog www.AnoopCNair.com)
- Twitter @anoopmannur -
FaceBook Forum For SCCM

WSUS sync fails with "Webexception the underlying connection was closed. The connection was closed unexpectedly"

While I have my WSUS integrated with SCCM. I think this error has nothing to do with SCCM, so I put it here in the WSUS forum. On one of my networks, the nightly WSUS sync worked until two weeks ago. I've made no progress in fixing it. Ocassionally it'll
say the sync was successful (about 1 in 15 attempts). I keep getting "WebException: The underlying connection was closed. The connection was closed unexpectedly. at System.WebServices.Protocols.WebClientProtocol.GetWebResponse(WebRequest
request) at System.WebServices.Protocols.GetWebResponse(WebRequest request) at MicroSoft.UpdateServices.ServerSync.ServerSyncCompressionProxy.GetWebResponse(WebRequest webrequest) at System.Web.Services.Protocols.SoapHttpClientProtocol.(Invoke StringMethodName,Object[]
Parameters) at Microsoft.UpdateServices.ServerSync.ServerSyncWebServices.ServerSync.ServerSyncProxy.GetRevisionIdList(Cookie cookie, ServerSyncFilter filter) at Microsoft.Update.Services.ServerSync.CatalogSyncAgentCore.WebserviceGetRevisionIdList(ServerSyncFilter
filter, Boolean isConfigData), at Microsoft.UpdateServices.ServerSync.CatalogSyncAgentCore.SyncConfigUpdatesfromUSS() at Microsoft.UpdateServices.ServerSync.CatalogSyncAgentCore.ExecuteSyncProtocol(Boolean allowRedirect)"
Our enterprise has it's own WSUS server we have to sync from. The problem may be at that end, not mine. A sync will start and will fail about 4 minutes later. Our network guy watched the traffic leave our compound but saw only a trickle of traffic coming
back. Any ideas?
Ben JohnsonWY

Hi,
Please try this fix below first:
FIX: Intermittent "Underlying connection was closed" error message when you call a Web service from ASP.NET
http://support.microsoft.com/kb/819450
I guess you are maintaining a downstream server. If it isn’t a replica server, please try to sync with Microsoft update.
Hope this helps.

SSRS Reporting manages goes down frequently. ERROR: The underlying connection was closed: An unexpected error occurred on a send.

We have been experiencing issues with SSRS over the past 5 weeks, the service goes down frequently. And it comes up only on reboot of the server.
We had also disabled the On Access scan in Mcafee.
The service is in use for about two years, and the below error started occuring over the last few days. Please advise on this.
ui!ReportManager_0-2!24e8!08/14/2014-18:13:45:: e ERROR: The underlying connection was closed: An unexpected error occurred on a send.
ui!ReportManager_0-2!24e8!08/14/2014-18:13:45:: e ERROR: HTTP status code --> 500
-------Details--------
System.Net.WebException: The underlying connection was closed: An unexpected error occurred on a send. ---> System.IO.IOException: Unable to write data to 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.Send(Byte[] buffer, Int32 offset, Int32 size, SocketFlags socketFlags)
   at System.Net.Sockets.NetworkStream.Write(Byte[] buffer, Int32 offset, Int32 size)
   --- End of inner exception stack trace ---
   at System.Net.Sockets.NetworkStream.Write(Byte[] buffer, Int32 offset, Int32 size)
   at System.Net.PooledStream.Write(Byte[] buffer, Int32 offset, Int32 size)
   at System.Net.ConnectStream.WriteHeaders(Boolean async)
   --- End of inner exception stack trace ---
   at Microsoft.SqlServer.ReportingServices2005.RSConnection.GetSecureMethods()
   at Microsoft.ReportingServices.UI.Global.RSWebServiceWrapper.GetSecureMethods()
   at Microsoft.SqlServer.ReportingServices2005.RSConnection.IsSecureMethod(String methodname)
   at Microsoft.SqlServer.ReportingServices2005.RSConnection.ValidateConnection()
   at Microsoft.ReportingServices.UI.Global.SecureAllAPI()
   at Microsoft.ReportingServices.UI.ReportingPage.EnsureHttpsLevel(HttpsLevel level)
   at Microsoft.ReportingServices.UI.ReportingPage.ReportingPage_Init(Object sender, EventArgs args)
   at System.EventHandler.Invoke(Object sender, EventArgs e)
   at System.Web.UI.Control.OnInit(EventArgs e)
   at System.Web.UI.Page.OnInit(EventArgs e)
   at System.Web.UI.Control.InitRecursive(Control namingContainer)
   at System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint)
ui!ReportManager_0-2!24e8!08/14/2014-18:13:46:: e ERROR: Exception in ShowErrorPage: System.Threading.ThreadAbortException: Thread was being aborted.
   at System.Threading.Thread.AbortInternal()
   at System.Threading.Thread.Abort(Object stateInfo)
   at System.Web.HttpResponse.End()
   at System.Web.HttpServerUtility.Transfer(String path, Boolean preserveForm)
   at Microsoft.ReportingServices.UI.ReportingPage.ShowErrorPage(String errMsg) at    at System.Threading.Thread.AbortInternal()
   at System.Threading.Thread.Abort(Object stateInfo)
   at System.Web.HttpResponse.End()
   at System.Web.HttpServerUtility.Transfer(String path, Boolean preserveForm)
   at Microsoft.ReportingServices.UI.ReportingPage.ShowErrorPage(String errMsg)
library!ReportServer_0-1!1c90!08/14/2014-18:13:51:: Call to ListParentsAction(/Data Sources).
library!ReportServer_0-1!1c90!08/14/2014-18:13:51:: Call to ListParentsAction(/Data Sources).
library!ReportServer_0-1!1c90!08/14/2014-18:13:51:: Call to ListChildrenAction(/Data Sources, False).
webserver!ReportServer_0-1!1c90!08/14/2014-18:13:51:: i INFO: Processed folder '/Data Sources'
library!ReportServer_0-1!68c!08/14/2014-18:13:56:: Call to GetItemTypeAction(/).
library!ReportServer_0-1!68c!08/14/2014-18:13:56:: Call to ListParentsAction(/).
library!ReportServer_0-1!68c!08/14/2014-18:13:56:: Call to ListChildrenAction(/, False).
webserver!ReportServer_0-1!68c!08/14/2014-18:13:56:: i INFO: Processed folder '/'

Hi SThiyag,
Based on your error message, it may be related to the “SecureConnectionLevel” in the RSReportServer.config file. Please go to C:\Program Files\Microsoft SQL Server\MSRS11.MSSQLSERVER\Reporting Services\ReportServer, use Notepad to open the RSReportServer.config,
modify <Add Key="SecureConnectionLevel" Value="0"/>, change the value into "1" or "2".
(Note: Please backup the file before modify it.)
Acceptable values are:
3 Most secure—Use SSL for absolutely everything.
2 Secure—Use SSL for rendering and methods that pass credentials but don't insist on it for all SOAP calls.
1 Basic Security—Accepts http but rejects any calls that might be involved in the passing of credentials.
0 Least Secure—Don't use SSL at all
Here is a blog for error message "The underlying connection was closed...", please refer to the link below:
http://blogs.msdn.com/b/engelsr/archive/2005/11/29/the-underlying-connection-was-closed.aspx
If you have any question, please feel free to ask.
Best Regards,
Simon Hou

The underlying connection was closed

Support:
We've been experiencing the following two errors for the past two days. On the Azure Status page, there was reference to an issue affecting all services regarding connections but it has since been resolved. Are there additional issues with these
services or has something changed that we should be considering? Thanks in advance for your response.
Error 1:
Microsoft.WindowsAzure.StorageClient.StorageServerException: The server encountered an unknown failure: The underlying connection was closed: An unexpected error occurred on a send. ---> System.Net.WebException: The underlying connection was closed: An
unexpected error occurred on a send. ---> System.IO.IOException: Unable to write data to 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.NetworkStream.Write(Byte[] buffer, Int32 offset, Int32 size) --- End of inner exception stack trace
Error 2:
Exception:Microsoft.ServiceBus.Messaging.MessagingException: The underlying connection was closed: An unexpected error occurred on a send. ---> 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.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

Hi,
Thank you for reaching out to us.
I am currently researching to gather more information with regards to your request.
I shall revert back to you with an update at the earliest.
Sincerely appreciate your patience.
Regards,
Shirisha Paderu

Register-SPWorkflowService error: The underlying connection was closed

I have a three server workflow manager farm. I'm using hardware load balancing across the three servers. I've associated a hostname in DNS with the VIP on the NLB.
When I run Register-SPWorkflowService and point at the hostname for the -WorkflowHostUri parameter, I get the error:
Register-SPWorkflowService The underlying connection was closed An unexpected error occurred on a receive.
If I put that URL into a browser on the SP machine where I'm running this cmdlt, it responds with the correct XML. So I know that the NLB is routing regular http requests to my machines in the quorum.
Also, if I use the actual machine name of one of the three machines in the workflow manager quorum, the cmdlt works.
I know very little about NLB hardware. Is there something I need to tell the guys configuring the NLB to do so that the connection doesn't close?

Yes, I actually had done that before using a host file entry to replace the DNS mapping from the NLB VIP to the IP of one of the machines in the WFM quorum. It worked from the standpoint of registering and SharePoint shows that the farm is "connected". However,
when I go to create an SP 2013 workflow, it still only shows 2010 workflows in the dropdown (in SPD.)
I also put Fiddler on the SharePoint machine that I'm using to register the WFM quorum to SharePoint. It shows that when the register cmdlt is executed, several calls to the
/SharePoint/ web service endpoint are made, initially getting a 401 asking for an authentication, and then after creds are passed, getting a 200. But then a call to
/SharePoint/$Activities is called and a 401 occurs twice, after which the registration cmdlt fails.

Register-SPWorkflowService : The underlying connection was closed: An unexpected error occurred on a receive

My Fellow SharePoint 2013 Engineers,
For the past two days I have been struggling to setup the SharePoint 2013 Workflow Manager. After following the detailed steps provided by
Harbar.net when I reach the final step to register the workflow service for a site, I get the below error.
Below is the powershell command that I am running.
Register-SPWorkflowService -SPSite "http://service.domain.com" -Workflowhosturi "http://wfm.domain.com:12291" -AllowAuthHttp -force
Our SharePoint farm comprises of two WFE servers and two web application servers all of which are setup. You can see the configuration across our farm after I run the following commands
Import-Module WorkflowManager
Get-WFFarm
Get-WFFarmStatus
FarmType : Workflow
WFFarmDBConnectionString : Data Source=sp13-sql-01;Initial Catalog=WFManagementDB;Integrated Security=True;Encrypt=False
RunAsAccount : domain\svc_wfman
AdminGroup : BUILTIN\Administrators
Hosts : {Name: SP13-APP-01.domain.com, Configuration State: HostConfigurationCompleted, Name: SP13-APP-02.domain.com, Configuration State:
HostConfigurationCompleted, Name: SP13-WEB-01.domain.com, Configuration State: HostConfigurationCompleted, Name: SP13-WEB-02.domain.com,
Configuration State: HostConfigurationCompleted}
InstanceDBConnectionString : Data Source=sp13-sql-01;Initial Catalog=WFInstanceManagementDB;Integrated Security=True;Asynchronous Processing=True;Encrypt=False
ResourceDBConnectionString : Data Source=sp13-sql-01;Initial Catalog=WFResourceManagementDB;Integrated Security=True;Asynchronous Processing=True;Encrypt=False
HttpPort : 12291
HttpsPort : 12290
OutboundCertificate : Thumbprint: B40221F8511412CF8509DB8873815E793D3B6AC5, IsGenerated: True
Endpoints : {https://SP13-APP-01.domain.com:12290/, https://SP13-APP-02.domain.com:12290/, https://SP13-WEB-01.domain.com:12290/, https://SP13-WEB-02.domain.com:12290/}
SslCertificate : Thumbprint: D1F9BF5D83B5CC93D7639A84FEB29A3EC72EEE0F, IsGenerated: True
EncryptionCertificate : Thumbprint: D1F9BF5D83B5CC93D7639A84FEB29A3EC72EEE0F, IsGenerated: True
PS C:\> get-wffarmstatus
HostName Service
ServiceStatus
SP13-APP-01.domain.com WorkflowServiceBackend
Running
SP13-APP-01.domain.com WorkflowServiceFrontEnd
Running
SP13-APP-02.domain.com WorkflowServiceBackend
Running
SP13-APP-02.domain.com WorkflowServiceFrontEnd
Running
SP13-WEB-01.domain.com WorkflowServiceBackend
Running
SP13-WEB-01.domain.com WorkflowServiceFrontEnd
Running
SP13-WEB-02.domain.com WorkflowServiceBackend
Running
SP13-WEB-02.domain.com WorkflowServiceFrontEnd
Running
When I go Central Administration>Service Applications>Workflow Service Application Proxy, below is what I see
Thanks in advance for your help.
Daniel Christian (MCTS)

Since I didn't get any response back, I turned on all the loggin on our SharePoint environment and ran the powershell command again. I got the same error. I searched for the Client ActivityID on the log file and found the below. Can anyone shed some light
on it?
System.Net.WebException: The underlying connection was closed: An unexpected error occurred on a receive. ---> 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.NetworkStream.EndRead(IAsyncResult asyncResult)     --- End of inner exception stack trace ---
at System.Net.Sockets.NetworkStream.EndRead(IAsyncResult asyncResult)     at System.Net.Connection.ReadCallback(IAsyncResu... ce3bb4ef-40ff-4db8-b6a3-517fd5d1fbf5
11/22/2013 11:45:05.10* PowerShell.exe (0x0874)                 0x337C SharePoint Foundation         PowerShell
6tf2 High    ...lt asyncResult)     --- End of inner exception stack trace ---     at Microsoft.Workflow.Common.AsyncResult.End[TAsyncResult](IAsyncResult result)
at Microsoft.Workflow.Client.HttpGetResponseAsyncResult`1.End(IAsyncResult result)     at Microsoft.Workflow.Client.ClientHelpers.SendRequest[T](HttpWebRequest request, T content)     --- End of inner exception stack
trace ---     at Microsoft.Workflow.Client.ClientHelpers.SendRequest[T](HttpWebRequest request, T content)     at Microsoft.Workflow.Client.WorkflowManagementClient.SendRequest[T](HttpWebRequest request, T content)
at Microsoft.Workflow.Client.ScopeManager.Get()     at Microsoft.SharePoint.WorkflowServices.WorkflowServerPairingContext.RegisterFarm()     at Microsoft.SharePoint.WorkflowServices.PowerShell.RegisterSPWorkflowSe... ce3bb4ef-40ff-4db8-b6a3-517fd5d1fbf5
11/22/2013 11:45:05.10* PowerShell.exe (0x0874)                 0x337C SharePoint Foundation         PowerShell
6tf2 High    ...rvice.InternalProcessRecord()     at Microsoft.SharePoint.PowerShell.SPCmdlet.ProcessRecord() ce3bb4ef-40ff-4db8-b6a3-517fd5d1fbf5
Daniel Christian (MCTS)

[Exchange-Online] [EWSMA] [C#] [Windows]: EWS - CreateAttachment problem - The underlying connection was closed: An unexpected error occurred on a send

Hello,
I have a problem with
ExchangeServiceBinding.CreateAttachment(...) method (EWS with Office 365)
When I try to add a small attachment (e.g. 5 MB), then the method works fine.
When I try to add a big attachment (e.g.
12 MB), then the following exception is thrown:
System.Net.WebException
The underlying connection was closed: An unexpected error occurred on a send.
   at System.Web.Services.Protocols.WebClientProtocol.GetWebResponse(WebRequest request)
   at System.Web.Services.Protocols.HttpWebClientProtocol.GetWebResponse(WebRequest request)
   at System.Web.Services.Protocols.SoapHttpClientProtocol.Invoke(String methodName, Object[] parameters)
   at C2EWS.Proxy.ExchangeServiceBinding.CreateAttachment(CreateAttachmentType CreateAttachment1) in d:\source\EWSProxyClasses.cs:line 1471
   at EWSRequest.Program.UploadAttachment(ExchangeServiceBinding esb, ItemIdType parentItemIdType) in d:\source\EWSRequest\Program.cs:line 90
   at EWSRequest.Program.Main(String[] args) in d:\source\EWSRequest\Program.cs:line 59
Inner exception:
System.IO.IOException
Unable to write data to the transport connection: An existing connection was forcibly closed by the remote host.
    at System.Net.Sockets.NetworkStream.MultipleWrite(BufferOffsetSize[] buffers)
    at System.Net.Security._SslStream.StartWriting(SplitWritesState splitWrite, SplitWriteAsyncProtocolRequest asyncRequest)
    at System.Net.Security._SslStream.ProcessWrite(BufferOffsetSize[] buffers, SplitWriteAsyncProtocolRequest asyncRequest)
    at System.Net.TlsStream.MultipleWrite(BufferOffsetSize[] buffers)
    at System.Net.Connection.Write(ScatterGatherBuffers writeBuffer)
    at System.Net.ConnectStream.ResubmitWrite(ConnectStream oldStream, Boolean suppressWrite)
Inner exception:
  System.Net.Sockets.SocketException
  An existing connection was forcibly closed by the remote host
     at System.Net.Sockets.Socket.MultipleSend(BufferOffsetSize[] buffers, SocketFlags socketFlags)
     at System.Net.Sockets.NetworkStream.MultipleWrite(BufferOffsetSize[] buffers)
The C# code is the following:
private void UploadAttachment(ExchangeServiceBinding esb, ItemIdType parentItemIdType, string attachmentPath)
// File Attachment
FileAttachmentType fileAttach = new FileAttachmentType();
// Attachment details
byte[] bytes = System.IO.File.ReadAllBytes(attachmentPath);
fileAttach.Content = bytes;
fileAttach.IsInlineSpecified = false;
fileAttach.LastModifiedTimeSpecified = false;
fileAttach.Name = System.IO.Path.GetFileName(attachmentPath);
// Create Attachment
CreateAttachmentType reqCreateAttach = new CreateAttachmentType();
// Add parent Id
reqCreateAttach.ParentItemId = parentItemIdType;
// Add attachment to the query
reqCreateAttach.Attachments = new AttachmentType[1];
reqCreateAttach.Attachments[0] = fileAttach;
// Upload attachment
CreateAttachmentResponseType resp = esb.CreateAttachment(reqCreateAttach);
// Check response errors
CheckErrors(resp);
Could you advise a solution, please?
Robert

Hello,
The maximum size is rather not the problem in this case. As mentioned in my question above, I have a problem uploading messages with 12MB attachments to Office 365 via EWS. According
to the documentation you provided a link to, the message size limit in all plans of Office 365 is 25MB.
When we try the same request using slow network connection (1Mbit/s) there IS problem - we are NOT able to upload 12 MB attachments.
When we try the same request using faster network connection (10Mbit/s) there is NO problem - we are able to upload 12 MB attachments.
It seems like a kind of timeout - probably from Office365.
Is there a possibility to upload attachment in chunks?
Robert

Cannot upload report to report manager 2008R2 : The underlying connection was closed: An unexpected error occurred on a receive

Hi all,
I cannot upload a report to our report manager. The message returned in report manager is: The underlying connection was closed: An unexpected error occurred on a receive
I have checked the report server log file and found the below...
Any assistance greatly appreciated.
Thanks, Clay
-------Details--------
System.Net.WebException: The underlying connection was closed: An unexpected error occurred on a receive. ---> 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.NetworkStream.Read(Byte[] buffer, Int32 offset, Int32 size)
   --- End of inner exception stack trace ---
   at System.Net.Sockets.NetworkStream.Read(Byte[] buffer, Int32 offset, Int32 size)
   at System.Net.PooledStream.Read(Byte[] buffer, Int32 offset, Int32 size)
   at System.Net.Connection.SyncRead(HttpWebRequest request, Boolean userRetrievedStream, Boolean probeRead)
   --- End of inner exception stack trace ---
   at System.Web.Services.Protocols.WebClientProtocol.GetWebResponse(WebRequest request)
   at System.Web.Services.Protocols.HttpWebClientProtocol.GetWebResponse(WebRequest request)
   at Microsoft.ReportingServices.UI.Global.RSWebServiceWrapper.GetWebResponse(WebRequest request)
   at System.Web.Services.Protocols.SoapHttpClientProtocol.Invoke(String methodName, Object[] parameters)
   at Microsoft.SqlServer.ReportingServices2005.ReportingService2005.CreateReport(String Report, String Parent, Boolean Overwrite, Byte[] Definition, Property[] Properties)
   at Microsoft.SqlServer.ReportingServices2005.RSConnection.CreateReport(String Report, String Parent, Boolean Overwrite, Byte[] Definition, Property[] Properties)
   at Microsoft.ReportingServices.UI.ImportPageCtrl.ApplyChanges()
   at Microsoft.ReportingServices.UI.BaseApplyPage.ApplyBtn_Click(Object sender, EventArgs e)
   at Microsoft.ReportingServices.UI.ScriptButton.RaisePostBackEvent(String eventArgument)
   at System.Web.UI.Page.RaisePostBackEvent(IPostBackEventHandler sourceControl, String eventArgument)
   at System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint)

Hi clay,
Per my understanding that you got some error when you upload reports in the report manager, right?
I have checked the log and the issue can be caused by many factors.
It can be caused by the size of the report is too big which will sent the request in its entirety and got a TCP ACK-FIN or RST from server to close the connection, without a response from server when uploading the reports. We can follow these steps
to increase the request size to resolve the issue:
Add the following registry key with the following value:
Key: HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\HTTP\Parameters
Value: DWORD "MaxRequestBytes" set it to a value of 5242880 (5MB). (This number is alterable).
Stop the SRS Windows Service.
From a cmd prompt run "net stop http" then "net start http".
Try and upload your report.
Details information please reference to this similar thread:
http://stackoverflow.com/questions/2238494/cant-deploy-or-upload-large-ssrs-2008-report-from-vs-or-ie
If the above didn't help, please also check below information:
configure the rsreportserver.config file and make the SecureConnectionLevel value set to 0 to solve the problem. By default, the file is under the path:
C:\Program Files\Microsoft SQL Server\MSRS10_50.MSSQLSERVER\Reporting Services\ReportServer
You can refer to the code below:
< Add Key="SecureConnectionLevel" Value="0"/>
The SecureConnectionLevel property allows values of 0,1,2,3, with 0 indicating that Secure Socket Layer is not required for any of the Web service methods. And a positive integer indicates Secure Socket Layer is required for all the Web service methods.
If you still have any problem, please feel free to ask.
Regards
Vicky Liu
Vicky Liu
TechNet Community Support

The underlying connection was closed error FIM 2010

I have a fresh installation of FIM 2010 R2. After installation I am able to see FIM portal through account used for installation.
however in evenvwr I am continously getting below error. During instllation EXCHANGE team provided the address 'outlook.company.in' as the address and I selected
all option like SSL and pooling on installation screen.
Below error seems related with Exchagne but I am not able to undserstand what should I demand from exchange team.
Kindly suggest.
Error
System.Web.Services: System.Net.WebException: The underlying connection was closed: Could not establish trust relationship for the SSL/TLS secure channel. ---> System.Security.Authentication.AuthenticationException: The remote certificate is invalid according
to the validation procedure.
   at System.Net.Security.SslState.StartSendAuthResetSignal(ProtocolToken message, AsyncProtocolRequest asyncRequest, Exception exception)
   at System.Net.Security.SslState.ProcessReceivedBlob(Byte[] buffer, Int32 count, AsyncProtocolRequest asyncRequest)
   at System.Net.Security.SslState.StartReceiveBlob(Byte[] buffer, AsyncProtocolRequest asyncRequest)
   at System.Net.Security.SslState.ProcessReceivedBlob(Byte[] buffer, Int32 count, AsyncProtocolRequest asyncRequest)
   at System.Net.Security.SslState.StartReceiveBlob(Byte[] buffer, AsyncProtocolRequest asyncRequest)
   at System.Net.Security.SslState.ProcessReceivedBlob(Byte[] buffer, Int32 count, AsyncProtocolRequest asyncRequest)
   at System.Net.Security.SslState.StartReceiveBlob(Byte[] buffer, AsyncProtocolRequest asyncRequest)
   at System.Net.Security.SslState.ForceAuthentication(Boolean receiveFirst, Byte[] buffer, AsyncProtocolRequest asyncRequest)
   at System.Net.Security.SslState.ProcessAuthentication(LazyAsyncResult lazyResult)
   at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
   at System.Net.TlsStream.ProcessAuthentication(LazyAsyncResult result)
   at System.Net.TlsStream.Write(Byte[] buffer, Int32 offset, Int32 size)
   at System.Net.PooledStream.Write(Byte[] buffer, Int32 offset, Int32 size)
   at System.Net.ConnectStream.WriteHeaders(Boolean async)
   --- End of inner exception stack trace ---
   at System.Web.Services.Protocols.WebClientProtocol.GetWebResponse(WebRequest request)
   at System.Web.Services.Protocols.HttpWebClientProtocol.GetWebResponse(WebRequest request)
   at System.Web.Services.Protocols.SoapHttpClientProtocol.Invoke(String methodName, Object[] parameters)
   at Microsoft.ResourceManagement.WebServices.Mail.Exchange.ExchangeServiceBinding.FindItem(FindItemType FindItem1)
   at Microsoft.ResourceManagement.WebServices.Mail.Exchange.MailChannel.ExchangeMailChannelListener`1.ExchangeMailListener.<OnPollTimerExpired>b__0(Boolean findUnreadItems)
   at Microsoft.ResourceManagement.WebServices.Mail.Exchange.MailChannel.ExchangeMailChannelListener`1.ExchangeMailListener.OnPollTimerExpired(Object state)
Thanks,
Mann

Hello,
You have to connect to the EWS (Exchange Web service: https://mailserver/ews/exchange.asmx) with the FIMService account to get the certificate of EWS.
http://technet.microsoft.com/en-us/library/ff512686%28v=ws.10%29.aspx
Regards,
Sylvain

The underlying connection was closed: An unexpected error occurred on a receive..Exception.Message - while executing powershell command for sharepoint online site

" +The underlying connection was closed: An unexpected error occurred on a receive..Exception.Message " OR sometimes
"The remote server returned an error: (503) Server Unavailable..Exception.Message"
Getting exception above when performing various operation (site coll creating, group creation, adding users to group) for sharepoint online (Office 365) site using powershell script.
I want to create 3500 site collections using PS script. In-between getting above exception so it will skip one site collection creating and working again. for eg. after creating 11 site coll, script will through above exception and so 12th site coll will
not be create but working fine from 13 and so on...

Remote server seems working to me...any additional check?
if problem with remote server then may be loop to create site provisioning should not start again..Right?
any idea?

OLAP Error:The underlying connection was closed: An unexpected error occure

We have recently installed BPC 51 (SP2). This been working fine for months until yesterday. Now we are getting errors on OLAP Database. Following is the problem description. Any help would be appreciated.
Received error "The underlying connection was closed: An unexpected error occurred on a send." while processing dimension. This message appears during 'Create Dimension' sub step( step 2/5). After this BPC server crashes.
The same error appears while deleting appset during 'Delete OLAP Database' sub step (step 2/4). We are also not able to restore an appset since the process hangs during OLAP Database stage.
Software version: BPC Version 5.0.102 SP2
MS SQL Server 2005
Microsoft SQL Server Management Studio      9.00.3042.00
Microsoft Analysis Services Client Tools      2005.090.3042.00
Microsoft Data Access Components (MDAC)      2000.086.3959.00 (srv03_sp2_rtm.070216-1710)
Microsoft MSXML      2.6 3.0 4.0 5.0 6.0
Microsoft Internet Explorer      6.0.3790.3959
Microsoft .NET Framework      2.0.50727.1433
Operating System      5.2.3790
Thanks

Yes we did that several time, but did not solve the problem.
Finally, we processed all the dimensions, applications, appsets within SQL server studio and the problem is resolved. I am not sure if this would surface again.
Thanks
Edited by: Sankaranarayanan Janakiraman on Jun 19, 2008 8:34 AM

SSRS Report Server Could not establish connection. The underlying connection was closed. Could not establish trust relationship for the SSL/TLS Secure channel

Hi
Had to un-install and then re-install MS SQL Server 2012 with SSRS.
After we re-installed we are able to get to the Web Services page but not the Report Server page and get the above error message. We need to use SSL and when we bind the cert in RS Configuration Manager it says it does this successfully on the WebServices
tab. We also do a similar exercise on the ReportServer page.
Any help warmly welcomed :D
Thanks

Hi Rich Whight,
According to your description, after you re-installed SQL Server 2012 with SSRS, you are able to access Web Service URL, but when you tried to access Report Manager URL, the error occurred: The underlying connection was closed. Could not establish trust
relationship for the SSL/TLS Secure channel.
The issue may be caused when the certificate isn't installed correctly in the trusted root for the local computer. To verify and install the certificate, Please refer to the steps blow:
In RsReportServer.config file(default location: C:\Program Files\Microsoft SQL Server\MSRS11.MSSQLSERVER\Reporting Services\ReportServer), change the “SecureConnectionLevel” element value from 0 to 3.
Add correct value to <UrlRoot> element.
Add the same value to the <ReportServerUrl> element as step2.
Go to Microsoft management Console, add the certificate which you use to access the report server under “Trusted Root Certification Authorities”.
For more information about SSL configuration and Managing Trusted Root Certificates, please refer to the following documents:
http://blogs.msdn.com/b/mariae/archive/2007/12/12/ssl-configuration-and-reporting-services.aspx
http://technet.microsoft.com/en-us/library/cc754841.aspx
If you have any more questions, please feel free to ask.
Best Regards,
Wendy Fu

Unexpected Error: The underlying connection was closed

Hi All,
I have a requirement to send SMS to user after submitting a form. I have created a visual web part and it is working fine in my test environment. When the same webpart is deployed to production, i am getting an error like "Unknown SMS Error:Unexpect 0000 Unexpected The
underlying connection was closed: An unexpected error occurred on a receive.f56b16e8-7b46-4b62-a234-1c65ee7bc9b7". my code is below
Code:
try
HttpWebRequest myReq = (HttpWebRequest)WebRequest.Create(_cmpURL);
myReq.KeepAlive = true;
myReq.ReadWriteTimeout= 10000000;
HttpWebResponse myResp = (HttpWebResponse)myReq.GetResponse();
System.IO.StreamReader respStreamReader = new System.IO.StreamReader(myResp.GetResponseStream());
string responseString = respStreamReader.ReadToEnd();
respStreamReader.Close();
myResp.Close();
catch (Exception ex)
Can some one please help me, how to get rid of above error.
MercuryMan

Hi MercuryMan,
Whether you have checked your environments as my first reply. If not, please check it, and let me know the result.
In addition, please check if the links are useful for you:
http://blogs.msdn.com/b/jpsanders/archive/2009/01/07/you-receive-one-or-more-error-messages-when-you-try-to-make-an-http-request-in-an-application-that-is-built-on-the-net-framework-2-0.aspx
http://stackoverflow.com/questions/2862817/an-existing-connection-was-forcibly-closed-by-the-remote-host
Best Regards,
Wendy
Forum Support
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact
[email protected]
Wendy Li
TechNet Community Support

Getting "The underlying connection was closed: An unexpected error occurred on a receive." in Azure Web Jobs

I have created one web job - on demand schedule under azure web site. This web jobs contains .execmd(i.e.)
Console Application.
I am retrieving the data from SQL Azure database and uploaded the data in sharepoint online lists. (i.e.)I have uploaded the data to several(7) lists in each subsites. I have 3 subsites.
I am getting this error "The underlying connection was closed: An unexpected error occurred on a receive.", while uploaded the data into lists.
Full Error Message:
Message - The underlying connection was closed: An unexpected error occurred on a receive.
StackTrace - at System.Net.HttpWebRequest.GetResponse()
> cc525c: INFO] at Microsoft.SharePoint.Client.SPWebRequestExecutor.Execute()
> cc525c: INFO] at Microsoft.SharePoint.Client.ClientRequest.ExecuteQueryToServer(ChunkStringBuilder sb)
> cc525c: INFO] at Microsoft.SharePoint.Client.ClientRequest.ExecuteQuery()
> cc525c: INFO] at Microsoft.SharePoint.Client.ClientRuntimeContext.ExecuteQuery()
> cc525c: INFO] at Microsoft.SharePoint.Client.ClientContext.ExecuteQuery()
This is not occur every time. Some time i didn't get any error data successfully uploaded in share point online list.
Totally 4 hours taken uploaded the data into list for completed all 3 subsites.
If anyone know how to resolve this.
Thanks,
A.Ramu

I have created one web job - on demand schedule under azure web site. This web jobs contains
.exe cmd(i.e.) Console Application.
I am retrieving the data from SQL Azure database and uploaded the data in sharepoint online lists. (i.e.)I have uploaded the data to several(7) lists in each subsites. I have 3 subsites.
I am getting this error "The remote server returned an error: (503) Server Unavailable", while uploaded the data into lists.
Full Error Message:
Message - The remote server returned an error: (503) Server Unavailable.
StackTrace - at System.Net.HttpWebRequest.GetResponse()
> cc525c: INFO] at Microsoft.SharePoint.Client.SPWebRequestExecutor.Execute()
> cc525c: INFO] at Microsoft.SharePoint.Client.ClientRequest.ExecuteQueryToServer(ChunkStringBuilder sb)
> cc525c: INFO] at Microsoft.SharePoint.Client.ClientRequest.ExecuteQuery()
> cc525c: INFO] at Microsoft.SharePoint.Client.ClientRuntimeContext.ExecuteQuery()
> cc525c: INFO] at Microsoft.SharePoint.Client.ClientContext.ExecuteQuery()
This is not occur every time. Some time i didn't get any error data successfully uploaded in share point online list.
Totally 4 hours taken uploaded the data into list for completed all 3 subsites.
If anyone know how to resolve this.
Thanks,
A.Ramu

Wsus Sync Failed. WebException: The underlying connection was closed: An unexpected error occurred on a send. --- System.IO.IOException: Received an unexpected EOF or 0 bytes from the transport stream.

Similar Messages

Maybe you are looking for