To resolve the issue complete the following steps:
- Connect to SQL instance on the Agent machine via SQL Sever Management Studio.
- Find the encrypted database and click through the context menu All tasks -> Encryption. You will see a certificate name.
- Select master database and execute the following query to export the certificate:
- BACKUP CERTIFICATE cert_name TO FILE=’C:\1.certbak’
- WITH PRIVATE KEY (
- FILE=’C:\1.pkbak’,
- ENCRYPTION BY PASSWORD=’ENTER ANY PASSWORD HERE’)
- NOTE: cert_name – is the name of the certificate.
- Copy C:\1.pkbak and C:\1.certbak from the Agent to the Core machine.
- On the Core machine, connect to Core SQL instance via SQL manager and execute the following query to import the certificate:
- REATE CERTIFICATE certificate_name
- FROM FILE=’C:\1.certbak’
- WITH PRIVATE KEY(
- FILE=’C:\1.pkbak’,
- DECRYPTION BY PASSWORD=’ENTER ANY PASSWORD HERE’)
- NOTE: certificate_name – this name should be unique.
- In some cases SQL instance will ask you to create master key. To do this execute the following query:
- CREATE MASTER KEY
- ENCRYPTION BY PASSWORD = ’123′
- Then perform query from step 4 once again.
- NOTE: Certificate with Unique Thumbrint should be imported only one time.
- Perform these steps for every certificate in use on the Agent machine.
- Perform attachability check to verify that the issue has been resolved.
- Delete the files *.pkbak and *.certbak from C drive of the Agent machine.
No comments:
Post a Comment