Symptom
The InstantData service keyring (managed by the system's data protection API) somehow becomes corrupted, and the service goes into a loop as it retries to read it.
Workaround
1. Open the settings.json file. The content looks like this:
-
{ "Secrets": { "49334462-cc4d-4115-9faf-d3e10969c880": "CfDJ8GzzYECz6o5HgEBaZULrtiTWv3yBKhk_m7ZGhNpbIlwvapnozBw-HTJhI_ELxkHh_JqwwaWkg9FETZN2ZmzHRBcCt-HNaDMLQUlM1IxonVUzaOUVMvB9bL8vf8FCIZtWEKI8qnDkZWu1xt_UZOHvzIZeHKjqJ-5xZ5pzaU7fAjUB3aDlPHKJe-XlFVtP1LlcDO6Hcizf-SYXrEWvB2Hz57qWsSjsP7-kcjyULznh4Ih1" }, "RefreshInterval": "1.00:00:00", "Timeout": "00:01:40", "Accounts": [ { "Server": "onlinebackup.redstor.com", "Port": 443, "AccountGuid": "49334462-cc4d-4115-9faf-d3e10969c880", "Servers": [ "https://UKDC1SS91.PRO.REDSTOR.COM:443/", "https://UKDC2MS91.PRO.REDSTOR.COM:443/" ] } ], "LastAccessUpdateEnabled": true, "DownloadCompleteNotificationEnabled": false }
2. Delete the Secrets section (i.e. the keys and account info) from this file, then save the file.
3. Start the InstantData service.
4. Run an Archiving task to reapply the encryption key to the account.
Comments
0 comments
Please sign in to leave a comment.