Hello Charles, many thanks for your detailed description. I thought i run exactly in that problem because the Windows user is different than the one specified in Cache (Network Account). I tried with the same user (Logged-in Windows-user = Cache Network user) ... but without any changes :-( The problem still exists ... the PopUp-Window with the error/warning-message (see below) from the program still comes up :-( Whatsoever ... i assume it also depends on the art/kind the program is stitched because i have programs who works perfectly via $zf.
Thanks and Regards... Bernd!
Charles Paik wrote:
Bernard,
It does sound pretty similar to the Adobe problem we have here. The way we got around it (and the workaround is simply a resolution, not a solution) was to have the Windows user (designated as the Network Account in the Configuration Manager) logged in to the Windows server.
Our main Windows admin account is the not same as the one we specified for the Cach� Network Account (I believe this is based on Intersystems' advice) and while our main admin is always logged in, our user for the Network Account is not. In testing the $ZF w/ Adobe we came to find out that when connected to Cach� through telnet, that specified user had to be logged into our Windows server in order for Adobe to have a (for lack of a better word) partition to load into since it is a GUI.
When using Cach� locally through a terminal session, I believe the $ZF command is executed by the Windows user who is logged in directly. But through telnet, the $ZF command assumes the identity of the Network Account and hence, expects to load the GUI into that user's "screen" or Windows session.
Like I said, it's a workaround and one we are not thrilled w/. I've never heard about this Log-On user defined in the Cach� Controller mentioned by Timur, so I'll have to check that out. But another idea we were experimenting w/ was using the RunAs DOS command so we could effectively re-direct launching Adobe into our default admin's session; however, the RunAs prompts for password so we would have to store the password on file or something.
Hope this helps.
Charles
"Bernd Mueller" <[EMAIL PROTECTED]> wrote in message news:[EMAIL PROTECTED]
Hello Timur and Charles, i want to convert a html-file to a pdf-document via a html2pdf-converter. I am evaluating and testing with "Document2PDF Pilot Trial Version" from http://www.colorpilot.com
The call is:
<prg-path>\doc2pdf.exe /nogui <SourceFile> /outfile <DestinationFile>
Charles, i thing the problem is exactly like yours! The /nogui switch means that the programm will end automativally when the coversion is done. There is a short PopUp of the GUI (it starts in the Foreground) and then it disapears when i start it via cache-terminal. When i start it via a client-telnet-session i couldn't see this PopUp but a hangig
doc2pdf-process.
Have you solved your problem with Adobe ? How ?
I also had configured a netwerk-server username and password in cache config-manager. Access to the files is sure and i think the Account has Admin rights.
How can i check if this account has the necessary privileges to execute this program ?
Thanks and Regards... Bernd!
