Problem with Acrobat 5.0 running on a Windows 2003 terminal server

[Acrobat-User@adobeforums.com]

Hi,

We have a Windows 2003 terminal server with Office XP and Acrobat 5.0.5 installed.

We are only able to create PDF files if there is an administrator logged onto the console.

This poses problems because:

1. We don't really want an administrator logged onto the console all the time (even if it is locked).
2. If something happens and the account is logged out (server restart, etc) then Acrobat breaks again.

What can I do to fix/avoid this problem? Thanks in advance.

[MarkATS@adobeforums.com]

What can I do to fix/avoid this problem?




I think Acrobat 6.0.1 may be a solution.

[Acrobat-User@adobeforums.com]

Hi, I have tried Acrobat 6.0 Trial version but I get the same problem. Is there a trial version for 6.0.1?

[MarkATS@adobeforums.com]

No, there isn't.

[Nathan_Strong@adobeforums.com]

We are only able to create PDF files if there is an administrator logged
onto the console.




That's correct. This will always be the case until the day Adobe releases a version of ACROTRAY.EXE that runs as a Windows service.

Currently, the Adobe PDF printer (or Acrobat Distiller printer in 5.x) communicates with Distiller via a TSR called ACROTRAY.EXE. This TSR runs automatically when you log in locally.

In order for the Distiller/Adobe PDF printer to work in a WTS environment, ACROTRAY.EXE has to be running in a local context on the server. Since ACROTRAY does not run as a service, that means you need to have an admin account logged in locally at the server at all times.

Nathan

[Acrobat-User@adobeforums.com]

Thanks Nathan.

Looks like we'll have to look into getting volume licenses for installing on individual workstations.

[Ian_Mellors@adobeforums.com]

you would need those anyway, as Acrobat is strictly single user licencing. You should have a licence for every user irrespective of how you impliment the installation .....

[YoJoe]

Just as a suggestion, you may want to try creating a service that runs under a domain account and have that service load the executable. Make sure that the domain account is an administrator on the machines that are loading the executable.

[Ian_Mellors@adobeforums.com]

hmm, that reminds me, some time ago there was a 'wrapper' that was part of the MSDN developer's kit that allowed an exe to run as a service, might work, any developers care to comment?

[Acrobat-User@adobeforums.com]

The funny thing is that, the acrotray.exe loads with every user that is logged on... Scenarios of when it works and when it doesn't:

Works:

- If any user logs on locally onto the console, they can make PDF files (even if they aren't administrators)
- Administrator connects through terminal session - works regardless of whether there is a user or not logged onto the console

Doesn't work:

- Non-admin user logs on through a terminal session, and there is no user logged in on the console
- Non-admin user logs on through a terminal session, and there is a non-admin user logged on in the console

[aapg@united.net@adobeforums.com]

You can try to set the acrotray.exe to start from the schedular and loggin in as SYSTEM. I ran across an artical that suggest this as one possible resolve.

[Acrobat-User@adobeforums.com]

Hi aapg, I tried your suggestion but looks like it didn't help. :(