I have a SSIS package that needs to read an excel (xlsx) file stored on a share on a server. The package runs flawless in Visual Studio but fails when run with the Agent on SSIS service.
I created a proxy user linked it to a credential that uses a login of a user that has access to the file and folder and under which I installed the Office Runtime (for access to the Excel file, version 16). I found out that the scheduled package runs successful when the user linked to the credential is logged on to the server on which SSIS runs. But when I log off the user the schedule fails.
Why does this user need to be logged on (have an active session) on the server for the package to run? What do I overlook here, because I don't want to consume resources with an active session on the server and prevent issues when the server reboots and the session is no restarted.
Thank you for your feedback
We're still investigating the issue. For the moment I still use the workaround of keeping an open session on the server with the user defined as the credentials for the proxy user.
But we're still investigating the route of granting the logon as batch job to the user. But for now no success.