Terminal Server in session

[LStuckey]

I have an environment with Windows 2k3 and Citrix Metaframe XP. PrimoPDF is loaded on the server. When a user prints through a session, the Primo box appears on the Console. Primo will generate a test page correctly if I do it on the console. I have tried this through RDP and ICA sessions. I have given users modify permissions on the folder C:\Program Files\ActivePDF. I also checked the ghostprinter settings in the registry and they are correct as well.

Any suggestions are appreciated.

[Douglas Saltsman]

There's been a lot of work to get primo to perform properly on citrix servers and nothing seems to do the trick. The problem is the user context and permissions of the various components that primo uses to create pdfs. At this time there is no workaround.

[LStuckey]

I have turned on the debug log file and tried again. I noticed that the USERPROFILE is the Local Service and I have checked the Run as User box on the port. I also see myself as the PRIMOMON_USER. Have you tried substituting the USERPROFILE variable for the profile?

I also noticed that C:\Program Files\ActivePDF is not in the PATH. Could this make a difference?

Thanks

[MichaelAllen]

I'm running this under Win2000 Terminal Services and have this blank page problem as well. After reading all the info and trying the various suggestions, the problem still exists. I have some additional information that may tweak somone's mind:

I *can* also run it without "run as user" checked, and get it to pop up on the Admin screen, and get a PDF. Also, it runs just fine under the Admin account. But, running as another user (even with admin rights) I still get the blank page problem with a file of 722 bytes.

After turning on the "debug" information and examining the output, I have noticed that PrimoMon seems to be unaware that a required process is running. Here is the text from the debug log:

-----start log paste-----
PrimoMon WritePort: about to write 4096 bytes to port.
PrimoMon check_process: process isn't running.
PrimoMon check_process: flushing child stdin to unblock WriteThread.
::
::
::
::
PrimoMon WritePort: Process not running. Returning TRUE.
Ignoring 4096 bytes

PrimoMon Cancelling print job
PrimoMon EndDocPort: starting
PrimoMon EndDocPort: process finished after 0 seconds

PrimoMon EndDocPort: 0 bytes written to printer
PrimoMon EndDocPort: ending
-----end log paste-----

So, I think the question is: How can we make this thing aware that the process (whatever it is) is actually running (and can be checked for).

Thoughts?

Cheers,
Mike