Source: SecureLogin
Possible Cause: SecureLogin tried to read or write to the offline cache. However, SecureLogin is unable to open the cache file.
Action: Assign rights so that the specified user has rights to the cache directory.