>>>Are files on a network? Is user logged in?
>>
>>The files are there - I can testify to that. When I run it manually, they're found, opened, converted - all under the same login as the one used for the scheduled task.
>>
>>And the task is set to run regardless of whether the user is logged in or not, and it errors the same both ways.
>>
>SNIP
>
>I'm confused, I thought I read in another message in this thread that it worked if the user is logged in? BTW, I'm wondering if any group policies are in effect that may be an issue? Another option is to try applying the GPO setting via Computer configuration, Windows settings, Security settings, Local policies, User right assignment "logon as a batch job" for the user account on the OU where the machine is? Another thing is the problem with using Word via COM - it requires c:\windows\syswow64\config\systemprofile\desktop to exist doesn't it? If you create it, does it make any difference?
Between what? :)
I created it and now it seems to work, at least when I'm logged in and click Run in the scheduler. We'll see tonight, when it runs unmanned, but my bet is that this fixed it, because until now I was getting the same error both ways and now I don't.
This is indeed M$ mumbo jumbo, the bathroom light switch is in the garage. Even funnier, I tried to create the directory from the command window (aka power shell), and I didn't have the rights. Then I thought, well, maybe it already exists, so I went down the path, step by step, and twice (at config and systemprofile) it said that I don't have the rights to access that folder - do I want to give myself the rights, yes/no?... And all it took was a click on yes. Funny guys those Redmondians, they'd do anything to get one more click out of me, and to prevent me from doing anything rough, like doing things from a command line or in a batch. Sometimes I think they are sworn to prevent any attempt to automate things - everyone should click and click and click.
Knocking on wood (genuine wood clogs #45, which should be size 11 or 12 in the US), so far so good.
Of course, this doesn't answer the initial question: why does Word automation work when I run it manually, but didn't when run from Task Scheduler? Ah... M$.
