Common Access and Exception Errors
You may encounter an error message such as 'The package failed to decrypt a sensitive data' when attempting to open a DTS Password within a XML node. Here are some common errors or issues you may experience:
"The package failed to decrypt a sensitive data. Access to the database or the certificate is not available."
- This means that either the database or the certificate being used to store and decrypt the sensitive data is no longer accessible.
"Failed to decrypt protected XML node."
- This error is typically caused if the DTS ProtectionLevel is set to "EncryptSensitiveWithUserKey". This property can be changed to allow for easier decryption of a DTS Password.
Solution Steps to Troubleshoot Failed Decryption
To troubleshoot this issue, you will need to take the following steps:
- Verify Database and Certificate Accessibility: Determine if the necessary database and/or certificate is accessible.
- Set the ProtectionLevel Property to "EncryptSensitiveWithPassword": Set the "ProtectionLevel" property of the package to "EncryptSensitiveWithPassword" to allow for easier decryption of a DTS Password.
- Check Permissions: If the package can’t access a credential or certificate object, confirm the package does not have incorrect permissions.
- Check for Outdated or Uninstalled Packages: Determine if any outdated or uninstalled packages are being used.
Q: How do I set the ProtectionLevel property to "EncryptSensitiveWithPassword"?
A: The ProtectionLevel property of the package can be changed from "EncryptSensitiveWithUserKey" to "EncryptSensitiveWithPassword" in the package designer or via scripting.
Q: What other tips should I keep in mind while troubleshooting this issue?
A: While troubleshooting, it’s also good to check the event viewer logs and verify that the package is not running with an outdated version of the package. Additionally, ensure that the necessary ISPac packages are not missing.