hi @growlingflea ,
Quick key background:
- There is a keyset in the database (in keys table), which is used to encrypt data that is stored on the drive
- There is a keyset on the drive (
logs_and_miscsubdir of the documents), which is used to encrypt data that is stored in the database (this is the keyset that is used to encrypt password/sensitive data in globals). The kicker to this mechanism is that we actually encrypt this keyset on the drive with the keyset in the database. Thus if you try to take a database from another instance (different keyset in keys table), then the encryption/decryption to/from the database will break down (since it it no longer compatible with the key stored on the drive(i.e. it can’t be unencrypted). I am guessing this type of problem is what is causing your issue. A way to test this would be to remove the keys inlogs_and_miscsubdir of the documents (make sure you keep that key around though in case this does not work) and then a new key will be created that is compatible with the keyset in the database. So, the save in globals should now work. Before you get in habit of doing this, do realize, that by removing the prior key from the drive means you would never be able to unencrypt the encrypted stuff stored in database (database globals and the log stuff if you have log encryption turned on).