06-05-2023 09:10 AM
I applied this update, and successfully built an installer. Running the installer to test it on another PC has broken the ActiveX link between LabVIEW Report Generation and MS Office. Is this expected? Should I re-install MS Office to repair? In the past, having this link broken has been insiduous to repair, sometimes not successfully.
06-14-2023 02:52 PM
The support article posted worked for me when this error came up on all my installers, easy fix.
06-16-2023 08:33 AM
UPDATE:
It was necessary to have our IT re-install MS Office to fix the ActiveX links. After that, no issue.
I had concerns this would cause trouble with my customer's PCs if I deployed it remotely, so it was necessary to ship the systems here to run the new installer and test. No issues were found.
07-06-2023 12:59 PM - edited 07-06-2023 01:01 PM
I downloaded and ran the installer that is supposed to upgrade the low level packages to prevent this problem.
Unfortunately, when I re-launch LabVIEW 2013 sp1 and re-build the installer, I still get the same error when I attempt to install the built application. And yes, there is a reason that this application is built using LV 2013 SP1.
07-06-2023 01:46 PM
John, what OS are you building the installer on and what OS are you installing the installer on?
07-06-2023 03:46 PM
Thanks for asking.
I'm building in Windows 10 (in a VM), and installing to either Windows 10 or 11.
07-07-2023 08:49 AM
John, I did the following testing:
Can you look at your installer and you should see the following file in the bin directory structure and in Explorer the file properties shows the version as 23.3?, e.g.,
If the above looks correct for you, the next step might be to potentially share the installer with us to review.
07-14-2023 03:55 AM
I also have same question. My LabVIEW version is 2020 SP1. I'm building in Windows 10 Enterprise edition, and installing to Windows 10 Professional edition. I already install "NI ADE Deployment Support", but still get the same error when I attempt to install the built application.
btw, my "MetaUninstaller" version is 20.6.0.
07-14-2023 12:08 PM - edited 07-14-2023 12:21 PM
@Andromeda and @Elaine_Yang
Please try the following and post back here:
07-16-2023 10:45 PM
WesW,
Thank you very much. It now can successfully built an installer. You have solved a big trouble for me.