LabVIEW 7.1 used to run fine, suddenly stops on the LabVIEW splash screen?

[wrath_of_con]

When trying to start LabVIEW 7.1, the program stops loading with the LabVIEW splashscreen visible. In particular, the "Exporting..." message is shown at the bottom right when the loading stops and the program stops responding.

Any ideas? I tried to Repair from the Add/Remove Programs dialog. It worked for awhile, now I have the same problem and Repair doesnt seem to fix it any longer.

- Thanks in advance.

[KileenC]

Hi,

LabVIEW will stop loading at the splash screen if there is an incorrect setting in the LabVIEW.ini file located in your C:\Program Files\National Instruments\LabVIEW x directory. The LabVIEW.ini file contains many of the LabVIEW settings and preferences and is automatically written to when LabVIEW runs.

My suspicion as to why LabVIEW is crashing at the Server: Exported VIs... message is because the last time LabVIEW was running, the option to select the list of Exported VIs in Tools >> Options >> VI Server: Exported VIs was changed to a setting that LabVIEW did not agree with. Go ahead and browse to the LabVIEW.ini file. Probably towards the bottom of that file, you'll see the key "server.vi.access". By default, this key has the setting "serve
r.vi.access="+*". You can try changing this setting back to its default value or just remove that line entirely. Once the LabVIEW.ini file is changed, then try relaunching LabVIEW. LabVIEW should hopefully work at this point.

Note that editing the LabVIEW.ini file is only recommended for advanced users or to users in situations where LabVIEW is not launching correctly. Editing the LabVIEW.ini file without knowing the proper keys/values may cause LabVIEW to crash. However, for information regarding some of the other LabVIEW.ini file settings, you can refer to Brian Renken's LabVIEW page.

Have fun and be careful! 🙂

Kileen C.
Applications Engineer
National Instruments

[wrath_of_con]

Kileen,

Thank you for the information!

Since I posted my question LabVIEW started cooperating again - sometimes working, sometimes not-working really concerns me.

I do appreciate your information and will try the solution should the loading problem occur again. And also thank you for the "Brian Renken" information page.

Sincerely,

Conrad

[wrath_of_con]

Kileen,

Interesting thing... There is no "Server.vi..." key in my LabVIEW.ini file. If I should have it (LV 7.1 on a Windows XP machine), then I wonder what happened.

I will check the Preferences | Vi Server dialog next.

Thanks again for your assistance.

- Conrad

[KileenC]

Hi Conrad,

Don't worry if you're missing particular key values. The key values are added to the LabVIEW.ini file as LabVIEW is used.

For example, you can even delete the LabVIEW.ini file that you have currently (or just rename it to something like LabVIEW.ini.bak temporarily so LabVIEW doesn't recognize it). Then, relaunch LabVIEW. You should get a pop-up dialog from LabVIEW that asks if you are a new user to LabVIEW. LabVIEW now has NO recollection of ever having been run on your computer. It's as if you are running LabVIEW from scratch. Once you start using LabVIEW, you will see a new LabVIEW.ini file written to the Program Files/National Instruments/LabVIEW x.x directory. Interesting, eh? 🙂

Therefore
, if you want to just go back to the default installation settings of LabVIEW, go ahead and delete or rename the LabVIEW.ini file.

Have fun!

Kileen C.
Applications Engineer
National Instruments

NI Week 2004 is here!!

[wrath_of_con]

Thank you Kileen.

On a side note, I made it up to Texas day at NIWeek and the sessions were quite informative.

- Conrad

[KileenC]

Heh, awesome!! I actually had a little floor demo with some of our new USB DAQ products that were recently released at NI Week. I'm glad you enjoyed the conference and hope you got a chance to check out Austin too! 😃

Kileen C.
NI