Book a Demo

Author Topic: Automatically returning shared keys  (Read 2354 times)

jeromy

  • EA Novice
  • *
  • Posts: 2
  • Karma: +0/-0
    • View Profile
Automatically returning shared keys
« on: August 30, 2006, 06:15:09 pm »
Hi,
Is anyone able to explain how returning shared keys works with EA 6.1 (corporate), and/or if they have their own process of accessing shared keys that works well?

We're encountering two very annoying problems:
 - if EA crashes (as it does) the shared key doesn't appear to be released, and restarting the application doesn't seem to (always) reacquire the same key, locking another; and
 - several users use laptops and often leave the network while EA is still running with a key locked.  If they quit EA whilst off the network, the next time they start EA they seem to acquire a different key while the original remains locked by them

I'm told the minimum time for a key to automatically unlock is 24hrs, so several times we're been in a situation where all keys are locked by users, none of the users are running EA, and none of them can start EA because there's no keys available.

The only work-around is to get an administrator to run the tool that manually unlocks keys, or to wait a while.  

Is this a common occurence or are we doing something wrong?

«Midnight»

  • EA Guru
  • *****
  • Posts: 5651
  • Karma: +0/-0
  • That nice Mister Grey
    • View Profile
Re: Automatically returning shared keys
« Reply #1 on: August 31, 2006, 03:17:37 am »
Jeromy,

Some shared key issues were addressed in version 6.5. You might want to browse through the release notes for builds 795 and subseqent (beta 1 and 2 at this time) to see if your concerns were among these. You can find the release notes in the Latest News section at the top of the forum main page.

David
No, you can't have it!

jeromy

  • EA Novice
  • *
  • Posts: 2
  • Karma: +0/-0
    • View Profile
Re: Automatically returning shared keys
« Reply #2 on: August 31, 2006, 04:33:24 pm »
Thanks David, the release notes for EA 6.5 Build 796 (Beta 2) appear to address the issue.  I'll give that version a try.