Dear All,
Would like to seek for your advise on why my processes keep encountered Connection Refused Error whenever after the service of OLConnect_Server being restarted?
What is the possible root causes and how to prevent it?
Many Thanks.
Hello @CLTeh,
Can you let us know please whether you are wondering why the following error is logged by executing a OL Connect Workflow plugin even after restarting the PlanetPress Connect Server service?
W3001 : Error while executing plugin: Socket Error # 10061 Connection refused
Can you please confirm whether this is correct and, if so, whether the following is correct too?
- Check via the (Windows) Services application whether the PlanetPress Connect Server service, also called the PlanetPress Connect Service service, does have the status “Running”
- Check whether the OL Connect credentials, as entered in OL Connect preferences (1) in the Workflow Configuration application, matches with the OL Connect credentials of one of the users as available in the list of Security and Users in the Connect Server Configuration application (2).
(1) These preferences can be accessed by executing the following steps:
- Open the Workflow Configuration application
- Click on the PlanetPress Workflow button in the top-left corner of the application
- Click on the Preferences button
- Go to PlanetPress Workflow Preferences window > Behavior > OL Connect > Server Connection Settings
(2) These settings can be accessed by going to: Connect Server Configuration application > (Preferences window) > Connections > Security and Users > Authorized Users
Hi @Marten,
Yes, I am encounter the below error after restarting the PlanetPress Connect Server service.
W3001 : Error while executing plugin: Socket Error # 10061 Connection refused
PlanetPress Connect Server service was in “Running” status before I trigger a Workflow process and OL Connect credentials are correct. And both PlanetPress Workflow Preferences and Connect Server Configuration are able to access.
For your information, this error is no longer appear when I re-trigger the same Workflow process, which means it only happen once after PlanetPress Connect Server service restarted.
According to Windows Event Log, I noticed that PlanetPress Connect Server service was encounter timeout error when trying to start. Refer to below:
It seems like PlanetPress Connect Server service is not 100% started, even it was in “Running” status.
Is there any ways to avoid this kind of error?
Thanks.
Did you find a resolution to this issue?
With some installations, the OL Connect service will fail to start after a reboot is it is set to Automatic start instead of Automatic delayed start, so I set the OL Connect service to Automatic delayed start. Failing to do so requires human intervention to manually start the OL Connect service.
In my current case with both the OL Connect service and OL Connect workflow service set to Automatic delayed start, the OL Connect workflow service attempts to process files before the OL Connect service is fully running. Subsequent files will work because the OL Connect service is running by them. It is fault tolerant, except for the file that fails immediately after the reboot. IF a file isn’t there to process, then there isn’t an error, however it does appear to happen enough to be a nuisance.
One may try to use Windows service dependencies to ensure that Workflow does not start before OL Connect. In admin command prompt run:
sc config ppwatch8 depend= winmgmt/olconnect_server
If this is not enough, add startup process to the workflow and either use a script to call OLC REST API (e.g. handshake endpoint Service Handshake), or add a loop using e.g. olc upload task with delay
Thanks, I believe that using a dependency will work.
I added the olconnect_server as a dependency yesterday afternoon and are monitoring. I tested this on my NFR trying to force the condition and it appears to work well.