Write protection of _TSUtility.llb under Windows10

[OnlyOne]

Hello,

i have a installation of Testand2019 and Labview2019.

In Labview i am using a file from C:\Program Files (x86)\National Instruments\TestStand 2019\API\LabVIEW\_TSUtility.llb

When i save my file then Labview also wants to save the file which is in the above llb (Changes: The file was converted from a different version of labview).

When i press save+yes then i get error "Cannot save xxxxx. You do not have permission to write to the containing LLB.

What has to be done?

Should i move the complete folder C:\Program Files (x86)\National Instruments\TestStand 2019\API\LabVIEW to another position?

Thanks

[IDASYAN]

Hi, 

Just for any case, never move NI Software from the original place. 

My suggestion will be to uninstall both and install again, use NI Package Manager for both, there might be a need to reinstall NI Package Manager as well, don't move anything. 

Thx.

[Anand_Jain · Accepted solution]

Hi, 

Your G code should be using the version of the file from vi.lib (C:\Program Files(x86)\National Instruments\LabVIEW 2019\vi.lib\addons\TestStand), and not from TS's folder. 

If there are no files in that location (C:\Program Files(x86)\National Instruments\LabVIEW 2019\vi.lib\addons\TestStand), then launch the Sequence Editor once on that machine. TS will copy the files to that location at startup of the application. 

Also by default all the VIs in the llb are marked source-only and LV should not prompt you to save.

Can you post the reasons LV provides when you get the prompt to save?

Regards, 

Anand Jain

NI

[OnlyOne]

Hi,

thank you for this great tip.

You are right, i didnt start Teststand once before i opened my VIs. Thats why they got linked to the write-protected llb in the Teststand folder.

I just checked now (after i iopened teststand several times) if there are now files in ..LabVIEW 2019\vi.lib\addons\TestStand

Then i temporay moved the teststand file in another directory so that my VIs get linked to the \vi.lib folder and now i can normally save without write protection error messages.

There was no reason in the error message, only that the file inside the llb cannot be saved "and that i should chose another location to save the file"

Thank you

[Fewoiz3]

So that's how I get it.  I've been searching all over and finally found this answer to how I get the llb.  I'm reviewing our internal code and this VI is missing on my system.  Finally searching the internet brought me to his post.  There is absolutely no way I would have figured this out any other way.  I have TestStand installed, but don't plan to use it for a while, so I never opened it.  It's corrupt and won't open so I'm re-installing it now.  Hopefully opening TestStand will copy the files as you described.