Hi @Linda Doan ,
Have you tried below resolution? If not you may have a try.
- Change all the connection managers in the package to use windows authentication.
Note: This is not an option while communicating with third party datasources which does not support windows authentication like Oracle.
- Encrypt the package with "EncryptSensitiveWithPassword" or "EncryptAllWithPassword" and provide a package password each time User wants to edit/manipulate the package.
- Create a configuration file to provide the connection information during Package runtime.
More details please refer: ssis-error-code-dts_e_oledberror-an-ole-db-error-has-occurred-reasons-and-troubleshooting
Regards,
Zoe
If the answer is helpful, please click "Accept Answer" and upvote it.
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.
Hot issues October