Unable to run jscript on IDServer thru Extendscript

[Bart_Devos]

Hi,

I'm working on Mac osx with IndesignServer CS5.

On my local machine i'm able to run a javascript on IndesignServer (launched "standalone" with ./InDesignServer) thru ESTK 3.5.x. On a production machine this trick doesn't seem to work. I can select the target "Adobe Indesign CS5 Server", the chain-symbol is initially green, but when i try to run a simple script, i get the message "Cannot execute script. Target Adobe InDesign CS5 Server provides no engine for debugging.". If i try to load the object-model viewer for Indesign CS5 Server, it shows nothing.

Googling around learned me to execute the script: "

BridgeTalk.__diagnostics__;"

There is a target Indesign server with following information:

indesignserver-7.0: IDLE

Path = /Library/InDesignServer.command

Display Name = Adobe InDesign CS5 Server

MsgAuthentication = ON

MsgDigest = ON

ESTK = ON

BundleID = com.adobe.InDesignServer

Status = IDLE

Info:

Version = 2.0

Build = ES 4.1.23

Next serial number = 12

Logging: = OFF

Now = 13:52:22

Messages:

Message Version = 2.05

Authentication = ON

Digest = ON

indesignserver-7.0: IDLE

Thread: indesignserver-7.0#thread

Avg. pump interval = 101ms

Last pump = 1ms ago

Ping: 7

ECHO_REQUEST: ECHO_RESPONSE

Timeout = undefined

Handler = undefined

STATUS: IDLE

Timeout = undefined

Handler = undefined

MAIN: MAIN

Timeout = undefined

Handler = installed

LAUNCHED: LAUNCHED

Timeout = undefined

Handler = installed

DIAGNOSTICS: DIAGNOSTICS

Timeout = undefined

Handler = installed

INFO: INFO

Timeout = undefined

Handler = installed

SETUPTIME: thread=0ms, left=46ms

Timeout = undefined

Handler = undefined

ExeName = InDesignServer.command

Installed: 0

Running: 2

The path to IndesignServer is not correct. It is not installed beneath "/Library" but in the default "/Applications" folder.

I re-installed ESTK several times with the same result.

Any idea how i can correct this? Is there a predefined order to install these products?

Any help would be much appreciated!

Kind regards,

Bart Devos.

[Bart_Devos]

Any ideas?

[John Hawkinson]

How are you starting ID server?

I noticed that if I ssh into a machine and start ID server, then the ESTK on the console cannot access the ID server instance.

If I start it interactively from Terminal.app, I can.

p.s.: JScript is a microsoft language that is almost but not the same as JavaScript. Please don't use the terms interchangably.

[Bart_Devos]

Thanks for your response, John.

Sorry, i didn't know that JScript was a seperate language.

I start in both cases Indesignserver directly with Terminal.app (not thru ssh):

cd /Applications/Adobe InDesign CS5 Server/

./InDesignServer

On my development machine, i can run scripts with ESTK on IDS but not on the production machine.

Kind regards,

Bart Devos.

[John Hawkinson]

Weird. I don't know. I assume you haven't edited the configuration.

You might ensure that Scripts/startup scripts/ConnectInstancesToESTK.js is present and functioning.

Otherwise search for differences in the filesystems?

I don't have much IDS experience.

[Harbs.]

This sounds very odd.

Some random thoughts:

Do startup scripts work?

Either something is wrong with the installation, or the regular scripting interface is somehw turned off.

Maybe IDS is caught in a hard loop? Is there startup scripts that might be causing this?

If there's some way you can check what app.serverSettings.javascriptUi is set to...

Harbs

[absqua]

I have no problem running scripts in the ESTK with a noport instance launched with the shell script, and I do get the same output from the BridgeTalk Diagnostics (including the bogus "Path = /Library/InDesignServer.command").

Do you maybe have a #target directive at the top of your script that's messing things up? Or have you tried "#target "indesignserver""? Or launching the instance with a port number ("./InDesignServer -port 10555") and then using "#target "indesignserver_configuration_10555" at the top of your script?

Jeff

[Bart_Devos]

Thank you, guys, that's a lot of usefull input!

First of all, i do think that all necessary startupscripts work, at least if the logging tells me right:

Thu Aug 11 17:14:38 2011 INFO [javascript] Executing File: /Applications/Adobe InDesign CS5 Server/scripts/startup scripts/ConnectInstancesToESTK.js

Thu Aug 11 17:14:38 2011 INFO [javascript] Executing File: /Applications/Adobe InDesign CS5 Server/scripts/converturltohyperlink/startup scripts/ConvertURLToHyperlinkMenuItemLoader.jsx

Thu Aug 11 17:14:38 2011 INFO [javascript] Executing File: /Applications/Adobe InDesign CS5 Server/scripts/converturltohyperlink/ConvertURLToHyperlinkMenuItem.jsxbin

Thu Aug 11 17:14:38 2011 INFO [javascript] Executing File: /Applications/Adobe InDesign CS5 Server/scripts/Export As XHTML/startup scripts/XHTMLExportMenuItemLoader.jsx

Thu Aug 11 17:14:38 2011 INFO [javascript] Executing File: /Applications/Adobe InDesign CS5 Server/scripts/Export As XHTML/XHTMLExportMenuItem.jsxbin

I have no custom startup scripts.

There is 1 main difference between the two: My development machine runs a debugversion of IDS and the productionmachine a regular release version. On older CS3 and CS4 installs i did the same thing on a release version without problems.

The production machine runs simultaneously corba and soap instances. But even when i kill that instances, it doesn't work.

The filesystems are the same (OSX 10.6.6) but the hardware differs.

I didn't run scripts with a #target directive, but i will try your suggestions, absqua.

I' ll try if i can get the serversettings thru a corba instance in java.

I'll keep you informed.

Thank you for the input, guys!

Bart Devos.

[Guest]

I tried with the #target directive, but it didn't work.

I'm beginning to suspect that, if the standalone indesign is not installed (for CS5), it's simply not possible to run scripts with extendscript on IndesignServer CS5. I encountered the same problem with different customer installs. Apparently there are some libraries or scripts that are only installed with the CS5 standalone version. This is new to CS5. On CS3 and CS4 installs i didn't have that problem.

I can't expect customers to buy an Indesign standalone license just to add Extendscript functionality to their, already expensive, IndesignServer license.

I can make a corba or soap client to run testscripts, but then i lack debug functionality. This is really annoying... :-((

My problem is that i have to be able to debug on site, because of server specific problems that i can't reproduce on my local install.

[John Hawkinson]

I'm beginning to suspect that, if the standalone indesign is not installed (for CS5), it's simply not possible to run scripts with extendscript on IndesignServer CS5. I encountered the same problem with different customer installs. Apparently there are some libraries or scripts that are only installed with the CS5 standalone version. This is new to CS5. On CS3 and CS4 installs i didn't have that problem.

I'm sure that's not it. My ID Server test machine has Server CS3, CS4, CS5, and CS5.5, but no InDesign Desktop. Though it does have InCopy CS3 and CS5, I guess that could be a factor. But I'm a little skeptical...

[Also, I would imagine, if that were really the problem, you might be able to install Desktop ID CS5 without a serial number and just not launch it...]

[Guest]

I can indeed try with a trialversion. Thanks for the suggestion!

[Harbs.]

I haven't tried on a Mac, but on my Windows server, it can definitely connect without Desktop being installed.

Harbs