Important Notice: Our web hosting provider recently started charging us for additional visits, which was unexpected. In response, we're seeking donations. Depending on the situation, we may explore different monetization options for our Community and Expert Contributors. It's crucial to provide more returns for their expertise and offer more Expert Validated Answers or AI Validated Answers. Learn more about our hosting issue here.

I am getting an unexpected server side protocol timeout error (502) and no SOAP response is sent back. What could be causing this?

April 26, 2017Error Protocol Response sent server Soap timeout unexpected

0

Posted

I am getting an unexpected server side protocol timeout error (502) and no SOAP response is sent back. What could be causing this?

1 Answer

0

Posted

WebWorks_WriteArrow(WebWorksRootPath, “wwdd1028221”, true); WebWorks_WriteDIVOpen(“wwdd1028221”, true); Check the timeout settings on any intermediaries that you are using — such as proxy servers or port sniffers (SOAPScope). To edit the timeout setting for SOAPScope, you need to edit the httpd.conf file to the desired settings and then restart the SOAPScope service. The httpd.conf file is located in the conf subdirectory of the SOAPScope data directory. Note: There is a link to the SOAPScope data directory in the Start menu. In the following code the default Timeout value of 300 has been changed to 901.