Frequently Asked Question
Errors on configuration N4V services in the CMC
Last Updated 3 years ago
Symptom
- Need4Viz services are started correctly (no error in n4v_xxx_err.log files)
- Need4Viz services cannot be declared in the SAPBI CMC.
Environment
- Need4Viz : all versions
Resolution
In some cases, Need4Viz services cannot be declared in the CMC.
1/ Check if the your SAPBI version is not flagged as a defect version here :
https://www.need4viz.com/support/kb/faq.php?id=35
2/ If the error encountered is the following one :
Check if your N4V key is activated :
- Open the URL http://xxxx:8209/about to see if the key is activated
- Check the files n4v_xxx_out.log in ~Need4Viz_folder_installation/logs folder, you should have a message concerning the validity of the key
If your key is expired, contact our sales team to get a new one.
Once you have a new key.js file :
- Replace the existing one in the ~Need4Viz\nodejs\node_modules\custom_element\ce_libs\ folder
- Open a PowerShell command window as local administror of the server
- Change directory to ~Need4Viz_folder_installation/Scripts/
- Run the Start_Need4Viz.ps1 command
3/ In case of other error :
- Check the URL used to declare the service is correctly whitelisted (cf. installation guide of N4V)
- Check the port used to declare the service is corresponding to the ports defined in the config.js file (in the ~Need4Viz\nodejs\node_modules\custom_element\ce_libs\ folder)
- Check the flows (for instance 8201, 8202...) are opened between your tomcat (SAPBI) server in N4V server