1 of 1 people found this helpful
Is your script running with full admin privileges? I recall running into this before and either the filemaker privs or windows privs on that directory were the root cause.
Other things I would check would be the windows default program association. IE making sure it's supposed to open with acrobat reader by default. Sometimes if they installed a third party app like foxit or a PDF printer like PrimoPDF, it makes the windows program associations for *.pdf do wierd things.
Sorry I don't recall the exact fix, hopefully this gives you a few more things to try.
Okay, thanks, Mike. No, it's not running with admin privs, but other users aren't having a problem. Just this one user. But we seem to have a LOT of issues with registry associations for some reason (despite being on managed desktops). I'll try both.