-
1. Re: acrodist.exe timeout setting
Test Screen Name Jun 4, 2014 12:22 PM (in response to gpbonfanti)It's never been noted or asked in the many years its (presumably) worked this way. Unlikely to be any control, why is it an issue?
-
2. Re: acrodist.exe timeout setting
gpbonfanti Jun 4, 2014 12:32 PM (in response to Test Screen Name)We are using a program called BarTender to print to the Adobe PDF printer. Instead of re-using an existing acrodist.exe process like other programs do, it creates a new one each time. This leaves us with many acrodist.exe processes until they eventually time out. We've asked BarTender about this and I've posted a message to the Adobe forums about this but most likely there won't be a solution for it. I was hoping a workaround would be to set the acrodist.exe idle timeout to a smaller value. I'm guessing there isn't a setting for that but thought I'd ask anyway. I did look in the Adobe Distiller registry entries but didn't find it...
-
3. Re: acrodist.exe timeout setting
Test Screen Name Jun 4, 2014 2:23 PM (in response to gpbonfanti)I wonder if, rather than the app, it's the environment. Is this BarTender app running in a normal interactive session for a logged on user, or something else?
-
4. Re: acrodist.exe timeout setting
gpbonfanti Jun 5, 2014 5:52 AM (in response to Test Screen Name)Good thought but the BarTender app is running in a normal interactive session for a logged on user. On the same machine we can use Notepad to print to Adobe PDF and it re-uses the existing acrodist.exe process. I'm guessing the issue is with BarTender but since they won't look into the problem, I'm trying to come up with a work around.
-
5. Re: acrodist.exe timeout setting
Steve Cordero Jun 5, 2014 9:37 AM (in response to gpbonfanti)This information from the Acrobat XI SDK may or may not be helpful:
PDF Creation APIs and Specifications > Acrobat Distiller API Reference > Windows Messaging > Command line options
Distiller 6.0 and above support command line and WM_COPYDATA interfaces and add the --deletelog and --nosecurity switches. Options can be passed as arguments on the command line.
acrodist [switches] [inputFiles]
If any switches are present, they must come before any input files. Switches and input file names are both optional. The command acrodist by itself runs Distiller, or if a normal instance of Distiller is already running, it brings Distiller to the foreground.
The switches parameter is a list of optional commands. Either the dash or slash character can begin a switch, which is identified by a single case-independent letter. (Note, however, that the deletelog and nosecurity switches can only be preceded by a double dash (--).) There should be a space after the switch letter, and if the switch takes a parameter, another space after the parameter. The parameter should be in quotes if it contains any spaces. Do not combine switches—give each one its own prefix (- or /).
The parameter inputFiles is a list of file names, separated by spaces or commas. Spaces and commas are both legal file name characters; if a file name contains spaces or commas, enclose it in double quotes.
To process a list of PostScript files, use this syntax:
acrodist [switches] inputFiles[, inputFiles...]
The following table lists the optional command line switches.
-
6. Re: acrodist.exe timeout setting
gpbonfanti Jun 5, 2014 9:42 AM (in response to Steve Cordero)Great information, we'll pass this along to they guys at BarTender to see if there's something they can change. Thanks!
-
7. Re: acrodist.exe timeout setting
gpbonfanti Jun 5, 2014 11:43 AM (in response to Steve Cordero)It turns out that BarTender sends the print job to the Windows print spooler instead of calling distiller directly. If you have any info for this scenario then please let me know.




