Remember that the passwords in SQL Server 2005 are case sensitive. I would also strongly recommend to add a new password on the production system using ALTER MASTER KEY () in case the original password is truly lost.īTW. Because you would need to use the FORCE option, make sure you have backed up any important data you have modified. On the system where the DBMK cannot be used, you will need to use RESTORE MASTER KEY ( ) with FORCE option to replace the DBMK. On the production system (where the DBMK is protected by the SMK) use BACKUP MASTER KEY ( ) to create a backup of the DBMK. Because the DBMK is still available at least on one of the systems (the production system), it may be possible to recover from this scenario if the DBMK has not been regenerated between the backup that you are using and the production system that still is working. I have been searching all morning and can not find any good documentation regarding the error.Ĭorrect, in this case the error means that the password is incorrect. Have they been using the wrong password to try to open the key? I am not able to reproduce the errors in house on our own DB's. But, the encryption functions still work on their DB. I had the client issue the Open Master Key statement in the prod DB and got the same MSG 15313 error.
Please create a master key in the database or open the master key in the session before performing this operation. The key is not encrypted using the specified decryptor. OPEN MASTER KEY DECRYPTION BY PASSWORD = 'ourpwd'ĪLTER MASTER KEY ADD ENCRYPTION BY SERVICE MASTER KEY A client of ours did a back up and restore of a database which we have created a db master key as well as asymmetric, symmetric keys and certificates.
0 kommentar(er)
