Dears,

I have faced related scenarios in that context for which I have managed to find a workaround, however until recently process started giving me a hard time.

My flow consists of an SQL Server Agent Job which triggers packages the contain VB Script task component to open and apply specific formatting to weekly generated Excel files. The original platform was Windows Server 2003 and all was well back then, however after the upgrade to Windows Server 2008 the job started to fail on execution noting that execution of the package from within BIDS would run with no issues. As per the research this is due to the fact that automation/unattended execution of Microsoft Office is not fully supported on Windows Server 2008, yet the creation of the 'Desktop' folder under C:\Windows\SysWow64\config\systemprofile solved the issue back then.

A few months later I faced another error when the job was triggered and I found a workaround by calling the packages in the job in 32 bit mode via command line (DTExec Util) and this worked well for around a year now... until last week upon execution, the job seems to go on forever without doing anything. Excel.exe does actually open up in the task manager processes, however the write functionality never starts maybe due to user restrictions??

Note that no windows updates or other changes have been made during last couple of weeks, I shall try to modify user permissions however not counting on that as the Excel.exe process is being triggered by Administrator user. Any suggestions are appreciated.

Regards,

Sam