Please note : This help page is not for the latest version of Enterprise Architect. The latest help can be found here.

Keystore Troubleshooting

The management of shared keys can be an onerous task, so Enterprise Architect provides the Keystore and its management interface to make the administration as easy as possible. Occasionally issues arise that prevent users from obtaining a license; these are typically due to the setup of the keystore and can be easily rectified.

Error Messages and Handling

Message Displayed:	Explanation
Error reading Key Store file: (Access is denied)	All users who are to use the shared key facility require Read, Write and Modify access to the sskeys.dat file containing the shared keys. Please verify that all required users have sufficient permissions to the file and try again. Review the effective permissions calculated at the location of the key file for the user account reporting the problem - you should closely examine the permissions for both the Network Share and the File System; it is possible that these permissions have been overwritten at some point. If the problem continues, contact Sparx Support.
Error reading Key Store file: (Key File has been moved)	In the key store, as a security measure the hard drive serial number is recorded when the file is created; the file then cannot be moved from the original location in which it was created. If the key store has to be re-located for any reason, the administrator should re-create the key store in the new location using the original license keys. This issue is commonly seen after a file server has undergone a hardware upgrade in which the physical hard drives have been replaced; problems could also occur if the drive used is part of a RAID configuration. The message can also appear where the key store exists on a Novell-based file system - when creating the key store, the administrator is prompted to confirm that the key store is to be located on a Novell Netware file server; if they click on the Yes button, the key store instead records the logical path used to create it, and all users must connect to the key store using this same path. The recorded path is case-sensitive and must be an exact match.

Message Displayed:

Explanation

Error reading Key Store file:
(Access is denied)

All users who are to use the shared key facility require Read, Write and Modify access to the sskeys.dat file containing the shared keys.

Please verify that all required users have sufficient permissions to the file and try again.

Review the effective permissions calculated at the location of the key file for the user account reporting the problem - you should closely examine the permissions for both the Network Share and the File System; it is possible that these permissions have been overwritten at some point.

If the problem continues, contact Sparx Support.

Error reading Key Store file:
(Key File has been moved)

In the key store, as a security measure the hard drive serial number is recorded when the file is created; the file then cannot be moved from the original location in which it was created.

If the key store has to be re-located for any reason, the administrator should re-create the key store in the new location using the original license keys.

This issue is commonly seen after a file server has undergone a hardware upgrade in which the physical hard drives have been replaced; problems could also occur if the drive used is part of a RAID configuration.

The message can also appear where the key store exists on a Novell-based file system - when creating the key store, the administrator is prompted to confirm that the key store is to be located on a Novell Netware file server; if they click on the Yes button, the key store instead records the logical path used to create it, and all users must connect to the key store using this same path.

The recorded path is case-sensitive and must be an exact match.