Frequently Asked Question

Symptom

• Need4Viz services have never been created

OR

• Need4Viz services cannot be started/stopped through the Central Configuration Manager.
  

Environment

• Windows Server
• Need4Viz : all versions

Resolution

1. Open a PowerShell command window as local administror of the server. If Need4Viz services have never been created, go to step 11.
2. Open the Central Configuration Manager and stop the BOEXI40Need4Viz service :
3. Check if services are stopped, run a pm2 -list command. You should get the following screen, if it's the case go to step 7 : 
   
4. If services are started, you should get the following screen :
5. Run the Stop_Need4Viz.ps1 command in the ~Need4Viz_folder_installation/Scripts/ directory.
6. Run a pm2 list command. You should get the screen as in step 3.
   
7. Run a pm2 kill command.
8. Open a Command Prompt and run the command sc delete boexi40need4viz.exe : 
9. Check in the Central Configuration Manager that the Need4Viz service does not exist anymore : 
10. Open the folder ~Need4Viz\nodejs\node_modules\pm2-windows-service\src\daemon and delete all files in it
11. In the PowerShell window, run the Create_Need4Viz_Service.ps1 in the ~Need4Viz_folder_installation/Scripts/ directory, answer "n" to the prompt : 
12. Check if services are started, run a pm2 list command. You should get the following screen :
    
13. Check in the Central Configuration Manager that the service is correctly created :

After these steps, you should be able to stop/start correctly the Need4Viz services through the Central Configuration Manager. Close the PowerShell window. You can check via the Windows Task Manager that the node services are correctly started/stopped : 

Possible issue

In case of restricted policy to execute scripts in the PowerShell window :

1. run the set-executionpolicy unrestricted command
2. answer o for the validation