Unlock file and folder attribute does not work in LV 2012

[andrej]

Hi,

I use unlock attribute to unlock a folder (set in installer build specification -> Source File Settings -> File and Folder attributes). This installer installs the application into Program Files (Win7 x64) and when application is started it creates a file in the "unlocked" folder. I used this many times with LV 2011, however this does not work with LV 2012 (the folder is not unlocked)? An example for LV 2012 (without installer) is attached, the same example works if I build it with LV 2011.

[bepus]

I've noticed the same problem with LV2012 even if I create a new installer in LV2012 (unlock with installer of LV2011 works fine). I will meet some NI-people tonight and maybe I'll know more tomorrow. 

Greetings B.

[BalazsNagy]

Hi!

Sorry for the late reply. Actually I tried to reproduce the problem.And I saw the same.

Installers created in LV2011 work fine, but to reach the same functionality with LV 2012 you have to run the installed application as administrator.

Please try to run your installed application (created with LV 2012) as administrator, and post the result.

Best regards,

[andrej]

Hi Balazs,

it is expected that if you run application as administrator to have right to write into any folder, because administrator has full access on all folders.

However, this solution is not acceptable for me, because my customers are not allowed to run application as administrator.

The unlock attribute should be used for the purpose as described in Labview help: "Unlock—Place a checkmark in the checkbox to unlock the selected file or folder. You cannot use the Unlock option for predefined destination folders in the Destination View tree, including absolute paths. When you unlock a file or folder, you remove administrator access requirements from deployed files and folders, which allows anyone to edit files and folders after they have been installed."

I think this is a bug. I am looking for the workaround (until fix comes), but running application as administrator is unacceptable.

I can also set folder rights manually, but this is also unacceptable solution for my customers.

[bepus]

Andrej is right. Of course this works (I have already tested this before) but this is not the desired solution for us, too. We have also many customers using our software without admin rights. Furthermore it seems to work with new LV2012 projects. Yet, I have not tested the new generation of a project with the LV2012 VIs (mass compiled...) and generating new application builder and new installer, but if this works it is also not preferred, because we have many LV2011 projects and the transfer to new LV2012 projects would last very long, too long for us.

[andrej]

Bepus,

I created new project in LV2012 and unlock still didn't have any effect. Could you upload your project?

[bepus]

You are right again, I tested a new project now, and it didn't work (I thought it would work, sorry). I have informed the NI support a few days ago, and they told me not to know the problem but they will discuss the problem and contact me afterwards. I hope the will do so. 

[andrej]

I have also contact NI support, so I hope we will have the answer or better the solution soon.

[bepus · Accepted solution]

I have received an email of NI support today:

'As discussed, I have analyzed the behavior you described "unlocking folders and files not working."
The error could be reproduced. This was also successfully detected and documented.
The development team is working on this and the next update may have already solved this problem.'

I hope this will be very soon :-).

[andrej]

I received the same answer.