"Please re-install EA" err msg on Sparx launch

[andykennelly]

"One of my colleagues has installed Sparx in the correct way (or, as far as he is aware, anyway) but when he launches it he gets this message:-

"Error opening or accessing key file! Cannot continue.  Please re-install Enterprise Architect!".
At first I thought he needed to define the path to the floating licence repository - but he can't even open Sparx at all. The error message appears as soon as he clicks the sparx launch icon.

I tried searching for "re-install" across the forum (possibly incorrectly) but couldn't find anything.

It might well, of course, be something related to his user profile etc., rather than something related to the sparx app.

Has anybody experienced this?
[original message]

[qwerty]

I haven't seen that, but it might as well be related to missing rights to modify the registry. Probably an admin should do the re-install.

q.
[original message]

[Ortmann@localhost Helmut Ortmann]

Hi,

I've seen the message when clicking multiple times on the EA shape.

It happens: If EA is started twice or more in a short time and you use a key server.

I usually wait until all EA instances are started. Then I close the not working EA instances and everything is fine. Sometimes I have to wait 5 minutes. Mostly it's only annoying.

Helmut
[original message]

[B@localhost Aaron B]

This error message typically indicates that the local key.dat file has become corrupted and needs to be re-built.  Please try performing the following steps:

- Close EA
- From the Windows Desktop, open Start > Run (Windows Key + R), paste "%APPDATA%\Sparx Systems\EA" and click OK.  It should open this directory for you in a new explorer window.
- You should see a "key.dat" file in this directory
- Rename the file "key.dat" to "key.dat.bak"
- Restart EA

(Do not rename or delete the key.dat file under the "Program Files" directory.)

A new "key.dat" file should automatically be generated.  When prompted by EA, add your license keys.  After adding licenses, if EA appears to run without any further error messages you should be able to safely delete the "key.dat.bak" file that was renamed earlier.
[original message]