SharePoint Webservice issue in WF : Error returned from server: The underlying connection was closed: An unexpected error occurred on a receive.

HI All,

We have a NIntex workflow configured in to run in addition of document in a document library. A component in nintex calls the SharePoint OOTB webservice to update document properties. 

The issue here is sometimes, the webservice calls fails with the error message 

" Error returned from server: The underlying connection was closed: An unexpected error occurred on a receive."

I have checked the timeout value in IIS and web.config. Both are set to 300 secs. The ULS logs are not elaborative to find the root cause of the issue. Kindly help on this. Is there a specific way to debug this.

Thank you in anticipation.

Regards

Karthik R

August 17th, 2015 12:10pm

Hi,

According to your description, my understanding is that there is sometimes an error message in Nintex workflow.

Please make sure you register the service correctly. You can refer to:

http://letrasandnumeros.com/2013/01/17/register-spworkflowservice-the-underlying-connection-was-closed/

Since we have no documentation about Nintex workflow and may not provide more help to you about Nintex workflow. I suggest you post the issue to the Nintex workflow forum, and you would get more professional help and confirmed answers here.

https://community.nintex.com/welcome

Feel freely to reply if you need more help about SharePoint.

Thanks,

Dean Wang

Free Windows Admin Tool Kit Click here and download it now
August 18th, 2015 3:37am

Hi,

According to your description, my understanding is that there is sometimes an error message in Nintex workflow.

Register-SPWorkflowService is used to configure the SharePoint host to use a workflow service by using the SPSite and WorkflowHostUri parameters. Please make sure you register the service correctly.

http://mohan1315.blogspot.com/2013/09/register-spworkflowservice-spsite-error.html

Please remove the component in Nintex calls the SharePoint OOTB web service and test whether the error occurs. If not, it seems the error is caused by SharePoint OOTB web service. If yes, please make sure you have configured workflow management service correctly.

Steps to troubleshoot workflow management service:

https://msdn.microsoft.com/library/azure/jj193529%28v=azure.10%29.aspx?f=255&MSPPError=-2147217396#WorkflowManagementService

Thanks,

Dean Wang

August 18th, 2015 7:35am

Hi Dean,

Thank you for the reply. YEs, I have checked all those setting. The workflows are registered properly. Also we removed the 'call web service' component from Nintex and the error disappeared. Hence I believe the issue is from web serice. 

Here is the additional logs which we got.

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)

Can you advise more on this.

Free Windows Admin Tool Kit Click here and download it now
August 18th, 2015 11:47am

Hi Kratzzz,

This error usually happens when the HTTP web request to a server failed due to connection timeout or security reason. If you have enabled SSL in your web applications, please first verify whether the SSL certificate has been expired. The following article explains the similar issue with this reason:

http://social.technet.microsoft.com/wiki/contents/articles/25869.the-underlying-connection-was-closed-could-not-establish-trust-relationship-for-the-ssltls-secure-channel-sharepoint-2007.aspx

If the reason is not security related, my suggestion is to create a simple external web application, and consume your SharePoint web services from it to try to reproduce the issue. Once issue can be reproduced, use fiddler or other network trace tools to analyze the root cause of the issue.

Thanks,
Reken Liu

August 23rd, 2015 11:51pm

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics