From services.msc, check that the BriefCam VSService status is running.

If it is running, right-click, select Properties and check that you are logged in with the correct user credentials:

1. The service should be run by the user selected during the installation of BriefCam.

2. Check that the password is correct.

3. For all-in-one environments, check that the user has Admin privileges.

In the BriefCam Administrator Console, confirm that the Processing Server and Alert Processing Server services are running.

Check the ProcessingServer.log file located at: C:\Program Files\BriefCam\BriefCam Server\logs. This gives information about the required decoder and plugin and processing info (processing duration, FPS, video format and more). In the log file, click Ctrl+End to go to the end of the file and search backwards for the words: task taken. This is when the processing server actually took the video to process. You'll also see here the name of the video, start and end time, and more.

Check that the following firewall ports are open:

In certain cases, following a crash, the processing server moves to a 'suspended' state, causing active processing requests to stall. To resolve this issue, disable the Windows dump files by opening the regedit, clicking on the following registry key: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CrashControl and changing the value of CrashDumpEnabled to 0.

Or, set the Agent.AggressiveShutdownOnCrashRecovery environment setting to true.