Io exception: socket was closed ????? Error 17002

Hi I am getting the following exception when connecting to Oracle 9i through JDBC...The code uses connection pooling initialized within a Lotus Domino Pooling and works great for about 8-12 tries and then starts erroring out....any help would be appreciated.
02/21/2002 08:50:27 PM Addin: Agent printing: Message: Io exception: socket was closed
02/21/2002 08:50:27 PM Addin: Agent printing: SQLState: null
02/21/2002 08:50:27 PM Addin: Agent printing: ErrorCode: 17002
02/21/2002 08:50:27 PM Addin: Agent error message: java.lang.NullPointerException
02/21/2002 08:50:27 PM Addin: Agent error message: at com.ext.connector.RelData.executeQuery(RelData.java:416)
02/21/2002 08:50:27 PM Addin: Agent error message: at com.ext.connector.Connector.open(Connector.java:487)
02/21/2002 08:50:27 PM Addin: Agent error message: at JavaAgent.NotesMain(JavaAgent.java:20)
02/21/2002 08:50:27 PM Addin: Agent error message: at lotus.domino.AgentBase.runNotes(AgentBase.java:160)
02/21/2002 08:50:27 PM Addin: Agent error message: at lotus.domino.NotesThread.run(NotesThread.java:203)

I don't see any error on the Oracle side which makes me suspect if Domino itself is shutting down the TCP socket as part of a scheduled task/background process. Domino uses JDK ver. 1.1.8. I have tried using both classes111.zip and classes12.zip separately. Also tried including the jdbc 2 jar file. Nothing seems to prevent the socket from getting closed abruptly. Any more suggestions are welcome.
Thanks,
Jacob.

Similar Messages

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

    Fala ae galera.
    tive problemas ao publicar meu primeiro report, exibe o seguinte erro: The underlying connection was closed: An unexpected error occurred on a send.
    Configurações IIS

    Hello,
    Based on the error message, the issue may be related to the “SecureConnectionLevel” in the RSReportServer.config file. When we use HTTP protocol, the value of the “SecureConnectionLevel” attribute should be 0. Usually, we change the value to “1” or “2” only
    when we configure the Report Server for Secure Sockets Layer (SSL) connections.
    Reference:
    http://msdn.microsoft.com/en-us/library/ms157273(v=sql.105).aspx 
    Please refer to the following steps try to resolve the issue:
    1. Use Notepad to open the RSReportServer.config. By default, in SSRS 2012, it is located in: C:\Program Files\Microsoft SQL Server\MSRS11.MSSQLSERVER\Reporting Services\ReportServer
    (Note: Please backup the file before modify it.)
    2. Search for “SecureConnectionLevel” and make sure its value is set to 0. It looks like this:
    <Add Key="SecureConnectionLevel" Value="0"/>
    There is a blog about “The underlying connection was closed…" error message, you can refer to it.
    http://blogs.msdn.com/b/engelsr/archive/2005/11/29/the-underlying-connection-was-closed.aspx
    Regards,
    Alisa Tang
    Alisa Tang
    TechNet Community Support

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

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

  • 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

  • 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

  • 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

  • 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

  • SQLException: Io exception: socket closed: Bad file number;

    Hi,
    My server application connects oracle 8i using thin driver.
    My code opens a connection and create a statement object:
    DriverManager.registerDriver(new oracle.jdbc.driver.OracleDriver());
    Connection connection = DriverManager.getConnection(url, username, password);
    connection.setAutoCommit(false);
    Statement statement = connection.createStatement();
    After a few hours it runs just fine I get the following error:
    java.sql.SQLException: Io exception: socket closed: Bad file number;
    The code line that couses this exception is:
    statement.executeQuery("my SQL query");
    after this there are more errors:
    ;java.sql.SQLException: Protocol violation;
    (in code line: connection.execCommit())
    and than a repeated exception of :
    java.sql.SQLException: Io exception: Broken pipe;
    Does anyone knows a solution? (is the problem in my code or in the oracle account?)
    Thank!!!

    Which package you are using? if you don't have
    classes12.zip, try again by including that package in
    the classpath. If you are already using classes12.zip
    then try by including nls_charset12.zip in the
    classpath.
    You can get these packages in Oracle (otn) website.
    SudhaThanks!
    I had classes12.zip in my classpath, but my classpath also had: classes111.zip
    so i removed classes111.zip from the classpath and as far as now,
    the problem did not occur again!
    (i also added nls_charset12.zip just to be sure)
    Lilach

  • The application, C:\Program Files\Adobe\Adobe Photoshop CS2\Photoshop.exe, generated an application error The error occurred on 10/01/2009 @ 11:31:59.964 The exception generated was c0000005 at address 7C81BD02 (ntdll!ExpInterlockedPopEntrySListFault)

    Hi,
    I get this error randomly when i run my VB 6.0 application which calls Photoshop CS2 actions. I went through many forums, but could not manage to get the right solution for this.
    "The application, C:\Program Files\Adobe\Adobe Photoshop CS2\Photoshop.exe, generated an application error The error occurred on 10/01/2009 @ 11:31:59.964 The exception generated was c0000005 at address 7C81BD02 (ntdll!ExpInterlockedPopEntrySListFault)
    For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp."
    OS: WIndows Server 2003 SP2
    Photoshop CS2
    ANy help on this will be highly appreciated.
    Thanks in advance,
    Smiley

    I see this sort of error notice in Bridge and Photoshop, preceded by the message " Photoshop (or Bridge) has encountered a problem and must close. Tell MS.
    Yes or No."
    It most frequently happens in PS when running Dfine 2.0. I have no clue what triggers the Bridge closure. It happens randomly.
    CS3, so nobody gives a tinkers dam, I suppose.
    I see this kind of message in software testing on a regular basis. Of course, when the test is under way, the software is generating a detailed log file which we package up as part of a bug report. Then at the bug scrubs, lively discussions ensue as to who has to fix what!
    I can only image what would happen if the Dfine people and the PS people had to sit through one of those!

Maybe you are looking for