using the excel.application com object in powershell won’t save a file through the task scheduler for automation.
it’s likely a dcom permissions issue. automating excel is sometimes fraught with peril…
the only way i’ve found around issues such as this is to set excel to run as a specific user through dcom permissions.
open component services (start > run, type in dcomcnfg)
if you’re using 32bit excel do this instead from a command prompt:
c:\windows\syswow64>mmc comexp.msc /32
drill down to component services > computers > my computer > dcom config
right-click on microsoft excel application and choose properties
in the identity tab select this user and enter the user that is running the task in task scheduler
when you're a little too careless about virtualizing your domain controllers, cloning, migrating, backing up and restoring, returning from vacation… Read More
systemd is new service manager for linux. it's a replacement for all previous init systems (sysv/sysvinit & ubuntu's upstart) and… Read More