6 Responses to Run LiveCycle PDF Generator ES2 as ‘Local System’ Account on Windows Server 2008

  1. Colin Robinson says:

    Should this also work on Windows Server 2008 R2? x64? We have that error, but all your suggestions in place. Working with support, but was hoping to ask directly since this fits our issue so precisely.

    • Jayan Kandathil says:

      Colin:

      Yes, I have it working on Windows Server 2008 R2 x64. Support for Windows Server 2008 R2 started with ES2 SP1. Does the System Readiness Tool (SRT) script report any errors or warnings?

  2. Gil says:

    You said, “…try running the appserver as a Windows service running as the ‘Local System’ account with the service ‘allowed to interact with desktop’.” We have found that this is the only way to resove the problem that we’re having using Windows Server 2008 R2 x64. However, running as Local System isn’t sufficient because we need to access remote file systems and hence need to be running as a domain user that has permissions to those remote file systems. There is no way to give “Local System” permission to our file shares. Is there another way around this problem? We’ve been battling this issue for a couple of months now. To get around it in our dev environment we run LiveCycle manually (run.bat -c lc_turnkey -b 0.0.0.0) as the domain user and it works. We’ve also found a strange work-around where we first run the service as “Local System” and then restart the service running as our domain user… and that seems to work as well (until we reboot the box and then we have to go back through the process of switching to “Local System” and back to domain user). Obviously, neither of these work-arounds are going to work in production.

    • Jayan Kandathil says:

      Gil:

      If the network share is a Windows file share, Windows will allow you to add the SYSTEM account of any domain computer running PDF Generator (COMPUTERNAME$) to the SHARE list. You will have to provide Read and Write permissions to this SYSTEM account. This has worked in our Engineering lab. There has also been reports that this won’t work if the network share is hosted on NAS devices.

  3. Joe Crowther says:

    Been tearing my hair out over this error message, was getting a CLASSPATH error to start with that was rectified when I re-booted the server (what’s all that about). Anyway I’m gonna give this a shot as Adobe haven’t come back to us yet…

  4. gour says:

    try running the appserver as a Windows service running as the ‘Local System’ account with the service “allowed to interact with desktop”.
    Really helped a lot….