LabVIEW has a strict "Version order" when installing software -- if you have a newer version of the Software installed, you can not install an older version. Your installation of VAS 17.1 means that you will not be able to install CDS 2016.
You have also "crossed" the boundary between LabVIEW 2016 (which did not use NIPM to handle installation) and LabVIEW 2017 (which does). This makes the "safe, almost-guaranteed-to-work" fix more difficult. The method that I've used (too many times!) to fix this type of problem is as follows:
- Remove all LabVIEW Modules, Toolkits, and Drivers (for all versions).
- Install the oldest Version of LabVIEW that you plan to use. Install all of the Modules, Toolkits, and Drivers for that Version that you plan to use. For best results, only install one Version of LabVIEW.
- Reboot your PC.
- If you are offered Updates that have Version numbers higher than your current Version, I recommend that you do not install them. I have experience doing a "Complete Removal/Reinstall" process that I'm describing when I allowed such an update.
If NIPM has been installed on your PC (because of a LabVIEW 2017 or higher component), the Complete Removal path is more complex. I think NI may have a White Paper discussing this, and there is also a Post on this Forum that I wrote about how to safely remove LabVIEW 2018 -- I think if you search the Forum for Safely Remove LabVIEW 2018, you'll find it.
If you do choose to follow this path, when you re-install LabVIEW 2016, go ahead and specify the DCS during the initial Install step. Don't forget the Reboot when the installation finishes.
If a new Version of LabVIEW is released, and you decide to migrate all your code to the new Version, it is generally "safe" to install the new Version (and all the Modules, Toolkits, and Drivers you need) "on top of" the old Version. In some circumstances, opening the old Version will still work, but you are taking some chances.
Bob Schor
