This article identifies known errors and fixes based on Windows dependencies.
Gotchas
This section documents learnings from past tickets.
BI Dependencies
VC++ Libraries
Both of the above error messages stem from the same issue. BI is a C++ program that runs on Windows. The program relies heavily on Microsoft's VC++ libraries.
If the installer fails, often your Windows machine does not have the right version of VC++ installed.
Download/install libraries from Microsoft.
The error message is saying
- Either you decided to save your recordings in a non-BVR format, e.g. MP4. If your New directory has mp4 recordings instead of BVR recordings, this is the issue.
Most users switch recordings back to BVR format for its many advantages, including playback in the UI.
If you decide to remain in MP4 format, most users just double-click the mp4 file in Windows Explorer and has it play on Windows default player. If you want to play an mp4 within BI, please install the k-lite plugin. You need only the “basic” version.
See FAQ section in Help for details. - Or the BVR recording was somehow corrupted.
Check your New folder. If you now have many files that are small like 1K, then BVR files are being corrupted.
Fix:- The most common problem is the key frame issue.
- If that does not work, check your camera encoding settings.
- Alternatively, check for Storage issues.
- Finally, check for database issues.
"Error importing the registry Key:5"
Running BI without admin privileges or security software (Kaspersky) is preventing access to registry. Error code 5 means access denied.
- Run REGEDIT and locate the key "HKLM\Software\Perspective Software\Blue Iris Import". It's the import key you want.
- Find the 'a1' key in "HKLM\Software\Perspective Software\Blue Iris Import" and right-click edit permissions. Add "full control" to the administrators group.
- You should now be able to delete the import key and startup.
- Go through the Windows Tuning article to make sure Windows is not in conflict with Blue iris.
https://blueirissoftware.com/forum/view ... =12&t=2080
It sounds like the camera may be open in a window behind the main window, another monitor, or possibly minimized?
You can always run REGEDIT and delete the camera from this key:
HKEY_CURRENT_USER\SOFTWARE\Perspective Software\Blue Iris\Cameras --> NOTICE this is CURRENT_USER and not LOCAL_MACHINE!!
This is where the window position and state are memorized.
The path you listed to save the registry settings does not exist. Need to reset the path.
Global settings -> About tab
Errors associated with running BI as a service.
1057 Error
If you get the 1057 error, i.e. “Failed to install service (1057)”, the username chosen to run the service does not exist or is invalid. See Service section of Windows Tuning article to create a local Windows account with admin privileges. Run Windows Services -> Right click Blue Iris Service -> Properties -> Log on tab. Specify username / password.
The 1069 Windows error occurs when the password associated with the Windows username associated with the service has changed. Run Windows Services -> Right click Blue Iris Service -> Properties -> Log on tab -> reset the password.
In order to run a Windows Service, the Windows account has to have password.
- Stop the Blue Iris Service manually. From the Windows search bar, type services and bring up the Services console.
- Select the Blue Iris service.
- Select "Stop service"
- Start BI.
- Return to BI. Global settings -> Startup tab -> Run as a Windows service. Check the selection.
- Restart BI. BI should start as a service.
- Stop Blue Iris manually.
- Restart the machine.
- Find where you downloaded the update or just go to blueirissoftware.com and download the latest version.
- Install/start the latest version and you should be good to go.
12002 Error
Communication issues related to error 12002 and 12029 are usually related to a network block of some sort. This is often due to the Windows firewall blocking access to the BI Web server for communication.
Symptoms: UI3 or the Mobile apps stop working.
Test: When you start experiencing issues, restart BI. Confirm via Remote Access Wizard whether the web server is running initially via the Web Server page.
When remote access breaks (UI3, mobile apps), recheck via the Wizard whether the web server is accessible.
Fix: Double check your Windows anti-virus and firewall settings. Double check your router settings. Something is blocking traffic to the web server. If problem persists contact support.