July 25, 2018 at 9:48 am
I have a package that has run every two hours for years. It suddenly stopped working and I haven't been able to track down why.
Running Win server 2012 R2, SQL Server 2014 and developing SSIS packages with VS 2013.
The package copies an Excel .xls (32 bit) template file to an export directory, and then does a series of data queries to populate 3 worksheets.
Yesterday afternoon we suddenly started receiving the error message below:
Executed as user: (domain AD id, that has admin rights). The process could not be created for step 1 of job 0xXXXXX (reason: %1 is not a valid Win32 application).
If I run the package in VS, it works fine, both from my desktop and if I'm logged in to the DB server. This only happens when running from a job in SQL Server Agent.
Nobody, that I'm aware of, installed any new software, changed any system settings, or otherwise did anything at this time that would cause this. We do have IT at a higher level of the organization that pushes patches without us knowing, but the software update log didn't show anything. The same error is happening with packages that import and export Excel data on this same DB instance, and other instances that run on the same server.
All other scheduled job are running fine, including jobs that use .xlsx (64 bit) Excel worksheets.
Any help is greatly appreciated.
Viewing 0 posts
You must be logged in to reply to this topic. Login to reply