Strange behavior since 2.7.0 late I could use some help on.
Free all in one audio/video ffmpeg batch encoder
Brought to you by:
eibol
Menu
▾
▴
Hello, Hopefully I am entering this issue correctly, as this is the first time since using this program that I have an issue, the forums did not already explain. I recently had to rebuild my Media Server and moved to Windows Server 2022 Data Center from Server 2019 Data Center, but this issue appeared in both Versions of Windows I was using. The issue I am having is that I cannot upgrade past version 2.5.4 to any version with the "Security and Performance" feature. If I do the application closes while performing any jobs I run while leaving the FFMPEG process running in the background to finish the job it was on. If I go into "Security and Performance", or i try to update the FFMPEG version I get the below message. If I "Quit", the program closes out entirely. If I "Continue" then the "Security and Performance" Window opens but never fills in the Top section and will not allow me to update anything. I have added the Folder and FFMPEG files to the "exclusions" for the Microsoft AV (Not using another at the moment). Would anyone know what this "invalid Namespace" error means? Thank you.
See the end of this message for details on invoking
just-in-time (JIT) debugging instead of this dialog box.
** Exception Text **
System.Management.ManagementException: Invalid namespace
at System.Management.ThreadDispatch.Start()
at System.Management.ManagementScope.Initialize()
at System.Management.ManagementObjectSearcher.Initial ize()
at System.Management.ManagementObjectSearcher.Get()
at FFBatch.Form25.Form25_Load(Object sender, EventArgs e)
at System.Windows.Forms.Form.OnLoad(EventArgs e)
at System.Windows.Forms.Form.OnCreateControl()
at System.Windows.Forms.Control.CreateControl(Boolean fIgnoreVisible)
at System.Windows.Forms.Control.CreateControl()
at System.Windows.Forms.Control.WmShowWindow(Message& m)
at System.Windows.Forms.Control.WndProc(Message& m)
at System.Windows.Forms.Form.WmShowWindow(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.8.4515.0 built by: NET48REL1LAST_C
CodeBase: file:///C:/Windows/Microsoft.NET/Framework64/v4.0.30319/mscorlib.dll
FFBatch
Assembly Version: 2.7.7.0
Win32 Version: 2.7.7
CodeBase: file:///C:/ProgramData/FFmpeg%20Batch%20AV%20Converter/FFBatch.exe
System.Windows.Forms
Assembly Version: 4.0.0.0
Win32 Version: 4.8.4515.0 built by: NET48REL1LAST_C
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Windows.Forms/v4.0_4.0.0.0__b77a5c561934e089/System.Windows.Forms.dll
System
Assembly Version: 4.0.0.0
Win32 Version: 4.8.4488.0 built by: NET48REL1LAST_C
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System/v4.0_4.0.0.0__b77a5c561934e089/System.dll
System.Drawing
Assembly Version: 4.0.0.0
Win32 Version: 4.8.4390.0 built by: NET48REL1LAST_C
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Drawing/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll
Microsoft.VisualBasic
Assembly Version: 10.0.0.0
Win32 Version: 14.8.4161.0 built by: NET48REL1
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/Microsoft.VisualBasic/v4.0_10.0.0.0__b03f5f7f11d50a3a/Microsoft.VisualBasic.dll
System.Core
Assembly Version: 4.0.0.0
Win32 Version: 4.8.4515.0 built by: NET48REL1LAST_C
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Core/v4.0_4.0.0.0__b77a5c561934e089/System.Core.dll
System.Configuration
Assembly Version: 4.0.0.0
Win32 Version: 4.8.4380.0 built by: NET48REL1LAST_B
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.8.4161.0 built by: NET48REL1
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Xml/v4.0_4.0.0.0__b77a5c561934e089/System.Xml.dll
System.Runtime.Remoting
Assembly Version: 4.0.0.0
Win32 Version: 4.8.4161.0 built by: NET48REL1
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Runtime.Remoting/v4.0_4.0.0.0__b77a5c561934e089/System.Runtime.Remoting.dll
AeroWizard
Assembly Version: 2.3.1.0
Win32 Version: 2.3.1.0
CodeBase: file:///C:/ProgramData/FFmpeg%20Batch%20AV%20Converter/AeroWizard.DLL
System.Management
Assembly Version: 4.0.0.0
Win32 Version: 4.8.4435.0 built by: NET48REL1LAST_C
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">
</system.windows.forms></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.
Image Attached Thumbnails
Hi, it looks like some incompatibility with WMI calls in new Windows Server.
You could try this version that does a light ffmpeg validation:
EDIT: Fixed error with this patched version.
Last edit: Abel 2022-06-27
Abel,
Thank You for looking at this so quickly and thank you for this software. It is a great piece of software and meets my needs very well. That Patched File worked. I can now run the jobs without the application closing unexpectedly and open the Security and Performance section to see that the FFMPEG file has the Green Checks. Also when I update the FFMPEG file with a different version, it allows me to Accept it, so that I can use that version. Going forward, will I need to keep this patched file, or is there something I will need to do as updates come down from your side? I am not sure if using a Server OS is normal for most people, but I can say it affected Server 2019 and 2022. Thank You again.
Last edit: Heinz Beckmann 2022-06-28
Hello, this fix will be available in future versions. Anyway, application is in a mature state so not big changes expected in the future. Application should be transparent to server versions, this bug was very particular, regarding a not essential system information feature.
Thank You, Abel. Keep up the good work.