drjdpowell Posted September 12, 2017 Report Posted September 12, 2017 (edited) Has anyone ever had a problem with LabVIEW crashing on start even after you reinstalled LabVIEW (and tried Windows System Restore to revert to a point before the problem happened)? I believe there must be some corrupt file somewhere; I've tried manually deleting the compiled-code cache and the LabVIEW INI file but to no effect. Can anyone think of any other file that LabVIEW might read on startup? Where does LabVIEW save the backup copies of VIs (that, after a crash, it asks you if you want to recover)? I think it could be that. Crossposted on NI.com Edited September 12, 2017 by drjdpowell Quote
PiDi Posted September 12, 2017 Report Posted September 12, 2017 (edited) Have you cleared both compiled-code caches, i.e. 1. The one in <National Instruments>\LabVIEW XXXX\VIObjCache\(...) 2. The one in <Documents>\LabVIEW Data\VIObjCache I think the recovery files are also somewhere in LabVIEW Data folder... Maybe just try to wipe this whole folder? Also: the crashes at the startup happens when LV have problems with loading project providers. Any toolkit you've installed recently? Or just go to the <LabVIEW>\resource\Framework\Providers\GProviders folder and remove it's contents to see if LV will start without them, this will narrow down the problem. Edited September 12, 2017 by PiDi 1 Quote
drjdpowell Posted September 12, 2017 Author Report Posted September 12, 2017 (edited) Thanks, I got those caches. New symptom: MAX wont start either (just hangs and the splash screen). Earlier version of LabVIEW (2015) works fine. Edited September 12, 2017 by drjdpowell Quote
drjdpowell Posted September 12, 2017 Author Report Posted September 12, 2017 On 9/12/2017 at 9:53 AM, PiDi said: I think the recovery files are also somewhere in LabVIEW Data folder... Maybe just try to wipe this whole folder? Expand Fantastic idea! That worked. LabVIEW 2017 now opens. Why was I searching through that folder for suspicious items when I could nuke the whole thing? Quote
hooovahh Posted September 12, 2017 Report Posted September 12, 2017 Glad you got it working (partially at least) my suggestion would just be to repair stuff. Yeah it takes a while to reinstall MAX, LabVIEW and all the other stuff but it has worked for me most times LabVIEW refuses to start. Quote
drjdpowell Posted September 12, 2017 Author Report Posted September 12, 2017 On 9/12/2017 at 1:28 PM, hooovahh said: Glad you got it working (partially at least) my suggestion would just be to repair stuff. Yeah it takes a while to reinstall MAX, LabVIEW and all the other stuff but it has worked for me most times LabVIEW refuses to start. Expand Sadly, NI has removed the ability for me to repair any NI installation. I’m not happy. Quote
hooovahh Posted September 12, 2017 Report Posted September 12, 2017 Oh lovely. Yeah I noticed this was removed for NXG and complained, but didn't realize this extended to current LabVIEW. Quote
chriscoxtx Posted September 13, 2017 Report Posted September 13, 2017 I'm currently in the middle of a complete reinstallation of everything. Everything. After multiple issues with 2017 crashing, and DAQ-mx not recognizing hardware (I re-installed it after installing 2017, and it was working fine for a couple months). wish I had seen this post yesterday, but c'est la vie. Quote
drjdpowell Posted March 29, 2018 Author Report Posted March 29, 2018 Arrgh! Same problem, only now nothing suggested above fixes it. Quote
gleichman Posted March 30, 2018 Report Posted March 30, 2018 I also had these same issues. Mine was due to a bad beta install and was so bad NI PM would not work which created a interesting catch-22. I finally got NI PM working and was able to uninstall everything and re-install. https://knowledge.ni.com/KnowledgeArticleDetails?id=kA00Z0000019R9WSAU Quote
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.