In rare cases, users may experience a crash in the Nx Mediaserver application or the Nx Desktop client. Typically, these are isolated incidents. However, if you are facing a recurring problem, take these steps:

Step 1: Find your current crash dump files

Windows

For Nx Server

C:\Windows\System32\config\systemprofile\AppData\Local\*.dmp

For Nx Desktop

C:\Users\%USERNAME%\AppData\Local\.*dmp

Note: Make sure that these dumps have the same version and build number as the software you are currently using. File names might contain words and phrases "HD_Witness.exe", "mediaserver.exe", or "Nx_Witness.exe".

Ubuntu

For Nx Server

• (GDB backtrace)

  /root/*mediaserver*.gdb-bt
  or
  /opt/networkoptix/mediaserver/var/crash/*mediaserver*.gdb-bt

• (System kernel dmp)

  /opt/networkoptix/mediaserver/bin/core

For Nx Desktop

/home/$USER/desktop_client*.gdb-bt

NOTE: Make sure that these dumps have the same version and build number as the Nx Witness you are currently using. 

Step 2: Enable & produce full crash dump files

This step is optional. Skip it unless the Nx Support Team directs you to complete this step.

Crash Dump files are automatically generated memory stack files that help our developers debug situations that may be causing crashes. Simple crash dumps are generated each time the Nx Desktop or Nx Server application crashes for any reason. However, to fully diagnose the cause of a crash, Nx Developers need the full, more detailed crash dump files. Follow the steps below to enable and produce detailed crash dump files.
 

Windows

1. Open the Windows registry editor (Open Windows Command Prompt > type in "regedit")
2. Add a new string value (Edit > New) with the name createFullCrashDump and value true in the following locations:

   • For Nx Server
      

     HKEY_LOCAL_MACHINE\SOFTWARE\Network Optix\Network Optix Media Server

   • For Nx Desktop
      

     HKEY_CURRENT_USER\Software\Network Optix\Network Optix HD Witness Client

3. Restart both the Nx Desktop client and Nx Server application.
4. Reproduce the crash if possible by going through the original process that caused the crash a few times.  
5. Look for new crash dumps after reproducing the crash. Crash dump sizes should be in the hundreds of megabytes. 

Ubuntu

1. Launch Terminal in Ubuntu (Ctrl+Alt+T)
2. Use a text editor (vi, vim or nano) to open the configuration file and add a new parameter called createFullCrashDump and set its value to true.

   • For Nx Server
      

     /opt/networkoptix/mediaserver/etc/mediaserver.conf

   • For Nx Desktop
      

     /home/$USER/.config/'Network Optix'/'Network Optix HD Witness Client.conf'

3. Save the file and close the text editor.
4. Restart Nx Desktop and Nx Server.
5. Reproduce the issue or crash. 
6. You shall be able to have a crash dump file in the folder presented in Step 1. 
   NOTE: The file size of the crash dump could be large. (i.e., several hundreds of MB.)

Step 3: Upload crash dumps & open a support ticket

1. Upload the crash dumps to a file-sharing app (e.g. Google Drive, Dropbox, Sharefile).
2. Submit a new support ticket and include the link to the uploaded crash dumps - and make sure we are able to access them!
3. We recommend that you return the configuration back to normal after full memory dumps have been collected. Otherwise, full dumps might occupy a lot of storage space. Also, enabling createFullCrashDump will increase the load on the CPU and RAM.

What to do if the required dumps cannot be found on Windows

Sometimes Nx Witness may be unable to produce full crash dump files. In this case, additional configuration is required with the Windows Error Reporting Service to enable and configure the feature (according to this post):

1. Open Registry Editor and navigate to
    

   HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\Windows Error Reporting\

2. Right-click anywhere on the right pane and click New > Key. Type LocalDumps and press enter.
3. Left-click it on the newly created LocalDumps on the left pane.
4. Right-click anywhere on the right pane and click New > Expandable String Value. Type DumpFolder and press enter. 
5. Right-click DumpFolder > Modify. Enter any path into the Value data field (e.g. C:\dumps) and press OK.
6. Right-click anywhere on the right pane and click New > DWORD. Type DumpCount and press enter.
7. Right-click DumpCount > Modify. Enter the dumps count into the Value data field (we recommend typing number 2) and press OK.
8. Right-click anywhere on the right pane and click New > DWORD. Type DumpType and press enter.
9. Right-click DumpType > Modify. Enter the dumps type (we recommend typing number 2) into the Value data field and press OK.
10.  After the application has crashed, dumps will be generated in the DumpFolder. After at least 2 crashes, upload 2 dump files to the file sharing service and share it with our support staff.
11. Send us the generated dumps along with your software version information.
12. Remove the registry changes from your system.

If you need to enable full Dump generation for specific Server and Client processes:

1. Create Expandable String Value keys called mediaserver.exe and HD Witness.exe with the path to each executable.
2. Continue from step 7 above.

Note: We recommend you remove these settings after full memory dumps are archived. Otherwise, full dumps might consume a lot of drive space.