Unable to publish Workflows locally in Workflow 7.5 with error "No connection could be made because the target machine actively refused it".
Last Updated September 30, 2013
When trying to publish a Workflow locally on a Workflow 7.5 server or a ServiceDesk 7.5 server, the error "No connection could be made because the target machine actively refused it" occurs. The logs will reference the local machine IP address and port 11434. This occurs while remoted into the machine via Remote Desktop Connection (or another remote solution).
No connection could be made because the target machine actively refused it.
The default settings for the Allow Remote Connections in the LocalMachineInfo Editor have changed. Due to customer requests, this is disabled by default in Workflow 7.5.
Workflows may be published by locally logging into machine, or by enabling Allow Remote Connections in the LocalMachineInfo Editor. Here are the instructions to enable this:
1. Go to Start > All Programs > Symantec > Workflow > Workflow Designer > Tools > LocalMachineInfo Editor.
2. On the Local Machine Info tab, click on the ellipse for Workflow Server Configuration.
3. In the General section, check the checkbox for Allow Remote Connections. Click OK.
4. Click Yes to the dialogue asking to save changes.
5. Say Yes to resetting Server Extension services.
You should now be able to publish workflows while logged into the Workflow server via a remote connection.
Imported Document ID: TECH211084
Subscribing will provide email updates when this Article is updated. Login is required to Subscribe