An SSIS package is invoked via DTEXEC.EXE from a web application. The package uses a File System Task to make a copy of an Excel template file to be used as the Excel desti
Using Process Monitor reveals that ISServerExec.exe is trying to save a buffer to C:\Users\Default\AppData\Local\Microsoft\Windows\Temporary Internet Files. When the limited user account is given access and permissions under C:\Users\Default, everything works.
This explains why an interactively logged-in user or a local admin account was able to write Data Flow records to the Excel file, but a regular batch login was not able to do so. This is an undesirable behavior of the SSIS Excel Destination.
SSIS package works fine in BIDS for loading excel file with more than 5000 rows but failed when same package runs in SQL server Agent Job under proxy account. Main cause of this is that for large file SSIS process use C:\Users\Default location to buffer data. So Proxy account needs write access on this folder location. Package works fine in JOB too after this…