It is common to use the built-in DSP encrypted column functionality to encrypt data source information. Problems may arise during upgrades due to known issues in released versions of DSP.
Data source information is maintained in two tables within DSP:
Generally speaking, working around these issues involves re-synchronizing the information by ensuring encrypted data in these two tables is in a consistent state.
The following workaround is an example, and the steps may be adapted to apply to other similar situations. If assistance is needed adapting the workaround below to the specific situation faced, please open a support ticket.
This example workaround resolves a situation where ttDataSourceRegistry is encrypted and DataSource is not. There will be several other variations of this workaround, depending on the situation, but the steps below are needed in this scenario because some of the Password field values were encrypted in the DataSource table, and some were not. In this case, attempting to reenable encryption via the UI fails because already encrypted values cannot be encrypted again.
- Decrypt Password fields in both DSPCommon and CranSoft databases
- Manually edit the DataSourceTableColumnEncryption table to change the EncryptionStateID field for the associated column to a ‘1’
- Manually editing the DataSource table in CranSoft to change the Password field values for all records that are displaying as encrypted, replacing with real password values