2 Replies Latest reply on Jul 6, 2012 1:30 PM by brhurley

    ExtendScript Toolkit cannot launch InDesign CS6 Server

    brhurley Level 1

      I have installed the trial version of InDesign Server CS6 on Windows 2008 and am trying to run scripts against it using the ExtendScript Toolkit, but it is not working. When I select "Adobe InDesign CS6 Server" from the drop-down list in the upper left, I get an alert box that says "Cannot launch target Adobe InDesign CS6 Server!". When expanding the details box it just repeats that same message.

       

      I can start InDesign fine using either the command line or the windows service and it responds to requests. As far as I can see, it is just ExtendScript that is having problems with it.

       

      I have combed through the event logs and can't find anything there indicating what the problem might be. I have also googled everything I can think of looking for a solution with no luck.

       

      Has anyone else run into this? Any suggestions on a solution or at least where I might be able to track down a useful error message that says why it can't launch InDesign?

        • 1. Re: ExtendScript Toolkit cannot launch InDesign CS6 Server
          brhurley Level 1

          I still haven't found a solution to this problem, however I have tracked down some possibly useful information about it. Watching ProcMon while trying to launch InDesign from ExtendScript Toolkit, I see that it is looking for InDesignServer.com using the path C:\Program Files (x86)\Common Files\Adobe\InDesignServerCS6\InDesignServer.com. That's not a valid path. It is actually located at C:\Program Files\Adobe\Adobe InDesign CS6 Server x64\InDesignServer.com. Does anyone know where ExtendScript gets that path from? Is there a configuration file or registry entry somewhere that it can be corrected?

          • 2. Re: ExtendScript Toolkit cannot launch InDesign CS6 Server
            brhurley Level 1

            Just in case somebody else is having this problem and stumbles across this thread, I did find a workaround for the problem:

             

            1. Open Extendscript Toolkit, but do not try to launch InDesign from it.

            2. Run C:\Program Files\Adobe\Adobe InDesign CS6 Server x64\InDesignServer.com.

            3. Go back to ExtendScript and select InDesign.

             

            When InDesignServer.com starts up, it will recognize that there is an instance of ESTK running and attach itself to that which will allow you to debug scripts again like before.

             

            This certainly isn't as convenient as simply launching InDesign directly from ESTK like you could do in previous versions, but at least it works.