An old principle of computer science did hit me on this one: Garbage in, Garbage out.
The problem is solved, and the reason was that the path argument was faulty…
Therefore, I did miss something…
I fell victim to this a couple of days ago in a similar instance while trying to open a file. The error report should be modified to reflect that the filepath is not legit. The "system security settings" blurb sends people on a wild goose chase of setting of priviledges, disclosing documents, and changing security settings in their preferences. Luckily, a few people on here already knew of the issue and pointed me in the right direction.
First, I thought that there is not really any connection between this statement and the problem described.
However, at a second thought, it is.
The connection is that the error message provided by Acrobat is COMPLETELY, AND TOTALLY WRONG!!!!
In both cases, the correct error message should be something like "filespec invalid"!
Besides making the "security guys" look "good", those misleading error messages are of no use. Acrobat is a development tool, and as such, error messages MUST be as precise as possible.