Andre Naef
asked this on May 31 10:36
I am currently evaluating ScreenSteps Pro for the use combined with our Confluence Enterprise Wiki.
Creating the actual lessons is a very smooth process with ScreenSteps.
Unfortunately, uploading to Confluence is not that smooth. We have enabed the XML-RPC extension in Confluence. The export dialog displays the list of spaces and the list of pages within the selected space on Confluence. So the XML-RPC service would appear to be working and the user authentication is successful as well.
Once the export is started, it aborts half-through most of the time with the error shown in the screenshot attached to this post. After the abort, the target page exists as an empty page in Confluence and has some (but usually not all) screenshots as attachments. And the page is empty. One time, I got lucky and the export just went through completely. This was without any change on the Confluence backend. There is no detectable pattern to the export going through or aborting. We have set the logging level to diagnostic in Confluence, however this does not generate any useful error information in the Confluence logs.
So, I am a bit at at a loss here. ScreenSteps works truely well as a production tool. However, it cannot reliably publish to our Confluence wiki which is the final goal of the effort.
Edit: We are using Confluence 3.1.0.

Hi Andre,
Based on the screenshot you posted it appears that the connection between ScreenSteps (your computer) and your Confluence server is being closed down during the upload process. What is causing the connection to close prematurely is unknown.
If it is possible to set up a test account on your server I would be happy to test out uploading from my office to see if I can reproduce the problem. Just email information to support at screensteps.

Answer
Thanks four your quick reply.
As our Confluence server is located on our intranet and not directly accessible from the outside world, I was about to record a pcap trace with Wireshark. Then I noticed that ScreenSteps traffic between my computer and Confluence was actually going via our proxy server. It would appear that ScreenSteps is honoring the proxy configuration from Internet Explorer. And it is indeed our proxy server that is causing the connection shutdown. After disabling the proxy for our Confluence server, everything is working fine now.
So, the problem is resolved. And perhaps this information is of use to other users, too.

Glad you got it working Andre.