libraries not loading into 2018 LabVIEW

[Gearmiester]

For some reason after upgrading to LabVIEW 2018 from 2017 the libraries are not loading in the project, however, they do load in a new vi not tied to the project. what step did i miss and how do I fix this?

[Bob_Schor]

How did you do this "upgrading"?  Did you install an "update"?   Or did you download a full LabVIEW 2018 Installer?

When you install a Version of LabVIEW, it has default locations where it puts its own Library.  You might have installed a LabVIEW update without installing its support files.  Did you install 32-bit or 64-bit LabVIEW?  There's a lot we don't know about what you did ...

Bob Schor

[Gearmiester]

Bob~

Thanks for the reply. So this has escalated to a service ticket and i have spent all this week woring on the problems. to answer your questions, I have installed the 2018 developer suite, mathcad, fpga, c-rio runtime, all drivers, and softmotion modules. also installed all my required 3rd party libraries through the VI Package manager. i have to run both 32 and 64 bit versins for what I am doing until i upgrade to a 64 bit c-RIO. but even with that I have to run 32 bit programming for the SoftMotion program to run a hydraulic pump and controls.

now up to the latest and what NI ream is still helping me with is this:

I can load up my LabVIEW project in 2018 no that i have moved and copied user and vilib to a folder called Target. I have corrected all conflicts and now everything loads correctly except for the fact i have no visible function or program blocks in the working part of the project. Also I am missing one vi when i load vi's that call for an fpga close vi. i actually have that vi available but i cannot access it due to the first problem. Here are some screenshots of what i am experiencing.

one other thing that you will notice is that I have no call for the libraries.

[Gearmiester]

Sorry for the double post but just as I finished this first one I received this from the support ni team.

"Hi Stephen,
 
Thanks for the screenshots. I also tried finding the Library Directory selection on my computer and saw the same behavior as you did. It looks like our documentation is outdated, so I'll work on getting that fixed. Apologies that it was misleading!
 
In general LabVIEW 2018, it looks like we're still missing some 2018 modules (the functions that appear as gray question marks). From what I can see so far, here is what's missing and what we can do to solve it:
 
FPGA Module
Download 2018 version here: http://www.ni.com/download/labview-fpga-module-2018/7351/en/
 
Robotics Module
Download 2018 version here: http://www.ni.com/download/labview-robotics-module-2018/7403/en/
 
C Generator
2017 is the latest version. Repair the software to see if you can use it with 2018.
 
Embedded Module for ARM Microcontrollers
2012 is the latest version. Repair the software to see if you can use it with 2018. Do you need this and the C Generator for your current project? If not, I wouldn't worry about these.
 
Regarding the error with the Close FPGA VI Reference VI in your specific project, can you add the Close FPGA VI Reference VI to a blank project in LabVIEW 2018, and then copy and paste it into your current VI?
 
As for the functions not showing up at all in your project, make sure that you are opening your project in the same bitness of LabVIEW 2018 as you developed in LabVIEW 2017 (i.e. if you developed in 32-bit, open in 32-bit). Does this change anything? If not, we should try a mass compile of your project. This will make sure that all subVIs exist and relink them to the main VI, update the VIs to the current LabVIEW version, and report any corrupted VIs. Here are some instructions on how to do this, as well as additional information on what mass compiling does:
https://knowledge.ni.com/KnowledgeArticleDetails?id=kA00Z000000P9BESA0
 
I hope this is helpful! Let me know what your results are."

I will be working on this next.

[Gearmiester · Accepted solution]

resolved - here was the solution

OK, so I have double checked and reinstalled all drivers. I found an odd thing when I opened up the 64 bit side of the program…I didn’t have any of the issues that I am having in the 32 bit program. (I have to run two different versions due to restrictions with the c-RIO 9023 controller – 32 bit operating system; while the HMI runs 64 bit operating system and I need to utilize the extra memory due to latency in a 32 bit system) anyway long story short, when I opened up the VI Package Manager app I found that the 2018 32 bit program was not on the list. I scratched my head because I know I have it installed. Went back to the 2018 23 bit folder in the Programs (x86) folder and found that I had changed the names of the LabVIEW 2018 exe and ini files. I renamed them back to the original and viola the issues are resolved.

The only reason I renamed the exe and ini files in the first place is due to the fact that I always have issue trying to open the .lvproj from the file location because for some reason it will not open the different bit versions (32 or 64 – it’s only one version tied to both projects) and I believe that this has to do with the fact that the exe and ini files in both versions have the same name. I had brought this up before but have had to use the work around by opening up the correct version of LabVIEW first then opening the correct project.

So issue has resolved itself by me undoing my error.