ITunes can't sync. "sendMuxSegment connection was closed"

My iPad 2 can't seem to sync.
I've rebooted the Mac and the iPad several times.
I've check the computer with Disk First Aid and all checks out fine.
I thought it might have something to do with the iPad not being on the latest iOS, so I upgraded to 6.1.3, but iTunes continues to behave the same way.
It is able to get through the backup, and didn't have any issues with teh upgrade to 6.1.3, but as soon as it starts the last step of syncing, it finishes. When I checked the Console application it said:
2013-03-27 8:03:07.632 PM com.apple.usbmuxd[67]: MuxTCPInputSCE received RST for 0x7-[REDACTED]@0xfd130000:49353->0x10020d6a0-MDCrashReportTool/NULL:41729: sendMuxSegment connection was closed
I have the latest XCode installed and am doing ad hoc distribution to my iPad 2. (Not sure if it's relevant.) When I launched XCode after update it started pulling "symbols" from the iPad. Then it, too, threw the same error.
2013-03-27 8:19:28.149 PM com.apple.usbmuxd[67]: MuxTCPInputSCE received RST for 0x7-[REDACTED]@0xfd130000:49543->0x100502850-Xcode/com.apple.dt.Xcode:12034: sendMuxSegment connection was closed
Neither iTunes or XCode created any alerts about the error. Both fail completely silently except for the notation in the Console.
Any help would be great!
Thanks,
Colin
iTunes 11.0.2
Mac OS X 10.8.3
XCode 4.6.1
iPad 2 6.3.1

Resolved.
A few months ago, I enabled some restrictions on the iPad to prevent my son (4) from getting constant requests for in-app purchases, including restricting installing or deleting apps. I assumed this would be limited to someone interacting directly with the iPad, not extend to an iTunes sync session.
Really, Apple? You couldn't spare a little warning: "Please enable app installation on the iPad and re-sync."

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

  • Since I'd installed the new version of iTunes, iCal and Address book do not sync with my iPhone 3GS through iTunes anymore and I get an error message stating that iTunes can not sync with this iPhone. Was must i do to correct this issue?

    Since I'd installed the new version of iTunes, iCal and Address book do not sync with my iPhone 3GS through iTunes anymore and I get an error message stating that iTunes can not sync with this iPhone. Was must i do to correct this issue and if i must, how dI reintall iTunes without loosing my content?
    P.S. I am able to sync postcasts and music though!

    http://support.apple.com/kb/TS3694
    http://support.apple.com/kb/TS3125
    http://support.microsoft.com/kb/299357

  • I can't connect to the iTunes Store because the network connection was refused.

    I can't connect to the iTunes Store because the network connection was refused. I'm using a laptop with Windows 7 Ultimate.

    Hi ChanTwo,
    Welcome to the Support Communities!  The article below will help you troubleshoot the issue you are having with the connection issue you are having with the iTunes Store:
    Can't connect to the iTunes Store
    http://support.apple.com/kb/TS1368
    iTunes: Advanced iTunes Store troubleshooting
    http://support.apple.com/kb/TS3297
    I hope this information helps ....
    - Judy

  • 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

  • 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.

  • Can't connect to iTunes Store. "The network connection was refused"

    Since I updated to the newest version of iTunes I have had this error message:
    "iTunes could not connect to the iTunes Store. The network connection was refused. Make sure your network settings are correct and your network correction is active, then try again."
    Is this most likely a problem with the functioning of my Norton Internet Security 2007 with the new iTunes software?

    Here is the Diagnostic information, in case this helps anyone understand me better. I genuinely appreciate any feedback or suggestions.
    Microsoft Windows XP Professional Service Pack 2
    iTunes 7.0.1.8
    Network Connection Information
    Active Connection: LAN Connection
    Connected: Yes
    Online: Yes
    Using Modem: No
    Using LAN: Yes
    Using Proxy: No
    SSL 3.0 Support: Enabled
    TLS 1.0 Support: Enabled
    Firewall Information
    Windows Firewall is on.
    iTunes is enabled in Windows Firewall.
    Connection attempt to Apple web site was unsuccessful.
    The network connection was refused.
    Connection attempt to iTunes Store was unsuccessful.
    The network connection was refused.
    Secure connection attempt to iTunes Store was unsuccessful.
    The network connection was refused.

  • My macbook pro's iTunes can't sync with my iPad1

    Hi there,
    My MacBook Pro's iTunes can't sync with my iPad1. They are connected by cable and the Macbook and the ipad can find each other by wifi but that's it. The software seems to be upto date on both but im not sure as i can't find the itunes app symbol in the settings area of the ipad but it has itunes. I hope that helps.
    Cheers folks,
    R

    It is not of any help but have exactly the same issue. Called one of our local radio Tech Shows (The Tech Guy, with Leo Leporte) and for what it is worth his only answer was that it was a bug. He noted that apparently i-Tunes was not looking at i-Photo for the library location but rather, as you have noted, only looks in the default location.
    Be interested if you get this solved or come up with another work around that does not require my library to be in the default directory.
    As you noted i-Photo is happy it is just the sync with i-Tunes, it just doesn't work,
    Chuck Queen

  • ITunes Store Error Message: "network connection was reset"

    I've been having trouble connecting to the iTunes Store since Dec. 25, 2006. The last time I was able to connect to the site was Jan. 2, 2007!
    The error message that I have been receiving is: "iTunes could not connect to the iTunes Store. The network connection was reset."
    Here are the troubleshooting issues that I have already performed.
    1) Ensured that my internet connection was active.
    2) Checked to make sure Windows XP Service Pack Updates were compatible. No problems with the firewall detected.
    3) Have the latest version (7.02.16) of iTunes.
    4) iPod software is up to date.
    5) Ran iTunes diagnostics which states:
    Windows Firewall is on.
    iTunes is enabled in Windows Firewall.
    Connection attempt to Apple web site was unsuccessful.
    The network connection was reset.
    Connection attempt to iTunes Store was unsuccessful.
    The network connection was reset.
    Secure connection attempt to iTunes Store was successful.
    Does anyone have this problem? Can anyone recommend a solution that worked for them?
    Sony   Windows XP  

    PS: I also went into Internet Explorer...
    Selected Tools, selected Internet options, then selected Advanced Tab
    Then I looked for the security section and made sure that SSL 2.0 was selected.
    I was still unable to access iTunes Store.

  • SQL Service Broker 2012: the connection was closed by the remote end, or an error occurred while receiving data: '64(The specified network name is no longer available.)'

    Anyone can help with the below issue please? Much appreciated.
    We have about 2k+ messages in sys.transmission_queue
    Telnet to the ports 4022 is working fine.
    Network connectivity has been ruled out.
    The firewalls are OFF.
    We also explicitly provided the permissions to the service account on Server A and Server B to the Service broker end points.
    GRANT
    CONNECT ON
    ENDPOINT <broker> <domain\serviceaccount>
    Currently for troubleshooting purposes, the DR node is also out of the Availability Group, which means that we right now have only one replica the server is now a traditional cluster.
    Important thing to note is when a SQL Server service is restarted, all the messages in the sys.transmission queue is cleared immediately. After about 30-40 minutes, the errors are continued to be seen with the below
    The
    connection was
    closed by the
    remote end,
    or an
    error occurred while
    receiving data:
    '64(The specified network name is no longer available.)'

    We were able to narrow down the issue to an irrelevant IP coming into play during the data transfer. We tried ssbdiagnose runtime and found this error:
    Microsoft Windows [Version 6.1.7601]
    Copyright (c) 2009 Microsoft Corporation.  All rights reserved.
    C:\Windows\system32>SSBDIAGNOSE -E RUNTIME -ID 54F03D35-1A94-48D2-8144-5A9D24B24520 Connect to -S <SourceServer> -d <SourceDB> Connect To -S <DestinationServer> -d <DestinationDB>
    Microsoft SQL Server 11.0.2100.60
    Service Broker Diagnostic Utility
    An internal exception occurred: Timeout expired.  The timeout period elapsed prior to completion of the operation or the server is not responding.
    P  29830                                 Could not find the connection to the SQL Server that
    corresponds to the routing address tcp://XX.XXX.XXX.199:4022. Ensure the tool is connected to this server to allow investigation of runtime events
    The IP that corresponds to routing address is no where configured within the SSB. We are yet unsure why this IP is being referred despite not being configured anywhere. We identified that this IP belongs to one of nodes other SQL Server cluster, which has
    no direct relation to the source server. We failed over that irrelevant SQL Server cluster and made another node active and to our surprise, the data from sys.transmission_queue started flowing. Even today we are able to reproduce the issue, if we bring
    back this node [XX.XXX.XXX.199] as active. Since, its a high business activity period, we are not investigating further until we get an approved downtime to find the root cause of it.
    When we get a approved downtime, we will bring the node [XX.XXX.XXX.199] as active and we will be running Network Monitor, Process Monitor and the SSB Diagnose all in parallel to capture the process/program that is accessing the irrelevant IP.
    Once, we are able to nail down the root cause, I will share more information.

  • 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

  • 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)

  • 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

  • URGENT - The underlying connection was closed: An unexpected error occurred on a send

    Hello,
    We have a web app that works with Ping Federate SSO. The code that was working fine suddenly stopped working with this error message.
    Code: httpResponse = (HttpWebResponse)httpRequest.GetResponse()
    Error: The underlying connection was closed: An unexpected error occurred on a send
    We have tried everything to try to make it work. Made sure TLS is enabled, review the logs from both sides. Nothing seemed to work. I read on the net that there appears to be some known bug with the .net framework. 
    This is our prodcution code and our customers are currently impacted by this issue and we need to get the SSO working again.
    I'd appreciate if you can email me how we can go about resolving this issue. BTW, I also made sure have the correct certificate through IIS bind.
    regards, 
    Ilanko
    [email protected]
    206.931.9442

    Hello Ilanko,
    It seems that you could access the application source code, if so, I suggest that you could check this
    blog to debug the GetResponse() method to find the exact caused code line.
    For this exception, here I find some related information which might be helpful:
    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 1.1 Service Pack 1
    A blog which contains a summary for this exception and provides various workarounds:
    http://blogs.msdn.com/b/engelsr/archive/2005/11/29/the-underlying-connection-was-closed.aspx
    If your application is calling a web service, you could check this hotfix to see if your environment are met:
    https://support.microsoft.com/kb/819450
    If not, you could post a hotfix request with your environment description to:
    https://support2.microsoft.com/contactus/emailcontact.aspx?scid=sw;%5BLN%5D;1422
    Regards.
    We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
    Click
    HERE to participate the survey.

  • The underlying connection was closed: An unexpected error occurred on a receive

    Hi,
    We have a requirement where we need to create a custom workflow code activity which will download the current uploaded document to a shared network drive. We have created a code activity using client object model  to achieve this. But intermittently
    below exception is being occured at ctx.ExecuteQuery();
    Can anyone help me in resolving the issue?
    Exception :
    :-The underlying connection was closed: An unexpected error occurred on a receive.The underlying connection was closed: An unexpected error occurred on a receive.   at System.Net.HttpWebRequest.GetResponse()
       at Microsoft.SharePoint.Client.SPWebRequestExecutor.Execute()
       at Microsoft.SharePoint.Client.ClientRequest.ExecuteQueryToServer(ChunkStringBuilder sb)
       at CustomActivity.CustomCodeActivity.Execute(CodeActivityContext context)
    The underlying connection was closed: An unexpected error occurred on a receive.The underlying connection was closed: An unexpected error occurred on a receive.   at System.Net.HttpWebRequest.GetResponse()
       at Microsoft.SharePoint.Client.SPWebRequestExecutor.Execute()
       at Microsoft.SharePoint.Client.ClientContext.GetFormDigestInfoPrivate()
       at Microsoft.SharePoint.Client.ClientContext.EnsureFormDigest()
       at Microsoft.SharePoint.Client.ClientContext.ExecuteQuery()
       at CustomActivity.CustomCodeActivity.Execute(CodeActivityContext context)
    Below is the code written.
    using (ClientContext ctx = new ClientContext(strSiteUrl))
    // ctx.ExecutingWebRequest += clientContext_ExecutingWebRequest;
    LogMessage("In Using");
    ctx.FormDigestHandlingEnabled = true;
    Web web = ctx.Web;
    LogMessage("In Using1");
    ctx.Load(web);
    LogMessage("In Using2");
    ctx.FormDigestHandlingEnabled = true; //Issue occurring while executing below line
    ctx.ExecuteQuery();
    LogMessage("Exceute Query 1");
    //foreach (ListItem item in GetAllListItems(web.Url, strListName,strItemId))
    ListItem item = GetAllListItems(web.Url, strListName, strItemId);
    LogMessage("in loop1"+item.DisplayName);
    foreach (Microsoft.SharePoint.Client.File file in GetListItemAttachments(web.Url, item, strListName))
    LogMessage("in loop2");
    SaveAttachmentToDisk(file, strFilePath, web.Url);
    string fileExt = System.IO.Path.GetExtension(file.Name);
    string newName = file.Name.Substring(0, file.Name.IndexOf('.'));
    newName = newName + "-" + curDate;

    Hi,
    According to the error message, it usually occurs when server or network device unexpectedly closes an existing Transmission Control Protocol connection.
    This problem may occur when time-out value on the server or network is set too low.
    To resolve this issue, I suggest you do as the followings:
    1. Configure the Web site that hosts the Web services not to use keep-alive connections.
    2. Override the HttpWebRequest method in the Reference.cs file that is generated by Microsoft Visual Studio .NET for the Web client proxy.
    protected override WebRequest GetWebRequest(Uri uri)
    HttpWebRequest webRequest = (HttpWebRequest) base.GetWebRequest(uri);
    webRequest.KeepAlive = false;
    return webRequest;
    More Reference:
    http://support.microsoft.com/kb/819450
    http://stackoverflow.com/questions/21728773/the-underlying-connection-was-closed-an-unexpected-error-occurred-on-a-receiv
    Best regards,
    Zhengyu Guo
    TechNet Community 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 Support, contact
    [email protected]
    Zhengyu Guo
    TechNet Community Support

Maybe you are looking for