Mass compile crashes LabVIEW 2010

Before I go ahead and call the support line
Pentium 4
2.8GHZ
2GB RAM
XP 32 bit
Anyone have issues mass compiling an application code from 8.6.1 to 2010 SP1 whereby it would seem to work fine for quite awhile then crash?
I tries no cache on the VI and all other items are off.
It seems to happen even in subdirectories of the application.
I just installed 2010 SP1 and the device drivers and when I look at them in isolation they seem to be installed correctly.
I can also load the 8.6.1 application
Im just wondering if Mass Compile is running out of memory and is it known issue or am I discovering something.
I will attempt to log results on the next try.

Hey guys, this is Paul with Applications Engineering at NI.
I have reviewed your issues, asked around, and have a couple tips and questions.
First, if there is any chance you could post your project in a zipped format, then we could examine it on our end and see if we experience the same issue, which would make it easy to file a CAR on. If you are wary of posting your code publicly, you can PM me, and we can work out a way to upload it to our FTP server that only NI employees can access.
richjoh, in your posted Mass Compile screen, I see a VI being flagged as bad. When you open this VI on it's own do you experience this problem? Can you locate in that VI where it calls the NanoMsg.lvclass?
Second, to either of you, were the controls and lvclasses mentioned still referenced in your projects anywhere? Were they included in the dependencies? If not, once you restored these files into the project, find them in the
dependencies, right click them, choose "Find">"Callers". Where they still being called anywhere?
Alternative to your solutions, have you considered creating a new project and adding all of your VIs into the new project? I have seen this resolve upconverting issues in the past.
Paul Davidson
Sound and Vibration Software Staff Product Support Engineer
National Instruments

Similar Messages

Is it possible to disable the optimized compiler in LabVIEW 2010

Hello,
I have a project that take 3 minutes in LabVIEW 8.6 to build and now with LabVIEW 2010 it take 10.5 minutes. 3x more longer.
In fact my project as 61 .lvproj for a total of 4300 vi's that take 1 hour to build. If I interpolate, the entire build process will take 3 hours in LabVIEW 2010. This is not acceptable
I know that the new compiler optimize the code for better performance, but if I don't need better performance.
Is it possible to disable the optimized compiler in LabVIEW 2010 with an INI key in LabVIEW.ini.
Dany Allard
Dany Allard
Solved!
Go to Solution.

Jarrod S. wrote:
One Application Builder setting you might try out to make builds go much more quickly is the Remove Unused Members of Project Libraries checkbox and the Modify Project Library File after Removi....
This can drastically cut down the build times. Note, however, that this option does not work well if your application will load external plug-in VIs when it runs, because the libraries of those plug-in VIs may conflict with the modified libraries in the executable file. If you don't have a plug-in architecture, this will not affect you.
The "Remove unused members of project libraries" was already selected but not the "Modify project library file after removing unused members" and selecting this cut the build time from 10.5 min to 4 min.
Thank you Jarrod for this tips
Dany
Dany Allard

Problems with mass compiling for LabVIEW 6.0.2

When mass compiling the LabVIEW folder after installing 6.0.2, I get a Log file telling me "Bad VI" for 8866 vi:s. Have looked specifically at two of them, and the broken arrows are fixed by pressing and clicking the broken arrow. Somehow I don't feel like doing this for 8866 vi:s.
What is wrong, and how do I fix it?
Attaching the Log.
//Martin
Attachments:
MassCompileLog ‏1263 KB

Yes, it definitely appears as though you need to reinstall NI-DAQ. You can receive this error when the VIs which are being mass compiled depend upon other VIs which are either not present or have been incorrectly updated. Make sure that you have installed NI-DAQ support for your new version of LabVIEW. This is separate from installed NI-DAQ by itself. You must install the LabVIEW support files also. You can get these off of NI's website.
Also, if you did a complete install of LabVIEW, you may have installed a newer version of NI-DAQ without realizing it. This could cause a problem if there are two versions of NI-DAQ on your computer. Make sure you only have one version.
J.R. Allen

"red X" error during mass-compiling installing labview upgrade 6.0.2

I always get a "red X" error during installation of the LabVIEW 6.0.2 upgrade.
The mass compiling always fails.
The environnement is an italian version of W98.
Salvatore Randazzo
[email protected]

I would try compiling one directory or .llb at a time instead. See if you can isolate the problem.

Deleting broken wires crashes Labview 2010

Hi
I am down to earth after
enjoying all the nice features of LV 2010.
I randomly encounter
hour-glass hang-up when I try to delete broken wires. This is really
unpredictable as far as I have watched. I t happens if click on a broken with
the mouse or when I select a couple of those. It does not happen, if I use
ctrl-b.
When you try to delete it,
the hour glass comes up and the window is no longer refreshed.
I use the task-manger to
kill LV after
that a wild hard disk action starts, whoever initiates that ??
After LV-restart I usually
can recover a lot, but this make RAEL work almost impossible.
I a running an English LV
2010f2 on a German WinXP professional.
And Please, please patch
this as soon as possible.
Gabi
7.1 -- 2013
CLA

Hi Gabi,
I'm glad to hear that you are enjoying LabVIEW 2010! Can i ask what is the specifiation of the computer you are using it on?
This is because it might be that your computer doesn't have enough memory for this program.
Also there is a patch for LabVIEW 2010, in this link.
Hope this helps!
John McLaughlin
Insides Sales Engineer Team Leader
National Instruments UK & Ireland

Internet Toolkit for G5.0 crashes Labview 8.2 during Mass Compile

I have just received my Labview 8.2 update and installed it my system along with all my toolkits. When I tried to Mass Compile Labview 8.2 directory I found that it would crash labview consistantly as shown in the attached image.
I traced this to the vi's supplied with the Internet Toolkit for G5.0.
The workaround is ...
1. Re-installed the Internet Toolkit for G5.0 into Labview 8.2
2. Mass Compiled ...\project\_config\authcfg.llb using Labview 8.0
3. Mass Compiled ...\project\_config\authcfg.llb using Labview 8.2
and there wasn't any more Labview 8.2 crashes during mass compile. As Labview 8.0 was able to mass compile the internet toolkit vi's without crashing I am suspicious that Labview 8.2 might not be completely compatible with Labview 5.0.
I posted this just in case anyone else sees a similiar issue.
David
Attachments:
Labview 8.2 Mass Compile Crash with Internet Toolkit.png ‏34 KB

David,
I was able to reproduce the crash mass compiling authcfg.llb or just trying to open the VI named 'Directory Configuration'. That code is saved in LabVIEW 5.0.1 and must have something that LabVIEW 8.2 chokes on, I'll have to get someone to investigate it. Your workaround of saving that .llb or even that one VI in 8.0 first (or probably even 7.x) is the only way I see around it with 8.2.
I do want to mention that in Q1 2004 we released version 6.0 of the Internet Toolkit and it does not exhibit this behavior. So the official solution for this crash is to upgrade to the latest Internet Toolkit.
Kennon

Simple LV 8.6 vi crashes LV 2010

Hi,
I've a very simple LV 8.6 .vi that causes LV 2010 to crash. On next restart no crash investigation window appears.
It has no dependencies.
Mass compiled in LV 8.6 ok.
Attempting Mass compile in LV 2010 also causes crash.
Does anyone see similar or can explain this?
Thanks,
ds1
Attachments:
BuildArray.vi ‏7 KB

Looks like this is a known bug:
242603 LabVIEW 2010 crashes on compile if you have a divide primitive with dominator less than 1 wired to the for loop count terminal (N)
The 0.01 denominator triggers the bug. It is present in LV 2010, I've checked with SP1 (10.01) and appears to be fixed. (I'm not sure what 10.0f4 version is)
The purpose of code is not really the issue, sure it can easily be implemented more effectively/efficiently etc but it it works and in 8.X etc. SP1 will now have to be rolled out to many users (which is a pain)
It is really disheartening when existing code cannot be relied upon with newer versions of LabVIEW and gives us less confidence in this constant upgrading.

LabView 2010 application runs twice as slow in Windows 7

When our company mandated the replacement of Windows XP PC's, my LabView test application that was compiled in LabView 2010 runs over twice as slow on a Fujitsu Esprimo E710E86+ machine. The application uses a GPIB USB - HS adapter to control an HP 4285 Impedance analyzer whose signals are switched to it using two (2) SCXI chassis that contains five (5) SCXI-1193 switch modules. This chassis uses the USB-1359 communicator.
On the Windows XP machine that is being replaced (a Dell Optiplex 960), a typical set of measurements takes around 40 seconds to complete. The new Windows 7 machine takes about 100 seconds to do the same set of measurements. Has anyone noted this increase in test time???
Thank you.
Rod Johnson
Test Engineering
FujiFilm SonoSite Inc.

Hello Rod,
Before updating to LV 2013 I'd recommend isolating what components are causing the slowdown or at least trying to eliminate some of the variables - right now there's a new PC, new OS, new physical connections, and perhaps even new hardware, so figuring out which of these is causing the slowdown should be the first order of business. I've seen issues simlar because USB devices were switched around to different (built-in) ports on the same machine.
A few things to check:
-What does this application do? Are you doing any intensive data manipulation or is this mostly a call-and-response type application?
-What does your system resource utilization look like on the two machines? In either case, are you using more or less RAM on one machine or railing one or more CPUs?
-Do you see the same sort of performance hit on a Windows 7 installation on an Optiplex or similar machine?
-Did you change drivers when you upgraded to Windows 7?
-What NI driver version(s) are/were you using?
-Does this application log data data to disk or perform any network operations?
-Have you attempted recompiling the 2010 executable on "new" hardware? The LabVIEW compiler will optimize for the platform it is being built on and it seems highly likely that the Dell and Fujitsu machines have different processors. As a note I've never seen recompiling in this fashion result in a 100%+ speedup.
-Have you taken a look at the machine's I/O traces to see how long the acquisition itself takes?
-Have you tried moving the USB connections to different ports? Most desktop PCs nowadays have one hub on the front and one on the back of the machine, although I'm not familiar with Fujitsu desktops. If the adapters you are using or anything else on the machine is forcing a USB 2.0/3.0 port to 1.0 or something this could be a factor.
Regards,
Tom L.

Difference between Mass compile in Project %26 in LabviewTools Advanced mass Compile

what is the differece betwen the two, Mass Compile option in a Project(LVPROJ) and  LabviewTools Advanced mass Compile
The Issue is if I do the Mass compile thr' the Project I do not get an Error.
But if I mass compile thr' labview >> tools>> adv. Settings>>mass compile it shows BAD VI ??

My Project folder is clear of   Erorr VIs -->> there are none
inspite of that the difference exist.
I am using classes in my Project &   may be the   class contains information abt the VIs (the broken ones)
My Class is added ina llb file which is part of my project...
In runtine I get issues with the project.

LabVIEW crashes during mass compilation every time

Hello All
I have installed a new LabVIEW 7.1 from February on Win XP.
Every time when I try to mass compile LabVIEW, after few files it crashes, and only one thing I can do is to send a report to Microsoft.
It looks like it crashes in a moment when it can not find a subvi in the directory structure.
What is wrong with it?
Thanks in advance.
Pawel

I hope you are not trying to mass compile the entire LabVIEW directory. I will definately choke on several of the files it will find. If you have upgraded to 7.1.1, you should mass compile the vi.lib, instr.lib, user.lib and examples directories.
You could also have an error with the Paths settings. If it is searching an invalid path to find a subvi, that might cause the problem.
I suggest that you start small and try a single subdirectory like user.lib, then move on to instr.lib, then examples.
Michael Munroe, ABCDEF
Certified LabVIEW Developer, MCP
Find and fix bad VI Properties with Property Inspector

LV 8.6 will Not Compile in LV 2010 - Labview 10.0 Development System Has Encountered a Problem and Needs to Close

I submitted this support request to NI on 8/12/2010.
When I compile my LV 8.6 app in LV2010 I get this error:
"LabVIEW 10.0 Development System has encountered a problem and needs to close. We are sorry for the inconvenience."
I was told to do a "Mass Compile" of my LV 8.6 app in LV2010...this failed too.
I was then told to go to each and every vi and "Mass Compile" individually...after about the 50th vi this got old quickly...and it still didn't compile. I then sent NI tech support "my code". The good news is my LV 8.6 app didn't compile with LV2010 @ NI.
My LV 8.6 app compiles and runs great in LV 8.6. I don't want to be left behind with the newer upgrades and I want to move to LV2010. I have lots of LV8.6 code to maintain and I really don't have the time to debug all of my apps.
I was told this will be looked @ in LV2010 SP1.
One note...back up your LV8.6 data before you move to LV2010. Once your LV8.6 code is compiled in LV2010 you will not be able to go back to LV8.6.
I restored all of my LV8.6 code and I'm back working with LV8.6.
It's a tough call, do I stay in LV8.6 and get left behind?
Do I bite the bullet and try to debug this mess in LV2010?
I was told the compiler is completely different in LV2010. That's great, but one reason I have NI Maintenance Agreement is to keep updated with the latest software. I can't afford to re-compile LV code every few years. Like most people, maintaining my Apps with customer's revisions, and modifications is enough work. I don't want more work!
I was told LV2010 SP1 would likely appear in May or June of 2011. I'd hate to break out my old Turbo Pascal apps again...but hey...they still work! My NI maintenance agreement is due this month too, I guess I'll pay NI one more year, and see if they come up with a solution. But if NI doesn't fix this LV8.6 compile in LV2010 problem...I don't see any value staying current with LV software.
I found another Bug with LV2010...you are going to love this one!
There is a new "LV Update Service". Perfect! I like updating my LV software when new patches are available. When I click "update" the update spins over and over "Checking for New Version". I have let it run ALL day with no results...just sits and spins over and over.
OK, I know give NI a break! Yes, LV2010 has a new compiler...and Yes, I will renew my NI maintenance agreement. I just want NI to know failing to compile just one LV8.6 app in LV2010 is not a good idea for customer relations.
Thanks,
Doug

For your update service problem
Unable to Update Current Version of NI Update Service
Why am I Unable to Update My Version of NI Update Service in Windows Vista or Windows 7?

Labview 2010 crashes XP while looking for webserver

Hi,
I am using a Windows 7 laptop with LV 2010 to compile my 32-bit executable. I've copied it to my target Windows XP, SP3 computer and after running it for a short while it rebooted the computer automatically (I believe the reboot was caused by a BSOD).
I've gone into the Windows Event Viewer and there is an event that says "Labview information: Error: 404 "Not Found" for "national instruments/ni-rpc/interface/eadfc80d-1e6f-425b-8986-12ccef98f646/ncalrpc", file "c:/program files/national instruments/shared/ni webserver/www/national instruments/ni-rpc/interface/eadfc80d-1e6f-425b-8986-12ccef98f646/ncalrpc": Can't access URL ."
I'm attaching a jpg of the Event in case I typed it incorrectly. There is another post that mentions this error but there is no resolution and the discussion went in a different direction: http://forums.ni.com/t5/LabVIEW/LabVIEW-2010-unstable-on-Windows-7/m-p/1247366/highlight/true
Neither my Win 7 development laptop or my target Win XP system have this www folder.
Has anyone seen this before or know the cause? Thanks.
Steve
Attachments:
Event Viewer small.jpg ‏69 KB

Altenbach,
Thanks for the quick reply.
Yes, the time stamp of this error coincides with the crash. I guess I assumed that it caused the crash because I see about 20-25 instances of it in the Event Viewer. Immediately before these errors appear there are two instances of the NI Configuration Manager with the Description saying "Opening configuration database".
This only happened on time and I have not been able to reproduce it again.
I'll need to explain to my customer why this Error has appeared so many times in the Event Viewer, and also how I can get it to not happen again. Do you have any suggestions? Once I isolate this error and prevent it from happening again then I can monitor the computer for future crashes.
Thanks.
Steve

Exe compiled in LV 2010 crash - Since installing LV 2012 SP1 and 2013

Exe compiled in LV 2010 crash - Since installing LV 2012 SP1 and 2013
Double-click on exe icons (LV apps written in 2010), the application icon appears on taskbar then disappears (program crashes).
I have tried re-installing the exe's but doesn't fix. Is there an issue with the new LV RTE's?
Any suggestions for fix???

battler,
Have you tried making your exe into a debuggable exe? You can do this through your project build specification Advanced>>Enable Debugging. Make sure you check the box for Wait for Debugger. This means when you launch your exe you can connect to it from LabVIEW and see your block diagrams, use highlight execution, probles etc. It is quite possible that you are running into an error case while your program is loading and it is exiting.
Regards,
Jeff Peacock
Product Support Engineer | LabVIEW R&D | National Instruments

Application crashes in Windows 7 64bit made in Labview 2010 sp1 f2 with Fault module name%3A lvrt.dll%2C version 10.0.0.4033 and exception code c0000005

I build an application exe and then its installer along with run time environment.
The installers instals the application correctly but when I try to execute the application, I get an error that application has crashed and Windows must close it down or search for solutions online with this additional information for the crash.
Problem signature:
Problem Event Name: APPCRASH
Application Name: AGMS.exe
Application Version: 1.3.0.0
Application Timestamp: 4c24e8f5
Fault Module Name: lvrt.dll
Fault Module Version: 10.0.0.4033
Fault Module Timestamp: 4c9273f4
Exception Code: c0000005
Exception Offset: 00005310
OS Version: 6.1.7601.2.1.0.256.1
Locale ID: 1033
Additional Information 1: 0a9e
Additional Information 2: 0a9e372d3b4ad19135b953a78882e789
Additional Information 3: 0a9e
Additional Information 4: 0a9e372d3b4ad19135b953a78882e789
Read our privacy statement online:
http://go.microsoft.com/fwlink/?linkid=104288&clcid=0x0409
If the online privacy statement is not available, please read our privacy statement offline:
C:\Windows\system32\en-US\erofflps.txt
I am using labview 2010 sp1 32 bit on a 64-bit machine, with the following specs
Operating System: Windows 7 Home Premium 64-bit (6.1, Build 7601) Service Pack 1 (7601.win7sp1_gdr.130318-1533)
Language: English (Regional Setting: English)
System Manufacturer: Dell Inc.
System Model: Dell System XPS L502X
BIOS: Default System BIOS
Processor: Intel(R) Core(TM) i7-2630QM CPU @ 2.00GHz (8 CPUs), ~2.0GHz
Memory: 8192MB RAM
Available OS Memory: 8106MB RAM
Page File: 3457MB used, 12753MB available
Windows Dir: C:\Windows
DirectX Version: DirectX 11
DX Setup Parameters: Not found
User DPI Setting: Using System DPI
System DPI Setting: 96 DPI (100 percent)
DWM DPI Scaling: Disabled
DxDiag Version: 6.01.7601.17514 32bit Unicode
The exe /application runs fine on my PC but when I try to run it on another PC it crashes. The other PC has similar specs as given below
Operating System: Windows 7 Ultimate 64-bit (6.1, Build 7601) Service Pack 1 (7601.win7sp1_gdr.140303-2144)
Language: English (Regional Setting: English)
System Manufacturer: LENOVO
System Model: HuronRiver Platform
BIOS: Default System BIOS
Processor: Intel(R) Core(TM) i3-2330M CPU @ 2.20GHz (4 CPUs), ~2.2GHz
Memory: 4096MB RAM
Available OS Memory: 4010MB RAM
Page File: 1359MB used, 6658MB available
Windows Dir: C:\Windows
DirectX Version: DirectX 11
DX Setup Parameters: Not found
User DPI Setting: Using System DPI
System DPI Setting: 96 DPI (100 percent)
DWM DPI Scaling: Disabled
DxDiag Version: 6.01.7601.17514 32bit Unicode
I tried another machine, 64 bit of course, as I want to deploy my application on a 64bit PC, but still got the same problem.
This other machine was from HP, iCore 3 (4 CPUs) 2.2GHz, 4GB RAM and running Windows Professional 64 bit.
Now as I see it, it could be a Run-time environment mis-match error.
For this I tried installing a 64 bit LVRTE from NI, but still no sucess.
I checked DEP, for all 3 PCs and it was set to the following
Turn on DEP for essential Windows programs and services only (first option).
I am confused. I can not find a solution for this and it is really frustrating.

But I am assuming that when I make the installer, the 32-bit Run Time Engine is appened with the installer, as show below
Since from the picture you can see its including the support installers from '\Program Files (x86)\'
The application runs queries to fetch data from database in SQL server 2008, and for that I am using a Microsoft SQL Native Client 2008 R2 64 bit ( this is the only version that installs on either PC, even the one on which I developed my LV Application).
I am not using any driver, only toolkits for reports - and for that I un-checked the "Remove unused polymorphic VI instances" when making the executable, otherwise LV throws up an exception that share variable are not being included.
Yes I did reboot every time after I ran the installation.
Still getting the same error.

LabVIEW classes and mass compile

Just wondering if anyone out there has found any problems mass compiling LabVIEW classes, as I am having what appears to be totally un-resolvable issues - I get a list of VIs that either say BadsubVI or BadVI all of which I have verified are error free.
The only thing I can round it down to is the use of the lvclasses, and in particular the fact that I'm making extensive use of the inheritance functionality, and also a few override vi's.
It wouldn't be such an issue except that I'm calling some of these vi's from TestStand, and am unable to get a deployment to work without a successful mass compile.
Appreciate any responses,
David Clark
CLA | CTA
CLA Design Ltd
Hampshire, England

I'm not sure if it's the same problem but I had a vi that would compile into an unrunable exe. I found the problem by mass compiling the project, which came up with a bad vi and bad subvi's that used that vi. Turns out my problem was that I had two classes with the same name (even though they were in separate lvlibs). And renaming one corrected my problem. LabVIEW 8.5 gives a warning and renames the compiled vi's (so if you could try 8.5, that might help you find the problem quicker assuming it's related). It seems to me that the name spaces provided by lvlibs go away when compiled into an exe or by the mass compiler (It may just affect lvlclasses).
Matt

Mass compile crashes LabVIEW 2010

Similar Messages

Maybe you are looking for