Summary: describes how to ensure that all Nodes are running.

Ensure all the Node back-end packages you have installed on dedicated Nodes are running. This should be done regardless of whether you are using a single or a multi-node deployment scenario. To start the Node back-end package, you can do any of the actions listed below. You will need to do this on EACH Node where you have installed the Node package.

For those using the standalone deployment mode, the Node should already be running with Console.


If it is not already running, start the Windows Service:

If you have chosen to install the Node package as a Windows Service, then CAST recommends using this method.

Use the shortcut on your desktop or in the Windows start menu.

These two methods should only be used if you have not chosen to install the Node package as a Windows Service.

The Node package will start in a CMD window. Check to ensure that you see the line "Started Application" as shown below highlighted in red (click to enlarge):

  • The CMD window must be kept open to keep the Node package running.
  • You may be prompted to allow the application through the Windows firewall - click Allow access:

  • If you click in the CMD window once the package is running, be aware that this may unintentionally pause the package. This is due to the default settings in Windows for the CMD window where clicking anywhere in the CMD window changes it into "selection" mode and pauses the running application. To resolve the issue:
    • tap the ESCAPE key to change the CMD window back to normal mode - this will start the package again
    • consider changing the CMD defaults to avoid this issue altogether - right click the CMD window toolbar and select Defaults. Then untick QuickEdit Mode in the Options tab:

Run (i.e. double click) the following batch file:


If the package fails to start, you can check the error logs here (see also AIP Console - Logging mechanisms):