Role base security is throwing an exception when the session lock timer fires. See attached.

I can’t be sure but it seems that the AppLifeUpdate and sessionmonitoring issues started with 1.7.7.1. I don’t know if anything changed in SFrelated to session monitoring with that release or if Microsoft released an OSpatch that may somehow be causing a conflict. In any event the AppLifeUpdateand session monitoring is not a problem since I know how to work around it byturning off session monitoring when processing an update. The real issue for meis trying to figure out why I’m getting the duplicate key error while the applicationis running. I can’t reliably reproduce the error, it just randomly happens.

BTW, how is SF2.0 coming along?

-Larry

It is possible that I broke something in some changes I made for 1.7.7.1.  We started using a WPF dialog for our login process with several of our applications.  A WPF Window certainly doesn't inherit from WinForms Form, so I had to add another interface ILoginFormExtended and tie the session locking into that.  Upon hearing of your problems yesterday, I made some changes to the SessionLock class to simply hide the forms when the session locks, so they don't stay on the task bar, only the login form is shown on the taskbar.  The side effect of that is that I no longer need a dictionary to store off the WindowState of each of the windows, so I changed it to use a list instead.  I'm not sure what could be calling LockSession() when it's already locked, but no longer using a dictionary, you certainly wouldn't get a duplicate key exception any more.