automatic security handling doesn't work at all

[cs42]

Hi all,

I'm just discovering that the automatic security handling of LV DSC 7.0 doesn't work! That means if I set security options for a control, they won't be applied. Even the VI's in example\lvdsc\security don't work as supposed (and as they did in LV DSC 6.1)!

Does anyone out there experience the same problems?

[Khalid]

Hi,

I hate to just give the it-works-for-me-fine answer, but it truly seems to work just fine for me. I just tested it with a Control, and also tried the HMI Security.vi from the examples.

Did you upgrade your 6.1 system to 7.0 replacing it in-place? If yes, did you have user-accounts configured / changed. Can you try this on a fresh machine?

Regards,

Khalid

[cs42]

Hi,

I'm not surprised hearing that...

For the installation: I did try to remove LV 6.1 completely off the machine; so it could be considered a fresh one.

I'll test it on a fresh machine tomorrow again.

Regards

[cs42]

Hi again,

just the results of a very quick test: logging off and on again

All works fine after that (even in my VI)! Do you have an idea, what could confuse the automatic security handling?

I'll do further tests tomorrow...

Cheers,
Carsten

[JR_A.]

Since logging off and then back on seems to fix the problem it would seem that when LabVIEW is starting it is automatically logging you into an account with access priviledges. You can check what account is automatically logged into by launching LabVIEW and going to Tools>>DSC Module>>Security>>User Info.... You can also set this behavior by logging in as an Administrator and then going to Tools>>DSC Module>>Options and then the Security Preferences button on the Advanced tab.

Regards,

JR A.

[cs42]

I'll have a look at it but I don't suppose this could be the reason.

In my tests I did log on and off as different users with different rights. And on my test app (just created a small one) I had controls which should be activated/disactivated&gray for these different users. Using the DSC dialog to log on and off didn't do anything first. But after logging off the machine and on again all worked fine.

I did some tests yesterday, but could not reproduce this behaviour unfortunately.

Cheers,
Carsten