My main program no longer compiles/program terminates.

[Nick_S]

My main program (8.6.1 version) will no longer compile and provide the error listing.  The entire program just ends out of Labview completely.  First time it has occurred at our location in years of working with Labview.  I can't tell if it has something to do with the new laptop the program is hosted on or my code.  Any suggestions or solutions would be appreciated.

[altenbach]

You probably did not provide enough information for NI to analyze the problem.

What is your definition of "compile"? Does it crash when you press the run arrow?

Does only the VI crash or does it drag LabVIEW with it?

What is different between the old and new computer? (OS, installed toolkits, installed software, etc.).

Since it is a new computer, maybe it is a hardware problem (e.g. defective RAM, power supply, voltage regulator, etc.)

Is there an error log?

Is the crash reproducible? Does it occur at exactly the same step every time you try?

What does the program do/contain? (DAQ, third party DLLs, etc.)

[Nick_S]

Thanks altenback.

I define compiling as clicking the blackened out run arrow and waiting for the error listing to identify coding errors.

Problem example:  I'll remove a single wire on the block diagram.  I select the blackened arrow and then the Error List window pops up

without any errors listed inside.  At the same time, layered over the Error List window I get the "famous"

"Labview 8.6 Development System" window indicating a problem has been encountered and the program must close - sorry etc."

The "Send Error Report" and "Dont Send Error Report" buttons are shown. It doesn't matter which one I choose; the program exits out of my

program and drags Labview 8.6 with it so I'm back at Bill Gates big blue screen (I haven't put up any nice wallpaper yet).

This is repeatable - I've done it about 6 times in a row on the "newer" laptop (bought ~2009; WinXP Prof 2002 service pack 3, 3.5 GB RAM ) and just repeated it on the 2 older laptops (Lenovos; junk, bought ~2006; WinXP Prof 2002 service pack 3, 504 MB and 1 GB RAM).

My main program is       ~ 1.5 Mb in size and has 126 files under it.  Its not being run as a project. Dah!  May be this has something to do with it; never did before, I'm not sure.  My code communicates to 3 pieces of hardware via Agilent's USB/GPIB cable (82357A).  Those 3 pieces are an Agilent 34970A data acq system, an Agilent 6060B electronic load, and a Sorenson power supply.

Strange thing is the program runs fine at my desk computer (WinXP Prof 2002 service pack 3, 504 MB RAM) - IT department maintained.

It's something in the laptops, because they all worked, then during development they stopped.  Only thing I can point a finger at is the program

kept growing in size over the last year.  A lot of information but I can't come up with a solution.

Any ideas?

[Drewski]

Could it be as simple as a permissions issue?  Perhaps you haven't given the login you are using permission to write back to the labVIEW files or LabVIEW directory inside of the Program Files?

If you are using an Admin level login on the laptop, then as Altman suggested, you may have to use Measurement and Automation Explorer (MAX) to get a list of the installed LabVIEW drivers on the desktop and then compare them to the same drivers on the Laptop to verify that all the expected drivers are installed and all the drivers have the same versions.

Go into MAX and click on the software drop down menu to get the list.

Good Luck!