05-27-2023 03:27 AM
Hello! I need to build an exe file using Labview 2022. The problem is that build fails with error 1502 which occurred at AB_Source_VI.lvclass:Close_Reference.vi -> AB_Build.lvclass:Save.vi. The error message gave me the possible reason, so I opened the vi of the following directory.
C:\Program Files\National Instruments\LabVIEW 2022\vi.lib\addons\_office\excel.llb\Excel Find and Replace (num)
It turns out the vi is broken (like the picture below).
The program I made should open the Excel template and save some numbers with a new file.
I hope I can get any clues or solutions to solve it.
Thank you.
05-28-2023 10:15 AM
There are many reasons why a program doesn't work. Some of the time, it is the programmer's fault. Some of the time, it is bugs in the Software. Sometimes there are "flaws" in the data being processed.
Simply showing "pictures" of the Error Message and a Front Panel is unlikely to allow us to help you. If you want help/advice, please do the following:
Bob Schor
05-29-2023 06:41 AM
That has happened to me a couple of times. The Report generation toolkit is based on an older Excel and sometimes calls are changed. Open the VI and fix the call.
05-29-2023 09:47 AM
@Yamaeda ha scritto:
That has happened to me a couple of times. The Report generation toolkit is based on an older Excel and sometimes calls are changed. Open the VI and fix the call.
Agree. But beware that if the target computer contains an older Excel version than the development computer, the fixed vi may not work there.
10-27-2024 05:43 PM
Hi all,
I have the same problem. I cannot build my exe due to this broken VI in the Excel report generation toolkit.
I know how to fix the broken VI, but it's not allowing me to save it.
Please advise.
10-28-2024 06:53 PM
@battler. wrote:
Hi all,
I have the same problem. I cannot build my exe due to this broken VI in the Excel report generation toolkit.
I know how to fix the broken VI, but it's not allowing me to save it.
Please advise.
When you get this error message:
It means one of two things.
First, it could just be that the file is set to read-only. Find the current file in explorer, right-click it, select Properties, then uncheck Read-Only.
If that's not it, then you legitimately might not have permissions to modify files in "Program Files" with your login. You might need to speak to your organization's IT department to get permissions to those directories, or you might need to run LabVIEW with admin rights (log in as admin and/or start LabVIEW with the "right-click -> run as administrator" option).