Thanks for the input:
Setting the Start-in path didn't help
The user I'm running as is not on the machine but one on the domain and has adminstrator privileges on the machine. I'm sure this has something to do with it.
Note that the perl script runs, but an interesting bit is this: if I choose "Run with highest privileges" Word starts and hangs. But if I don't choose this, Word does not start at all. All the event log shows is that the perl script successfully ran and is unaware of the Word instance.
So I think I just need to plug away at this permissions thing until I can find something that works. Maybe I'll try creating an admin user on the machine and run the task as that user. (somebody else created the one user account that's currently on the machine).
In reply to Re^2: Win32::OLE from Task Scheduler
by alafarm
in thread Win32::OLE from Task Scheduler
by alafarm
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |