KeeAnywhere-1.5.0 plugin incompatible with Keepass 2.40

[LegoChicken]

Two machines running Windows 7 professional. One works fine the other one produces:

[pascal69480]

Unfortunatly had a similar issue on my 7 machine.
Have tried to delete the directory in the \AppData\Local\KeePass\PluginCache\KVtC9Wrw4Tat3CIKCR6e directory but it was recreated at the next run of the app.

I read in the release note :
Default Storage Location for settings is now in User's Roaming AppData instead of User's Local AppData. but nothing seems to be stored in this path :(

I'm unable to open my Dropbox stored file and plan to downgrade KP to (temporary) solve the problem.

[LegoChicken]

I also tried deleting the PluginCache directories. It was recreated on the next run of the app.

[Antasik]

Hello,

After moving KeePass (2.40 portable) to new Windows 10 machine i've got the same Error. I solved the problem by removing KeeAnywhere.Accounts.json file from KeePass directory. It looks like "secret" is encrypted and need to be decrypted in the same machine and user account but i'm not sure.

BR,
Marcin

[eulercb]

To avoid this problem, just select KeePass Configuration for Storage Location and you will be able to use your settings KeeAnywhere on any machine. Be aware that your access token will be stored unencrypted in KeePass.config.xml file.

[Kyrodan]

I see two different errors here:

1. "Key not valid for use in special state"
2. "Impossible to load Microsoft.Graph.Core..."

Topic 1:
I double checked the documentation and can't find a problem I can fix. As @Antasik statet (#147 (comment)) the KeeAnywhere.Accounts.json is encrypted via the current users account secrets. It can't be read, if it is not the same user anymore: copied the file to another users directory; deleted the original account and recreated a new one with the same name; etc. If it's a domain user, it also works on other machines (for what I move this file to "Roaming" App Data folder.

Topic 2:
In next version I applied another improvement for this problem. I can't reproduce this issue and do not know, why this still happens on some machines.

Other remarks:
@pascal69480: User's Roamin App Data is used. Old data get's converted. Maybe you used my temporary developer build? Then this is behavior does not happen and you have to move it by hand.

[LegoChicken]

Still not working after upgrading to 1.5.1. Deleted everything in the PluginCache directory. Can you please re-open this defect.

[Kyrodan]

@LegoChicken: v1.5.1 indeed does not fix your issue because maybe this is not an issue :-)
Please check my post #147 (comment):

Topic 1:
I double checked the documentation and can't find a problem I can fix. As @Antasik statet (#147 (comment)) the KeeAnywhere.Accounts.json is encrypted via the current users account secrets. It can't be read, if it is not the same user anymore: copied the file to another users directory; deleted the original account and recreated a new one with the same name; etc. If it's a domain user, it also works on other machines (for what I move this file to "Roaming" App Data folder.

Maybe try to save the account info to KeePass config instead of seperate KeeAnywhere.Accounts.json

[Antasik]

In my opinion plugin behavior is fine and expected (there is no needed crypto key on new/other user profile) but exception info is misleading. Information thrown should be clear (about encrypt not "plugin incompatible with Keepass 2.40")

[LegoChicken]

I finally got back to looking at this again. I deleted the KeeAnywhere.Accounts.json file from KeePass directory and set it up again and now works.