labview .net runtime error on startup

[rich-h]

Hi.

I was trying to clean my XP (SP3) system up and uninstalled and reinstalled Labview FDS. Now Labview only momentarily starts up and then crashes.

The even viewer reports ".NET Runtime 2.0 Error".

other info:

Faulting application labview.exe, version 7.0.0.4000, stamp 3eb1302f, faulting module unknown, version 0.0.0.0, stamp 00000000, debug? 0, fault address 0x05c4bad2.

Any ideas how to get this working again?

I've reinstalled / repaired .NET 4 and tried reinstalling and repairing Labview but no joy.

I have a string of users who need this running again so any help much appreciated.

Rich.

[Norbert_B]

Rich,

.NET Framework contains the .NET 4.0 Runtime (CLR, Common Language Runtime).

From the error message, .NET CLR 2.0 is missing on the machine.

.NET CLR 2.0 is part of any .NET framework version 2.0-3.x.

hope this helps,

Norbert

EDIT: OK, a missing .NET CLR should not crash the process (should create an error dialog and shut down gracefully).

Also, does the crash occur immediatly when launching a blank LV instance, or does it only crash if you open specific VIs (e.g. by double click the VI-file in the file explorer)?

[rich-h]

Hi.

The crahs occurs pretty immediately on a blank startup - it gets as far as loading some of the background stuff in the bottom right of the start up panel and then fails, as you put it, 'gracefully'.

When I try to run a shortcut to a VI it just opens the folder where the VI is and displays that folders contents as small icons.

Will have a go with a colleague who knows more than me...

[rich-h]

Seem to have it fixed now.

Seems it wasn’t .net after all – and I spent 5 hours uninstalling all versions and then reinstalling the @##@ thing!

After all that I found it was windows had included labview and PCI_something in the DEP selection.

Reverted that to the ‘windows essentials’ only and it’s ok now.

cheers for the advice anyway - at least I know .NET is sparkling clean.