web
You’re offline. This is a read only version of the page.
close
Support Portal

Application /Product Knowledge

Field Analytics - NodeRed Version Error

Article No: KA-10308
Version: 1.0
Subject to change without notice
Symptoms: NodeRed not Running in services, red x showing on nodered files path
Related Products
AN-64500, FA, 1 - 3 SYSTEMS, PER SYSTEM
FieldAnalytics

Table of Contents

Issue:
certification issue when trying to access FA Node-RED

I'm getting this error message in the Node-RED logs, and the Node-RED service won't start. Even after restarting it the service stops again immediately.

Solution:
The error is due to multiple node.js modules/versions installed with different configurations, that's why it is giving that error.
 
 
STEP1: Compare the conflicted node versions
  • Open CMD, copy paste "node -v"
    • Will give you version result (e.g. v23.11.1) [This would be the version that may have been on the computer before FA was installed]
  • Now copy and paste the path to nodejs used by FA, " "C:\Program Files\SICK\FieldAnalytics\node-red\runtime\nodejs\node" -v "
    • Result will give you a different version (e.g. v18.16.0) [This would be the version installed with FA]

*If the two versions are different, then we can confirmed that there is a version conflict.

STEP2: Edit Path of NodeRed start-flow

  • Navigate to "C:\Program Files\SICK\FieldAnalytics\node-red" and create a backup of "start-flows.bat".
    • Simply copy paste the bat in the same path, "start-flows-copy.bat"
  • Edit the original "start-flows.bat" file
    • Find the line containing "PATH|find /i "nodejs" >nul || set PATH=%CONNECT_PATH%\nodejs;%PATH%"
      • Delete "PATH|find /i "nodejs" >nul || "
    • End Result "set PATH=%CONNECT_PATH%\nodejs;%PATH%"
      • VIEW BEFORE AND AFTER IMAGES BELOW
    • Save

STEP3: RUN .bat file

  • open CMD
  •  "cd C:\Program Files\SICK\FieldAnalytics\node-red"
  • "start-flows.bat"
  • Enter

STEP4: Restart in Services

  • Close cmd
  • open services
  • Restart SICK NodeRed Service

Nodered should still be running, Login to FA and check NodeRed, Issue should be solved

 

**The issue was caused by having two different versions of Node-RED installed. The script is designed to first check the environment variable for Node.js and use that version if it’s set; otherwise, it falls back to the local Node.js instance. In this case, the Node.js version defined in the environment variable was incompatible, which led to the problem.

 
Keywords:
NodeRed, NR, NodeRed Error, NodeRed Version, NR Version
Create request