I'm encountering two distinct errors when attempting to manually execute or schedule SSIS packages on my SQL Server 2019. Despite thorough checks on permissions and configurations, these errors persist, preventing any SSIS package from running. I'm seeking insights or solutions to overcome these hurdles.
Error 1: COM Class Factory Access Denied
This error comes when the SSIS package is started by the SQL Job with the SQL Server Agent
Retrieving the COM class factory for component with CLSID {6E8597AE-3486-4838-A8E0-F5C683618DF4} failed due to the following error: 80070005 Access is denied. (Exception from HRESULT: 0x80070005 (E_ACCESSDENIED)).
Error 2: COM Component Instance Creation Failure
This error comes when the SSIS package is manually started from the SSIS catalog.
Creating an instance of the COM component with CLSID {6E8597AE-3486-4838-A8E0-F5C683618DF4} from the IClassFactory failed due to the following error: c0010014 Exception from HRESULT: 0x80070005 ; Exception from HRESULT: 0xC0010014;
Troubleshooting Steps Taken:
- The packages are executed manually over my account or scheduled with the SQL Server Agent.
- The account that tries to execute the packages has the ssis_admin permission and can access the SSISDB.
- I already tried to deploy the package with the target versions 2019 and 2022.
Questions:
- What could be causing these access denial and COM component instance creation errors specifically in the context of MSSQL Server 2019 and SSIS packages?
- Are there known compatibility issues or configurations unique to SQL Server 2019 that might be contributing to these errors?
- What additional troubleshooting steps or configurations should I consider to resolve these errors and enable the successful execution of SSIS packages?
The problem was a missing Windows permission for the executing user.
We created a new blank Windows user and a corresponding Proxy User.
Important was den Windows user role that we gave him.