Skip to main content

Task Server Showing as Not Running in Task Server Administrator Despite Running on The Task Server Server

A
Written by Antoine Larsen
Updated over 2 months ago

This issue occurs when there is no inbound rule set in your firewall to allow access to the command and message ports that are displayed in task server administration under the Server tab for each task server.

To correct this, you will need to have your IT create an inbound rule in your advanced firewall settings as follows:

  1. Open Windows Defender Firewall and select Advanced Settings.

  2. Select Inbound rules and then select New Rule.

  3. Set the rule type as port then click Next.

  4. Enter the port numbers specified for each Message and Command port for each task server in the Specific Local Ports field. These should be separated by commas. Click Next.

  5. Ensure Allow The Connection is selected, then click Next.

  6. Ensure Domain and Private are selected, then Click Next.

  7. Name the rule Allow Ports For Proclaim Task Server, then click Next.

  8. Click Finish.

If you have any Additional/alternative programs in use for Firewall configurations such as ESET, then you will need to configure/ white-list The settings within these programs to allow the necessary Openedge Graphical Client sessions related to the task servers to communicate correctly.

Note: the actions mentioned in these notes will need to be carried out by your IT team, our support staff will NOT make changes to your firewall settings in any scenario.

Information about Ports

Command Port contains the TCP port number which should be used to allow communication with the Task Server controller.
Message Port contains the TCP port number which should be used to send messages to the originating user when working with a Continuous type server.

Did this answer your question?