LV2009 SP1 Crashing (sometimes) on startup

[pallen]

My morning has taken an significant turn for the worse.  

It's funny how these things only seem to happen when there's a huge deadline or some other mitigating factors to the inconvenient into a disaster.

After a reboot and three startup attempts in a row, LabVIEW finally started.  But I'm not sure that I can trust it will start again.  

The instability seems to have started after I did the SP1 upgrades.  This PC (running XP SP3 on an Intel Dual Core) has Real Time and the FPGA addons. SP1 upgrades were done for these packages as well.  The latest Device Drivers have also been installed.  

The problem first appeared when I was attempting to open an RT project directly from disk a few days ago. The crash warning appeared several times in a row, and then finally one attempt was successful.  

I've attached the .txt dump that was generated this morning.  Not sure if the NI guys can find anything useful in this.  

My predicament is that I've several important installs and some frantic development to complete this week.  The time to reinstall 2009 is something I really don't have.  But if my machine suddenly becomes completely unusable while I'm at the customer's site, I'll be up the creek without a paddle.  (Or I suppose I could use my laptop as a paddle, since that's about all it would be good for at that point)  

I haven't seen any other reports like this one.  It's possible that LV is not the culprit here, and reinstalling won't remedy anything.  So I'm looking for suggestions.  

My saving grace might be my dual boot.  I do have Win7 setup in another partition, and although it's seen very little use; I've not seen this happening there.  I am concerned about suddenly jumping OSes in the middle of some very important projects however.  

Any suggestions (or perhaps shoulders to cry on) would be most welcome.    

[ceties]

I encountered same behavior twice. First time the reboot didn't fixed it so I was playing with killing different processes and restarting PC...I don't know what I did but it started to work. Few days later the same - this time the reboot fixed it. It also hanged while 'initializing plugins'. XP SP3, 2009SP1

[ST5]

I had the same message douzens of times, started in LV 8.6, but it also has it in LV2009

After that, supplementary problem was when working on an auto-run program,

Recovery interfered with the already running program.

The error appeared often when dragging a part of the block diagram,

but also without "visible" reason.

.

Message Edited by ST5 on 03-26-2010 07:18 AM

[Stephen_S.]

Hi Patrick,

It looks like various versions of this problem have been solved in various ways. I would suggest that you try repairing you installation of LabVIEW from Control Panel>>Add or Remove Programs>>National Instruments Software to see if this helps.

Other suggestions: Are any of your modules or components not activated? Others seem to have found that uninstalling unactivated components listed in the NI License Manager can get rid of similar problems. Also, do you have NI-RIO 3.4 installed, as this one will work with SP1.

If it comes down to it, LabVIEW 2009 is supported on Windows 7, so copying your VIs over to your Windows 7 partition shouldn't have an affect on them.

Regards,

Stephen S.

[pacpac]

Hi Stephen,

I'm having the same problem with LV2009. If it can help you, in my case changing the "IsFirstLaunch" entry in Labview .ini from "False" to "True" allow LV to start correctly but, after LV starts, it of-course change the value to IsFirstLaunch=False and the problem represent.

In my situation there no unactivated  installed modules and no win update nor LV updates or installations have been made. The problem simply came out without any clear reason.

I'll proceed now to uninstall-reinstall LV, hoping this will solve the problem.

Thank,

PierAlbino Colombo 

[Broken_Arrow]

I have had this problem a few times in the past, but this afternoon it started occurred every time I tried to open LabVIEW. Tried reboot. Tried ending some processes. Tried pacpac's idea using the "IsFirstLaunch"=True, to no avail.

What worked for me was: I launched MAX (thankfully that worked), then from within MAX, I launched LV 2009 (see picture).

Someone else mentioned having this issue possibly related to a VI set to Run When Opened. Earlier today, I was working with just such a VI and having to abort a lot. I have since set that VI to not run when opened. Just hoping that was it.

[yuval_yohai]

What worked for me was renaming labview.ini

Strange