Floating License in a File Server

[Mario romero]

Hi, I have to install a floting license EA in my company... I follow the steps to generate the "sskeys.dat" file in a Windows network file-system (it runs on a storage solution RAID 5) from my worstation. So far so good, I register the floating license in 3 PC's but I got a "Key file has been moved" error in other ones.

Have you ever got this scenario? I read in the troubleshooting section that  working with a Raid solution can be dificult, but I don't have other Non-Raid server to try.

Thanks!

Mario Romero
www.epidataconsulting.com

[Dave_Bullet]

The actual disk implementation (RAID or not) should not make a difference.

You either refer to the path of the sskeys.dat file from a client using either:
UNC path - ie. \\server\path\sskeys.dat (where server is a fully qualified name if in another domain - like server.domain or an IP address, or just the server name if in the same domain
or
Drive letter - ie. x:\path\sskeys.dat

All users must have read AND write access to the folder and sskeys.dat file (since they need to write to the file updating it when they acquire a license).

Cheers,
DAvid.

[Eve]

I'm not sure what troubleshooting section is being referred to, but it probably has a reason for saying that a RAID solution can be tricky.  From what I believe, a keystore is bound to a hard disk.  If I'm correct, I can easily see why a RAID could cause problems.

[Mario romero]

I'm not sure what troubleshooting section is being referred to, but it probably has a reason for saying that a RAID solution can be tricky.  From what I believe, a keystore is bound to a hard disk.  If I'm correct, I can easily see why a RAID could cause problems.

Hi! This is the troubleshooting section referred: http://www.sparxsystems.com/uml_tool_guide/license_management/keystore_troubleshooting.html

Thanks

[Dave_Bullet]

The helpfile alludes to the keystore using the hard drive ID when creating the keystore file.  I don't know what API is used, but maybe if EA is checking / regenerating this - it is getting a different ID for each disk in the RAID.

We operate a fully 2 fledged SANs (terrabytes of data) with RAID1+0 over a geographically dispersed WAN and don't have a problem.

This is a tricky one....

Cheers,
David.