SSIS package with Microsoft Office 12 ACE OLEDB driver resulting to 'Unexpected Termination' status when executing from SSISDB catalog

Question

We are trying to run SSIS package to read Access Database (.mdb) files using Native OLE DB\Microsoft Office 12 Access Database Engine OLE DB Provider in the Source Connection Manager. This package ran successfully from Visual Studio 2019 and also from SSISDB catalog in lower end servers.

However, executing the package in higher environments resulted in 'Unexpected Termination' status in SSISDB catalog without any error message. Tried changing different properties available in Source Connection Manager but all resulted in the same 'Unexpected Termination'.

Debugging it with help of DBA, we found out that the package executes successfully if the executor/caller of the SSIS package has admin privileges(like the DBA) in the server. As it turns out the successful execution in lower environments was also because of the admin privileges the executor had in the server. Revoking the admin privilege in lower environment(UAT) also seemed to show the same status.

Is the admin privilege an absolute necessity to run packages with ACE OLE DB providers? Or are there any missing areas we need to check?

Any answers or ideas would be very helpful.
Thanks.

Answer 1

Hi @Gagan Shrestha,

Is the admin privilege an absolute necessity to run packages with ACE OLE DB providers

Not the admin permission, but the account used to run the package need to have permission to access to read Access Database (.mdb) files.

You may consider using proxy account to run the job.

Here is an official documentation for your reference: create-a-sql-server-agent-proxy

For more information, see running-a-ssis-package-from-sql-server-agent-using-a-proxy-account.

Regards，

Zoe Hui

---

If the answer is helpful, please click "Accept Answer" and upvote it.