05-09-2019 06:48 AM - edited 05-09-2019 06:49 AM
I just downloaded the offline version of the installer for DAQExpress 3.2.0. While installing, I got an error saying that a package needs internet access. NI Package Manager does not work for me due to IT blocking it from getting updates. So the offline is really the only way for me to go. So this is something that needs fixed.
05-09-2019 03:48 PM
Hi crossrulz,
Thank you for bringing this to our attention. I have passed this information along to our downloads team. I hoping to have an update for you soon.
05-14-2019 09:39 AM - edited 05-14-2019 09:41 AM
05-15-2019 06:48 AM
@Mackenzie8907 wrote:
Can you visit the download page again and click the "Individual Offline Installers" link below the Download button?
I did do that. It started the install, but some package inside there needed online access in order to install. I'm guessing a dependency package was missed when building the offline version.
05-15-2019 02:16 PM
The error string "Please check your Internet connection and try again" is an unfortunate default string name in this case. It's not actually trying to access the internet, and is just encountering an error when installing the package. You should be able to open up the logs for that installation to determine what the problem was during installation. The log location is listed here ("C:\Users\<Windows Username>\AppData\Local\National Instruments\NI Package Manager\logs"). We're specifically going to be interested in the errorlog.txt as it usually contains the high level error that was encountered. If we determine that the error occurred inside of an MSI, we'll need to enable MSI logging and try running the installation again. That process is also included in that KB.
Also, just for future reference, if you run into issues while using NIPM, you can post to the NI Package Manager forum. I monitor that forum pretty closely and can help troubleshoot issues like this.
05-21-2019 10:41 AM
So I retried the installer I had previous downloaded and it worked this time. The only difference I can come up with is this time I made sure to run the installer as an administrator (right-click -> Run as Administrator). So all is fine after all. I probably just ran into an IT issue.