Unable to load the SQLite datasource. The saved master key is invalid!
Unable to load the SQLite datasource. The saved master key is invalid!
I did some research and it looks like a lot of people ran into this error back in March, and code update was required (ref). Unfortunately I'm not sure that is issue here.
I have two computers, one works, and one does not. One is running the Windows 10 1909, and the other is running Insider Preview build 19608.1006. Both systems are using the same configuration, and the latest release of RDM (v2020.1.20.0).
Any thoughts or suggestions would be greatly appreciated.
AppLogs.csv
All Comments (6)
Hello,
Do you share the SQLite database?
Regards
David Hervieux
Yes, all the RDM config is stored on OneDrive.
Hello Roland,
Sorry to jump in! If I am not mistaken, SQLite is using the encryption of Windows, which would explain why it is not portable. I will need to confirm this.
That being said, would it be possible for you to create an XML Data Source instead and see if the master is accepted on both workstations?
Best regards,
James Lafleur
Happy to give it a try after my next conference call. But I've been using this method for ~2 years or so, and it worked yesterday and not today. Oddly there were now changes that i know of in that time, though there was Insider preview update 2 days ago. But like I said, after installing that update it worked fine for a day.
I've exported the db to xml on the 1909 machine to OneDrive, and successfully added it as a datasource on the 19608.1006, and that is working for moment. Bu that really doesn't explain why the db suddenly doesn't work. I assume its something with the Insider Preview build, but it seems quite odd that it worked fine for a day after the latest update was installed.
Hello Roland,
Thank you for your quick reply and for performing this test!
Since the only change that was made was the Insider preview update, I suspect that this might be the cause of this issue. That said, I agree that this is strange that the master key worked for a day. As a test, would it be possible for you to revert to the previous build and see if this issue persists?
Best regards,
James Lafleur