LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Labview NXG 4.0 dies silently

Hi,

 

I've been having problems with Labview NXG 4.0.  It starts, the splash screen shows, then it dies without a visible error message.  When I looked under User/Appdata/Local/......Labview NXG 4.0 I find the following error log.  I am unable to find any component with version "8.1.0+116".  Anyone know what the problem could be?  I really have no ambition to reinstall windows...

 

 

Internal error from LabVIEW NXG
Message:
Unhandled Task Exception

Error message:
Invalid version: 8.1.0+116
Exception:
ArgumentException
Suggestion:
Contact National Instruments to report this error
Stack trace:
at NationalInstruments.PackageManagement.PackageVersion..ctor(String version)
at NationalInstruments.PackageManagement.Package.Builder.WithPackageVersion(String packageVersion)
at NationalInstruments.PackageManagement.PackageConverter.ToPackage(PackageMetadata packageMetadata)
at System.Linq.Enumerable.WhereSelectListIterator`2.MoveNext()
at System.Collections.Generic.List`1..ctor(IEnumerable`1 collection)
at System.Linq.Enumerable.ToList[TSource](IEnumerable`1 source)
at NationalInstruments.Restricted.PackageManagement.PackageManagerCoreApiWrapper.<QueryInstalledPackagesAsync>d__8.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at NationalInstruments.PackageManagement.PackageManagerWrapper.<QueryInstalledPackagesWithRetryAsync>d__18.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at NationalInstruments.PackageManagement.PackageManagerWrapper.<RetrieveAllInstalledPackagesAsync>d__17.MoveNext()

0 Kudos
Message 1 of 6
(3,648 Views)

Oh, if only it were so ...

 

Bob "Still using LabVIEW" Schor

Message 2 of 6
(3,591 Views)

Hi Albert.lederer,

 

Thanks for the error message. The error doesn't tell what package has an issue. Whatever the 8.1.x version package is, it might be an unreleased package and is causing problems. I would check NI Package Manager and see if any 8.1.x version packages are installed.

 

To do that,  open NIPM, open the INSTALLED tab, hover over your product, click the Gear and select show Full version numbers.

https://forums.ni.com/t5/LabVIEW/Upgrade-the-package-manager-upgrader/m-p/3911246/highlight/true#M11...

 

Thanks,

Frank

0 Kudos
Message 3 of 6
(3,477 Views)

Hi Frank,

 

thanks for the information.  I tried finding out which package that had the associated version number, but I couldn't find anything.  I ended up searching the registry to for multiple combinations of that version number but again, I couldn't find anything.  I ended up wiping the PC and reinstalling everything, which is why I hadn't replied to the message (I wasn't being rude 🙂 ).  That did solve the problem.  That PC did see every NXG version at some point (not all at the same time) so it might be some leftover from a previous version that was not cleanly uninstalled.  Who knows...

0 Kudos
Message 4 of 6
(3,403 Views)

Hi Albert,

 

Not a problem. Happy to hear that is it working. Sorry that you had to reformat the machine...

 

Feel free to post anything else that you find or if you have any feedback on 4.0. Happy NXG 4.0'ing!

 

Thanks,

Frank

0 Kudos
Message 5 of 6
(3,382 Views)

I know this issue has been resolved for a few months, but I recently ran into the same exact crash and error message and found the culprit. I had VeriStand installed on the same PC and I had installed a VeriStand custom device called VeriStand Steps for Teststand which was version 8.1.0+116. After removing the custom device, LabVIEW NXG stopped crashing.

 

There's a bug in LabVIEW NXG where if you have packages installed in NI Package Manager that use a version convention +### instead of +f###, it will cause this crash. NI uses +f### for any of their official packages, so if there is something that using a different version convention, it is likely not an official NI package, such a custom device installed from the VeriStand Add-ons Github.

 

-Jordan

Message 6 of 6
(3,229 Views)