LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Convert build script in LV 8

Hi,
im working on Linux platform with both LV6.1 and LV8 installations.
I need to convert my program, built in LV 6.1 to LV 8. As i already have a build script in LV 6.1. I compile the program in LV 8 and use the convert build script option from the tools menu of LV 8.
However im unable to do so. I get an error message (error 43)- Operation cancelled by user. Im unable to understand why this message is being displayed.
Attached with this mail is a screenshot of the error message
Kindly help
0 Kudos
Message 1 of 7
(3,473 Views)
Hi pavitraba,

maybe LV8 has problems to load an LV61 build script? But the error message should be different...

One comment on your attachment: By renaming an picture from bmp to jpg you don't change it file format. It would be much better to save pictures as (real) jpg or png. You can also make the window smaller to reduce the size of the picture. Nearly 4MB is waste of space for such a simple error message...
I have attached your picture again, so others may not have to wait for a minute (or so) for display).

Message Edited by GerdW on 07-12-2006 02:58 PM

Best regards,
GerdW


using LV2016/2019/2021 on Win10/11+cRIO, TestStand2016/2019
0 Kudos
Message 2 of 7
(3,467 Views)
HI,
Thanks for the useful input regarding picture attachments.

BTW ive got a lead for the solution to my problem. Do you have any idea. how to check whether  a VI is write protected?

Pavitra
0 Kudos
Message 3 of 7
(3,454 Views)
Hello Pavitra,

what do you mean by write protected: Is the vi locked for editing or are there restrictments on file access by file system or user privileges?

In LV6.1 the function 'Access Rights' in the file palette reads and sets the write protection (on Windows atleast for the user level). See the help for this function, it's a pretty good explanation. To check the vi status you can use the invoke node 'Get lock state' on a vi reference.

Best regards,
GerdW


using LV2016/2019/2021 on Win10/11+cRIO, TestStand2016/2019
0 Kudos
Message 4 of 7
(3,452 Views)
HI GerdW,

This is the solution i got from support NI.

"The error you are getting could be on account of the fact that some of the VI's that you trying to build through the build script are write protected.

This error or one extremely similar has been reported as an issue with importing build scripts (NI Error Report ID: 3Q9EHGF2).  It seems that an error should be generated saying that one of your VIs is read only when it needs to write the VI, but instead somewhere along the line its generating error 43 (user cancel).

Write enabling the application and all of its sub-VI's should complete the conversion with no errors. "

I have around 200 VI's in my build script. As the error message does not specify the vi, do i have to check the access rights of each vi?

Regards,
Pavitra
0 Kudos
Message 5 of 7
(3,448 Views)
Hello Pavitra,

in Windows you can set access rights for a folder and all it's content in one step...

Best regards,
GerdW


using LV2016/2019/2021 on Win10/11+cRIO, TestStand2016/2019
0 Kudos
Message 6 of 7
(3,432 Views)
Hi GerdW,

Thanks for your reply.

I am working on a Linux platform and dont have adminstrative rights, only user rights of the system. Hence, i am unable to change the access rights for the error.llb's of Labview 8. Could that be a reason why Labview is unable to convert the build script.

Regards,
Pavitra
0 Kudos
Message 7 of 7
(3,424 Views)