Refresh the main view when the pop up was closed

Hi,all
how can I refresh the main view when the pop up window was
closed to see the updated data? In pop up window I update
single row in the table based in main view.
Regards,
Michael

Michael,
There are 2 type of pop-ups in WD, and the answer is different depending on which type you are using:
1. Stand-alone browser window that hosts separate application (result of IWDWindowManager.createNonModalExternalWindow) -- no way.
2. Inner pop-up created via IWDWindowManager.createModalWindow -- absolutely possible:
-- a. Create event in component controller (probably with parameters)
-- b. Create method in component controller that fires this event (with corresponding parameters, if any)
-- c. In view that corresponds to window invoke method created in [ b ] and hence fire event. This should be done in action handler of something like "OK" Button or "Close" LinkToAction.
-- d. In any other controller subscribe to event described in [ a ]
Valery Silaev
SaM Solutions
http://www.sam-solutions.net

Similar Messages

Issue with complete refresh on materialized view when using rownum

Hi all,
I had an issue with rownum when using complete refresh
I am using rownum when creating materialized view and it is generation correctly.But the issue was when i am refreshing the same ,rownum was not getting sorted in ascending order.
anyone had come across this scenario

rownum is determined as the row is output, so "order by rownum" does literally nothing.
http://docs.oracle.com/cd/B19306_01/server.102/b14200/pseudocolumns009.htm

[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

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

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.

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

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

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

The underlying connection was closed. An unexpected error occurred on send

Hi,
I am unable to log into the BPC Admin console. I get this error "The underlying connection was closed. An unexpected error occurred on a send".
I saw a SAP message indicating that turning the Norton firewall off resolves this. I don't have this on my computer. Any ideas on what causes this and how to resolve it?
thanks
Agnes

The problem probably is in the network connection of the machine.
I have seen this problem when I logged in to SAP BPC through a very weak WLAN connection which sometimes lost connection. If the connection was lost during a data send I got this error. So maybe it has something to do with a bad network connection on the machine you are working on.
Side note, I only experienced the problem when I logged on to a Citrix environment throug an internet connection.
When I have a decent connection I don't experience the problem.

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

The underlying connection was closed: Could not establish trust relationship for the SSL/TLS secure channel.

I tried to redeem a digital download copy of a movie and was presented the following error:
The underlying connection was closed: Could not establish trust relationship for the SSL/TLS secure channel.
Any guesses on what it is and how to resolve it?
Thanks

Hi
Abhilash Francis,
Could you tell us your scenario? What's your project? Is it a WCF service?
Looks like this is not a code issue.
Just from the error information,
it seems that you do not configure the service certificate very well so as to Server was unable to process request.
I am not completely sure what the real scenario is, but it might be a problem of that It is a WCF services application, please check these following articles to configure the service certificate.
If not, please feel free to let me know.
How to: Configure an IIS-hosted WCF service with SSL
Could not establish trust
relationship for the SSL/TLS secure channel
Hope this helps.
Best regards,
Kristin
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.

Refresh the main view when the pop up was closed

Similar Messages

Maybe you are looking for