Blue Iris Update Helper (BiUpdateHelper)

bp2008 said:
Dropbox - update64_4.5.9.6.exe
Click to expand...
Thanks for that although that wasnt the issue turns out it had something to do with the audio being enabled. I was getting same problem on that version to not sure how it was working before.

Disabled the audio and all streams started. Now i need to get a dedicated server for this thing.

Thanks for the quick upload.

Is there any need for a repository of the update files? I work a hosting company and could basically host it for free.
 
They used to be hosted on the official BI website, if you modified the URL to view the directory that the update files were stored in. But at some point the developer turned off that ability.

I think it would be nice if someone hosted an archive of update files :)
 
Thanks for this app - it's really useful.

I have 1.4.1 installed on Win Svr 2012 R2 and BI 4.5.9.7 x64 - it's all working correctly with one exception:

The "Camera Config Links" causes a crash in BiUpdateHelper (type initializer for BiUpdateHelper.BiUserInfo thew an exception). The html file is created but is empty. Here's the dump:

See the end of this message for details on invoking
just-in-time (JIT) debugging instead of this dialog box.

************** Exception Text **************
System.TypeInitializationException: The type initializer for 'BiUpdateHelper.BiUserInfo' threw an exception. ---> System.NullReferenceException: Object reference not set to an instance of an object.
at BiUpdateHelper.UserInfo..ctor(RegistryKey key, String name)
at BiUpdateHelper.BiUserInfo.Reload()
--- End of inner exception stack trace ---
at BiUpdateHelper.BiUserInfo.Reload()
at BiUpdateHelper.CameraWebInterfaceLinker.GenerateWebInterfaceLinkDocument(String outPath)
at BiUpdateHelper.Program.btnCameraConfigLinks_Click(Object sender, EventArgs e)
at System.Windows.Forms.Button.OnMouseUp(MouseEventArgs mevent)
at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks)
at System.Windows.Forms.Control.WndProc(Message& m)
at System.Windows.Forms.ButtonBase.WndProc(Message& m)
at System.Windows.Forms.Button.WndProc(Message& m)
at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)


************** Loaded Assemblies **************
mscorlib
Assembly Version: 4.0.0.0
Win32 Version: 4.0.30319.34014 built by: FX45W81RTMGDR
CodeBase: file:///C:/Windows/Microsoft.NET/Framework64/v4.0.30319/mscorlib.dll
----------------------------------------
BiUpdateHelper
Assembly Version: 1.4.1.0
Win32 Version: 1.4.1.0
CodeBase: file:///C:/BI_UpdateHelper/BiUpdateHelper.exe
----------------------------------------
System
Assembly Version: 4.0.0.0
Win32 Version: 4.0.30319.34239 built by: FX452RTMGDR
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System/v4.0_4.0.0.0__b77a5c561934e089/System.dll
----------------------------------------
BPUtil
Assembly Version: 1.0.0.0
Win32 Version: 1.4.1.0
CodeBase: file:///C:/BI_UpdateHelper/BiUpdateHelper.exe
----------------------------------------
System.Windows.Forms
Assembly Version: 4.0.0.0
Win32 Version: 4.0.30319.34250 built by: FX452RTMGDR
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Windows.Forms/v4.0_4.0.0.0__b77a5c561934e089/System.Windows.Forms.dll
----------------------------------------
System.Drawing
Assembly Version: 4.0.0.0
Win32 Version: 4.0.30319.34262 built by: FX452RTMGDR
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Drawing/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll
----------------------------------------
System.ServiceProcess
Assembly Version: 4.0.0.0
Win32 Version: 4.0.30319.33440 built by: FX45W81RTMREL
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.ServiceProcess/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.ServiceProcess.dll
----------------------------------------
System.Configuration
Assembly Version: 4.0.0.0
Win32 Version: 4.0.30319.33440 built by: FX45W81RTMREL
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Configuration/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Configuration.dll
----------------------------------------
System.Xml
Assembly Version: 4.0.0.0
Win32 Version: 4.0.30319.34230 built by: FX452RTMGDR
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Xml/v4.0_4.0.0.0__b77a5c561934e089/System.Xml.dll
----------------------------------------
Microsoft.GeneratedCode
Assembly Version: 1.0.0.0
Win32 Version: 4.0.30319.34230 built by: FX452RTMGDR
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Xml/v4.0_4.0.0.0__b77a5c561934e089/System.Xml.dll
----------------------------------------
System.Core
Assembly Version: 4.0.0.0
Win32 Version: 4.0.30319.33440 built by: FX45W81RTMREL
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Core/v4.0_4.0.0.0__b77a5c561934e089/System.Core.dll
----------------------------------------
System.Management
Assembly Version: 4.0.0.0
Win32 Version: 4.0.30319.33440 built by: FX45W81RTMREL
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Management/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Management.dll
----------------------------------------

************** JIT Debugging **************
To enable just-in-time (JIT) debugging, the .config file for this
application or computer (machine.config) must have the
jitDebugging value set in the system.windows.forms section.
The application must also be compiled with debugging
enabled.

For example:

<configuration>
<system.windows.forms jitDebugging="true" />
</configuration>

When JIT debugging is enabled, any unhandled exception
will be sent to the JIT debugger registered on the computer
rather than be handled by this dialog box.
 
Andrew S said:
Thanks for this app - it's really useful.

I have 1.4.1 installed on Win Svr 2012 R2 and BI 4.5.9.7 x64 - it's all working correctly with one exception:

The "Camera Config Links" causes a crash in BiUpdateHelper (type initializer for BiUpdateHelper.BiUserInfo thew an exception). The html file is created but is empty. Here's the dump:
Click to expand...

Hmmm... looks like it fails when trying to read the user info out of the registry (this is used to log in to Blue Iris to grab snapshots from all the cameras). If you know your way around the registry editor, you could export
SOFTWARE\\Perspective Software\\Blue Iris\\server\\users and send it to me via private message and I will see if I can figure out what would have broken it. This does contain passwords encoded as base64 so you don't want to post it publicly unless you mask the password values in the exported file first.

It is also possible this is a matter of strange registry permissions... though this app requires administrator to even launch, and Blue Iris's registry keys don't have any specific protection I know of.
 
Andrew S said:
Thanks for this app - it's really useful.

I have 1.4.1 installed on Win Svr 2012 R2 and BI 4.5.9.7 x64 - it's all working correctly with one exception:

The "Camera Config Links" causes a crash in BiUpdateHelper (type initializer for BiUpdateHelper.BiUserInfo thew an exception). The html file is created but is empty. Here's the dump:

See the end of this message for details on invoking
just-in-time (JIT) debugging instead of this dialog box.

************** Exception Text **************
System.TypeInitializationException: The type initializer for 'BiUpdateHelper.BiUserInfo' threw an exception. ---> System.NullReferenceException: Object reference not set to an instance of an object.
at BiUpdateHelper.UserInfo..ctor(RegistryKey key, String name)
at BiUpdateHelper.BiUserInfo.Reload()
--- End of inner exception stack trace ---
Click to expand...

Did you happen to rename the admin user?

Looks like the code assumes you still have a user named 'admin'.
 
kdub said:
Did you happen to rename the admin user?

Looks like the code assumes you still have a user named 'admin'.
Click to expand...

The problem was that his user named "admin" did not have any of the normal user properties, so the code failed to read them and boom. I'm don't know how that situation came to be, but the important thing is that I added the try / catch on lines 26-34 of that file to ensure that errors loading any user info from the registry won't cause a crash. The bug has been fixed.
 
  • Like
Reactions: kdub
Yes, it's fixed thank you I think what happened was that when I built this new install I created another administrative user and then didn't go back and change the password for the existing admin user which meant that it was in its 'initial' state. Great response from bp2008 - much appreciated.
 
BP, thanks for this tool. It saved me from a recent Blue Iris update that caused my hard drive to fill up, lost footage of many random cars on my street, and long story short, it also prevented me from cutting off my left nipple with a box fan.

Question: Will it ever be (or can it even be) integrated into your Blue Iris Tools app?
 
OH, right, that's Mike. Sorry. That said, it'd be cool if it were implemented in one program, if you and Mike got together.
 
Just installed this and want to make sure I understand how it works before I do an update. I'm I supposed todo the updates like normally through BI or what's the process?
 
ZyBeR said:
Just installed this and want to make sure I understand how it works before I do an update. I'm I supposed todo the updates like normally through BI or what's the process?
Click to expand...

Yeah update normally and it’ll save the old exe’s in the BI program file folder
 
I've just downloaded, extracted and installed but as soon as I try to start I get;

System error 193 has occurred.

*** is not a valid Win32 application.

My system is W10 64bit and BI version is 4.6.0.3 x64

any ideas??
 
It sounds like there may be something wrong with your system, or the exe got corrupted somehow during download/extract. I suggest you delete the old zip and exe you extracted, reboot just for good measure, then download and extract again.
 
  • Like
Reactions: Tinbum
Thanks for the quick reply.

Did all that but still didn't work, then changed the location that I had saved the extracted files to and it all worked. Happy!!
 
Thank you for taking the time to make this program.
I am seeing an error in my log.
Exception thrown at 9/19/2017 12:00:01 AM
System.ComponentModel.Win32Exception (0x80004005): The system cannot find the file specified
at System.Diagnostics.Process.StartWithCreateProcess(ProcessStartInfo startInfo)
at System.Diagnostics.Process.Start(ProcessStartInfo startInfo)
at BiUpdateHelper.RegistryBackup.ZipFile(String SourcePath, String TargetFile)
at BiUpdateHelper.RegistryBackup.<>c__DisplayClass0_0.<BackupNow>b__0()
 
I am having an issue trying to extract license keys from two different installations of multi-camera Blue Iris v3 systems. First, I'm moving a Windows Vista BI v3 over to a Win 10 system. I don't have the email with the original license key for my Vista's installation when I purchased the license a few years ago, so I figured I'd try the BIupdatehelper v1.4 app to view the key. Problem is what you see in the attached photo... When I click BI Registration Info, I get Registration Code: Not Found and Name and Email are blank. So, on a completely different system, a Windows 10 installation of multi-camera BI v3 that is running just fine with its own license key, I get the same problem running BIupdatehelper. In other words, I get the same response from BI Registration Info. Reg code is Not Found and Name/Email are blank. I've tried emailing Blue Iris (to their sales and support email addresses_ to try to get my key back from them again, but haven't heard back from them in weeks. So, I was hoping I could grab the original key using BIupdatehelper. Can anyone help figure out why in two separate instances I cannot get the key to appear using this app? (I also tried various prior versions of the app after 1.4 didn't work for me. Same issues.) Thanks in advance! --Kal
 

Attachments

  • BIupdatehelper-noReg.jpg
    BIupdatehelper-noReg.jpg
    4.4 MB · Views: 12
You must log in or register to reply here.
Top Bottom