NI SECURITY

[aSquared]

Hi,

I use LabVIEW 8.2.1 DSC.

I have included NI Security Invoke Login Dialog.vi in my application.

(right click from the Block Diagram DSC MODULE>>Security>>NI Security Invoke Login Dialog)

But when the Dialog pops up, if you use the 'X' to close the Dialog box, 

LabVIEW stucks and need to be stopped from the OS Task Manager. 

I found that this is a known problem with the LabVIEW version that I have, at -

http://digital.ni.com/public.nsf/allkb/A58CF302F2746F1A8625733800691335?OpenDocument

Did anyone ever repaired this VI (for the 8.2.1 version) ?

(The application that is running is very important and sensitive, so I cannot allow the possibility that someone might close the Dialog Box using the 'X' and will hang all the other properties)

Sincerely yours ,

Amitai

[Ben]

Thank you for bringing that issue to our attention Amitai!

Let me now quote from that KB;

---

Solution:
The workaround for this problem is to use the Cancel button instead of the exit button to close out of the dialog.

---

Am I alone in my impresion that has to be one of the most lame "Solutions" ever offered?*

Can we please get an AE to research this issue and the state of the CAR?

I would expect wrapping that VI in another that disables to ability to close the window with the X or even monitor the FP state and if not open progrmatically punching the cancel button would work.

Ben

* That work-around reads like;

Customer : Every time I push the Stop button on the dashboard the engine blows-up. What do you suggest?

Mechanic : Don't push the the Stop button.

[aSquared]

Hi Ben,

Thank you for your reply,

(you also helped me with PID-Autotuning once, and I need to thank you about that.

though something wasn't clear back then, and I will get back to it in a week or two,

and I hope that you will still have the time to help me then)

Regarding the NI Security Invoke Dialog Loggin,

I would have tried to fix this VI on my own (just disabling the 'X - exit' option of the Dialog Box from its property node)

but the VI himself is password protected (even for viewing) by the developers.

LabVIEW support told me that this bug was fixed at LabVIEW 8.6, and I understand that every software has its bugs,

but upgrading is too complicated because all my controller are now working with the 8.2.1 version,

and upgrading to 8.2  was very complicated and created a lot of malfunctions.

Sincerely yours, 

Amitai

[Ben]

I'm not sure if this will help but its worth a try.

At the start of program open a ref to that VI (I suspect it will be in memory and all you need is the name wired to the path input) and set the "FP.Closable" property to "false".

That may be all you need for now.

BTW: if this works for you please let me know (and mark this post as a solution).

Still just trying to help,

Ben

Message Edited by Ben on 12-03-2008 11:51 AM

[aSquared]

Hi Ben,

Thank you for your reply,

I will be able to check it only at Sunday,

I will inform you then.

Thank you,

Amitai

[Hillman]

Hi Ben and Amitai,

Amitai - thanks for bring this Knowledgebase / Bug to my attention. 

Ben - Thanks for your suggesting. This would indeed look like a possible work around i.e. to prevent the event ever happening, good job!

I will investigate this issue and take any necessary action. I will update the post with any findings.

Thanks again both of you.

[Ben]

Thanks James.

If that works please edit that KB article (before one of my customers finds and reads it )

Ben

[Hillman]

Hi Amitai, Ben and All.

I hope your well.

I can confirm the bug. And that its been resolved in newever versions. I also agree the 'workaround' is rubbish. I have attempted the FP.closeable - but this seems to currently cause the VI to hang. Also, accessing the option by Tools>>Security>>Login also causes the same hang.

I have started talking to the State side team to get more information on the CAR and any more workarounds.

My current ideas have mainly been to edit the VI or save the newer NI Security Invoke Login Dialog.vi (8.5 / 8.6) back to DSC 8.2.1.

I will keep you posted.

[Hillman]

Hi Amitai, Ben and All.

I hope your well.

The CAR was closed with a fixed status in LabVIEW 8.5. The KB does provide a workaround in the fact that using the cancel button will provide the same functionality as pressing the "X" button will, but without the unfortunate crash.

The consensus is that R&D wont provide the password to that specific VI since the workaround in the KB is viable and the bug isn't a showstopper and because it was fixed in LabVIEW 8.5.

However, a possible solution has been suggested:

You could programmatically get the handle to the dialog window and then dynamically handle the "X" button press event and redirect it to the cancel button. This would have the advantage of looking the same to the user.

I wish I had better news for you.

I will attempted to program the workaround this afternoon and let you know how I get on.

[Hillman]

Hi All,

I am afraid I cant implement this workaround - any of the DLL calls I make freeze when the Security Panel opens (even when VIs are caleld dynamically). 

The only thing I can suggest is to generate another window on screen in Large Letters 😄 to ask the user not to press it.

For reference, I beleive the Message..::.HWnd Property would be something to use, if someone who understand Windows better could implement this. 

I am sorry that no better solution could be produced.