Application builder closes labview

[NIDave]

Doug,

Sorry for the delay, I was off at all day training.

1.  you're correct, I have LabVIEW 8.01 installed and now with DAQ mx 8.3 I no longer get the NI-PAL errors on boot.

2.  In license manager I have the full development system with mathscript along with app builder, both with green boxes.

3.  I have been creating just VIs at this point and selecting Tools>Build Application, that causes all LabVIEW programs to be released from memory and closed.  (I dont do the project because I'm not too fond of it yet and I was mid project during the change to 8.0)  As for the failure log, the last one I have is form mid July, before this problem surfaced.

I did add your text to the LabVIEW.ini file, Ill see if that does anything next time I crash it.

Now the awkward twist.  When I uninstall DAQ mx I can build applications with no problem.  Fortunately the most crucial application I'm working on makes calls to my TCP/IP hardware server to do anything hardware related so I dont need DAQ mx right this minute.  However I will need it soon.

To make it even more awkward... my NI MAX gives me an error now.  COuld that be related to having DAQ mx not installed.  Its a "MAX database connection error"  and reads, "There was a problem connecting to the database.  Please restart your computer and contact national Instruments if the problem persists"  This is a new problem for me.  Who knows but after all the changing NI products I lost all my hardware profiles in MAX.  I really need to add these ASAP so I can get a system up and running again.

Now the good news.  My SSP copy of 8.2 showed up yesterday.  (Somehow mine always get lost in the mail or something)  Im going to install that and hope that solves everything.  I'll keep you posted.

Any suggestions on the other issue with MAX? 

Thanks,

Dave

[Doug M]

Dave,

The MAX database error you are seeing is most likely caused by a firewall issue.  I would try first to disable anything like the Windows firewall or other software firewalls, anti-spyware utilities, that might be blocking any NI services.  If that solves the problem you can re-enable the firewalls and add the NI services to the exceptions list.  See the following Knowledgebase entry. 

As far as using the project, you are actually now required to have your VIs in a project in order to build an executable.  If you weren't experiencing the problem of LabVIEW shutting down, you would actually see a dialog that told you to add your VI to a project in order to build an application, so essentially you would be following the step I outlined.  You may try creating a project and adding your VI to the project, then building the application, to see if that works, but I'm guessing that will give you the same problems, but try it anyway.  I also wonder if the MAX issue is related to this.

Installing LV 8.2 is definitely a good idea, though you'll have to modify the install on your drivers to add support for LV 8.2.  Let me know how it goes.