SQL Monitor 13

Unable to read keys file

The contents of the encryption keys file could not be read by the Base Monitor. A Base Monitor cannot function without at least one encryption key.

The cause of this error will be visible in the Base Monitor's log file. Some of the common causes are listed below.

Could not find file

A custom encryption keys file path has been specified, but the file does not exist.

The encryption keys file path is configured in the path property of the keyStore section of the application settings file found at %ProgramData%\Red Gate\SQL Monitor\appsettings.json. Ensure this path is correct and points to an existing file.

Access to the path is denied

The base monitor's service account does not have permission to read the encryption keys file. Check the permissions on the encryption keys file and ensure the base monitor's service account has read access.

The input is not a valid base-64 string

The format of the encryption keys file is incorrect. See Managing the encryption key store file for details on how the file should be formatted.

Keys file did not contain any keys

No keys were found in the encryption keys file. Check that the file is in the correct format and that it contains at least one encryption key.






Do you have any feedback on this documentation?

Let us know at sqlmonitorfeedback@red-gate.com


Didn't find what you were looking for?