I have both Excel and SQL Server installed on the server.  I am working directly on the server. 

On the server, I can run the SSIS package directly from the catalog and it runs perfectly.  The Excel file is opened and saved back.  This just isn't executing when I run it from the SQL Server Agent.

I have a single job with one step that simply executes the SSIS package - or it says it does. It just isn't actually doing anything.  I've done everything I can think of regarding permissions, and I don't think that's the issue.  I just don't know what the problem is. 

I also tried using an Operating System Command step to run the little executable I created to open and save the file (the same .exe file that the SSIS package successfully runs) and that isn't working either.  The step succeeds, but the executable apparently isn't run.  The simple command I'm using in the job step is C:\SSRSExports\SaveFile.exe  That's the location of both the executable and the Excel file, only the date isn't being changed when I run the job the way it does when I run the executable directly.  I'm running the job as the SQL Server Agent Service Account, which has permissions set appropriately for the folder and the executable.  

I ALSO tried setting up a transact SQL step that uses cmd.exe, and that didn't work either.

So, I was trying to get around this by maybe writing a little stored procedure that ONLY opens an saves the excel file, but I can't figure out how to do that without setting things up to import and export data, which is NOT what I need to do.  This isn't a data spreadsheet.  It is a highly-formatted export from SSRS.

Any guidance would be greatly appreciated.