I have assigned this issue to a member of our support staff, and they will begin investigation as soon as possible. If we are unable to reproduce the issue, or we need additional information, our staff member will comment here with additional questions. Otherwise, we will post an ‘Answer’ once we have logged the issue in our bug database or we have a solution for it.
In the meantime, please be sure to review our suggestions for how to report a bug, and feel free to edit your post if you have additional information to provide.
Hi, sorry you’re still having problems with this. Can I confirm what version you are using? The previous report was for 4.2.1, but there was a change put into 4.3 that should output some more useful information into the agent logs.
If you are on 4.3, could you send use all your agent logs again please, so we can try and track down what’s going wrong?
Also, did you make any headway on the other report with respect to the named pipes?
“If you get the editor into the state where it can’t kick off swarm, then load up process explorer (download from here). Once running, choose Find->Find Handle or DLL. Type “\Device\NamedPipe\127.0.0.1” and hit search. If there is anything in the list could you please send us the output?”
I wanted to check in and see if you have had any traction with finding a resolution to this issue when you upgraded to 4.4. Please let me know if you are still having this issue as we are attempting to resolve the Swarm issues at this time.