DSC application with security problem

[peter_smith]

I'm currently developing a DSC application in LV8.5. On my development machine everything goes fine when I run my application.
On the front panel I have a STOP button, which has security feature enabled. Only one rule is defined: Operators group has the full control enabled.
In domain manager I made a local domain named "smith" on my development machine.
On an other machine which is currently my target for testing purposes, I have LV8.5 installed (I use only the Runtime Engine, because I test on this machine the compiled .exe applications only). I also installed the DSC Runtime System.
On the test machine I made also a local domain called "smith". On both machines I added a user who is the member of the operators group.

My problem is when I run the application on the test machine, the button disappears. It's OK, because I'm not logged in. BUT when I log in to the account of the user who is member of the operators group, the button doesn't show up.
On my development machine it does. Also I can press it when I'm logged in.

Any idea? Someone help please!

Thank you!


Peter Smith

[Johann.Wagner]

Hi,

can you attach here the screenshot and the vi of the problem. Try to build a debuggable *.exe (settings in build application) and try debugging it on other PC with the 30 days evaluation of LV or you set flags with additional indicators so you see on with structures your programm is when log in.

i can imagine that is a path or string problem and so debugging is the best way to find the problem. Have you test it in your developer machine with *.exe or *.vi ??

Best Regards

AE Munich (Germany)

[Johann.Wagner]

Problem:
If the only LabVIEW DSC module VIs your application uses are the Security VIs, you can distribute those VIs without using the LabVIEW DSC module Run-Time System. The LabVIEW DSC Help File indicates a way to deploy such an application, but you have to manually move files from the development computer to the deployment computer. How can I include the necessary VIs as support files so I don't have to go through this process?

Solution:
To include the necessary files as support files, you will first have to move the lv_init.vi out of the LabVIEW 6.x folder, as this VI is loaded into memory every time LabVIEW DSC Module starts, prohibiting you to include it as a support file. The following steps detail this procedure:

1. Close LabVIEW and the Tag Engine
2. Move the lv_init.vi out of the LabVIEW 6.x\vi.lib folder to a temporary directory
3. Restart LabVIEW and go to Build Application or Shared Library (DLL)

When you have configured all the parameters to build your application such as Destination Directory, Top-Level VI and any other options, you need to include the necessary security files (see Help) as support files and select a custom install destination for them. For this example, we will use the application folder as MyApp on the deployment computer, the custom destinations will be as follows:

• MyApp\vi.lib for the lv_init.vi file now located in your temporary directory
• MyApp\vi.lib\extensions\_core for every file of the LabVIEW 6.x\vi.lib\extensions\_core folder
• MyApp\vi.lib\extensions for the LVSecurity.vi file
• MyApp\vi.lib\extensions for the _security_stubs.llb file
• MyApp\vi.lib\extensions\security for every file of the LabVIEW 6.x\vi.lib\extensions\security folder

When you have successfully built the application, close LabVIEW and the Tag Engine and move the lv_init.vi back to its original location.

Also see the DSC Module help for deploying such an application: Help » LabVIEW Datalogging and Supervisory Control Module Help » Contents » Networking and Deploying Applications » Applications that Include Only Security VIs.

[Johann.Wagner]

Problem:
I have developed an application with the LabVIEW DSC module and I created and used an NI Security Domain. Now I want to move this application to another network or PC. How can I keep the Domain settings for the new PC/network?

Solution:
You should copy the directory located at Program Files\National Instruments\Shared\Domain to the same location on the destination PC. To apply the changes you should restart your computer.

You can also completely remove the NI Security Domain (if you forget your password, etc.) by deleting all the files from this Domain folder.

[peter_smith]

Thank You for your replies. I managed to solve my problem the way You suggsted in your last message.


Thank You and best regards,


                                           Peter Smith