Skip to main content

BriefCam Troubleshooting Guide

The services keep crashing and I can't log into BriefCam. How can I validate the integrity of the BriefCam license component?

Last Updated: 1 minute read
Version2024r2
LanguageEnglish

Sometimes certain antivirus applications or security software can break the BriefCam license.

This would result in constant service crashes and an inability to log into the BriefCam Client and BriefCam Administrator Console.

To solve this, try validating the integrity of the license by carrying out the following steps:

  1. Restart the Windows OS.

  2. Verify that the license files exist in the following folders:

    • C:\Program Files (x86)\Common Files\SafeNet Sentinel\Sentinel LDK\installed\92529 

    • C:\ProgramData\SafeNet Sentinel\Sentinel LDK 

  3. Send screenshots or text explanations of the contents of the folders in step 2 to BriefCam support.

  4. Verify that the license service is running:

    1. Open Services.msc.

    2. Look for Sentinel LDK License Manager and make sure it is in Running status.

  5. Verify that the license web interface is accessible:

    1. Open the internet browser on the BriefCam server.

    2. Navigate to the following URL: http://localhost:1947.

    3. Click on Sentinel Keys on the left-side table.

    4. Take note of the KEY IDs in the table.

    5. Send screenshots or text explanations of the licenses table to BriefCam support.

  6. Verify that the license module DLL files have not been deleted/quarantined by the anti-virus software:

    1. Go to C:\Program Files\BriefCam\BriefCam Server or wherever you installed the BriefCam server.

    2. Verify the existence of the following DLL files:

      • hasp_act_windows.dll 

      • hasp_act_windows_x64.dll 

      • hasp_net_windows.dll 

      • hasp_windows_92529.dll 

      • hasp_windows_x64_92529.dll 

      • haspdnert.dll 

      • haspdnert_x64.dll 

  7. Verify that the DLL files listed above are not blocked, by right-clicking on each of them and going to Properties and looking at the bottom for the Security section. Note that if the DLL files are not blocked, the “Security” section might not exist, in that case, skip this step.