Issue with reinstall on Windows Server 2022

I have fixed this issue!

I am confirming that my previous server was running v1.9.5.0 and my new server is running v1.9.5.0. both 64-bit.

I reviewed all forums posts related to this and tried the following:

  1. Uninstall Netcam Studio 1.9.5.0 64-bit
  2. Remove all data from:
    2.1. C:\ProgramData\Moonware\
    2.2. C:\Program Files\Netcam Studio - 64-bit
    2.3. C:\Users\[user]\AppData\Local\Moonware_Studios\
    2.4. C:\Users\[user]\AppData\Roaming\Moonware\
  3. Confirm installation of:
    3.1. Feature : .NET Framework 4.8
    3.2. Feature : Media Foundation
    3.3. Program: Microsoft Visual C++ 2015-2019 Redistributable (x64)
  4. Reinstall Netcam Studio 1.9.5.0 64-bit
  5. Start the NCS service successfully
  6. Access Netcam Studio Client to confirm connectivity
  7. Stop the NCS service
  8. Copy files Netcam.Security.xml, Rules.xml, & Server.config to C:\ProgramData\Moonware\Netcam Studio\Server\
  9. Start the NCS service
  10. Error Service cannot be started. System.NullReferenceException: Object reference not set to an instance of an object occured
  11. Removed Netcam.security.xml and Rules.xml
  12. Start NCS service
  13. Service started correctly
  14. When accessing Netcam Studio Client, had to use u:admin p:1234 rather than my previous settings
  15. Confirmed all camera sources were correct
  16. Checked settings and confirmed library target and other values were correct
  17. Used Access Control to set admin password and add other users
  18. Exited Netcam Studio Client
  19. Restarted Netcam Studio Client and confirmed settings were saved
  20. Closed Netcam Studio Client
  21. Stopped NCS service (only way to make the next bit work)
  22. Opened Netcam Studio X
  23. Accessed the license key area
  24. Entered license key and confirmed online activation
  25. Closed Netcam Studio X
  26. Started NCS service
  27. Confirmed with both web view and Netcam Studio Client that all sources were visible, logging, and licensed

Problem fixed. The root cause seems to be an issue when copying over the security and/or rules configuration XML files. This may warrant testing and adjusting the directions if necessary.

1 Like