PDF XChange Forum

Hello,
while converting a Word-2010 document with PDF-XChange 7.323 word plugin an access error for temporary file occurs, pls refer to attached screenshot.
Login has been done as user with normal access rights, read/write/list/change access to user's temp folder X:\web\ is granted, problem has been established after PDFXPRO7.exe update to v7.323 (licensed).
Tmp file is created (X:\web\PXC396C.tmp), but afterwards there must be an access issue!?
Word shows window Printing Progress: Spooling file.doc, but no response anymore.
If clicking 'OK' in Warning dialogue, pdf file is created.
Problem can be solved, if access right for user's temp folder is extended including first option "full access" additionally to read/write/list/change rights.
Administrators does not have this issue.

So, how to solve this for normal user's?
Thx and regards, Chris.

Hi pdfcoder
can you try this script to set the permissions correcty on your modified tmp folder please?
This thread describes what it is all about.
https://www.pdf-xchange.com/forum3 ... 83#p100693

-

Thanks for this hint.
On our systems all temp files are located on ramdisk X:.
After extending access rights similar to C:\Users\web\AppData\Local\Temp (= %LOCALAPPDATA%\Temp), everything works like expected.

Extending the access rights to full access had been done by: With PDFcreate!6.x it was working with read/write/list/change access rights only.
Now full access for PDFcreate!7.0.323 seems to be needed, read/write/list/change isn't enough!?

Hi pdfcoder

it looks like you did something other than what the script does. Roman, who wrote that script says it copies the permissions and that V6 and V7 require the same rights.
I will let him explain. He will post more detail soon.

Hi pdfcoder,
The original user temp directory is located in the user profile directory and thus inherits its permissions. The user profile directory (%USERPROFILE%) has a custom permission - full access for the user it belongs to. But an ordinary disk directory just inherits its permissions from the disk root and therefore does not have this specific permission. You can check this yourself.
That is why Windows users sometimes run into problems when they customize their temp directory location but do not take care of duplicating the permissions of the original temp directory. This is a general issue, not something specific to our product - any application that uses non-trivial security context manipulations might have similar problems in such a case.
As of PDF-XChange printer, it is actually a Windows system component that requires the temporary directory to have standard permissions. And the requirements for PDF-XChange V6 and V7 are the same.