Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

"Critical Error occured in WinNUT" in pre-release v2.3.8965 #167

Closed
Hedders opened this issue Jul 18, 2024 Discussed in #166 · 8 comments
Closed

"Critical Error occured in WinNUT" in pre-release v2.3.8965 #167

Hedders opened this issue Jul 18, 2024 Discussed in #166 · 8 comments
Labels
bug Something isn't working

Comments

@Hedders
Copy link

Hedders commented Jul 18, 2024

Discussed in #166

Originally posted by Hedders July 18, 2024
Hello, just installed the new v2.3.8965 and it fails to launch, displaying a broken-looking dialog with the error "Critical Error occurred in WinNUT".

I'm on Windows 11 23H2, build 22631.3880, with .NET framework 4.8.09032. The Windows event log shows event ID 1000 (Application Error), with the following diagnostic information:

Faulting application name: WinNUT-Client.exe, version: 2.3.8965.28008, time stamp: 0x66996e11
Faulting module name: KERNELBASE.dll, version: 10.0.22621.3880, time stamp: 0xee1eae1c
Exception code: 0xe0434352
Fault offset: 0x0014a782
Faulting process ID: 0x0x1D34
Faulting application start time: 0x0x1DAD9547DC0AC6E
Faulting application path: C:\Program Files (x86)\WinNUT-client\WinNUT-Client.exe
Faulting module path: C:\WINDOWS\System32\KERNELBASE.dll
Report ID: 77f6d5b7-99a6-42cd-9d82-4e7e13de4fdd
Faulting package full name:
Faulting package-relative application ID:

Immediately prior to that in the event log is a .NET Runtime Event 1026, with the following diagnostic information:

Application: WinNUT-Client.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: System.MissingMethodException
at WinNUT_Client.Controls.UPSVarGauge.set_Value1(Single)
at WinNUT_Client.WinNUT.InitializeComponent()
at WinNUT_Client.WinNUT..ctor()

Exception Info: System.InvalidOperationException
at WinNUT_Client.My.MyProject+MyForms.Create__Instance__[System.__Canon, mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089]
at WinNUT_Client.My.MyApplication.MyApplication_UnhandledException(System.Object, Microsoft.VisualBasic.ApplicationServices.UnhandledExceptionEventArgs)
at Microsoft.VisualBasic.ApplicationServices.WindowsFormsApplicationBase.raise_UnhandledException(System.Object, Microsoft.VisualBasic.ApplicationServices.UnhandledExceptionEventArgs)
at Microsoft.VisualBasic.ApplicationServices.WindowsFormsApplicationBase.OnUnhandledException(Microsoft.VisualBasic.ApplicationServices.UnhandledExceptionEventArgs)
at Microsoft.VisualBasic.ApplicationServices.WindowsFormsApplicationBase.DoApplicationModel()
at Microsoft.VisualBasic.ApplicationServices.WindowsFormsApplicationBase.Run(System.String[])
at WinNUT_Client.My.MyApplication.Main(System.String[])

Any suggestions gratefully received!

@Fr0stX76
Copy link

Same

@Fr0stX76
Copy link

The no installer works fine, si its the msi

@gbakeman
Copy link
Contributor

gbakeman commented Jul 18, 2024

Hi all,

Critical mistake on my part - I didn't test the MSI upgrade before deploying. Sorry!

Because I replaced the AGauge library in WinNUT, the new one actually has a lower version than the one that was deployed with WinNUT's version (2.3 vs 2.1.) It seems like the MSI decided it didn't need to upgrade the previous one, leaving the installation with a mismatched library (crash.) Please uninstall this version of WinNUT and reinstall from the latest pre-release currently available.

I need to work on the AGauge project a little more and rebrand the library so the installer knows to replace it next time.

@gbakeman gbakeman added the bug Something isn't working label Jul 18, 2024
@gbakeman gbakeman added this to the 2.3 Stable Release milestone Jul 18, 2024
@Hedders
Copy link
Author

Hedders commented Jul 19, 2024

Thank you for responding so swiftly!

@gbakeman
Copy link
Contributor

All,

Thanks for reporting this so quickly. A new pre-release is out, and from my own testing, it seems to be updating correctly! Please let me know if there are any further issues.

@Hedders
Copy link
Author

Hedders commented Jul 23, 2024 via email

@Hedders
Copy link
Author

Hedders commented Jul 23, 2024

Yep, can confirm all is copacetic. Thank you!

@gbakeman
Copy link
Contributor

Great, thank you for the update!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

3 participants