WORKAROUND 1If another Active Roles Administration Service is already running and using the same configuration database that this service is joining, and the new service starts normally, then this warning can be ignored.
WORKAROUND 2Run the below cmdlets to restore the encryption key:
$AREncryptionKeyPwd = Read-Host -AsSecureString -Prompt "Enter the existing password for the Active Roles Encryption Key"
Restore-AREncryptionKey -DatabaseServer "<SQL Server>" -DatabaseName "<ARS DB>" -RestoreFromFile "<AREncryptionKey>" -Password $AREncryptionKeyPwd
If there was no encryption key password set use this command:
Restore-AREncryptionKey -DatabaseServer "<SQL Server>" -DatabaseName "<ARS DB>" -RestoreFromFile "c:\temp\AREncryptionKey.bin"NOTE: To ensure that the correct encryption key is used, use the
Backup-AREncryptionKey cmdlet on a working instance of the old Active Roles version (if possible).
Backup-AREncryptionKey -BackupFile "c:\temp\AREncryptionKey.bin"
STATUS
Waiting for a fix in a future release of Active Roles.