Skip navigation
jeremiah-swanson
Currently Being Moderated

IOR files not being created

Nov 16, 2011 1:13 PM

Tags: #service #indesign_server #ior_files #windows_service

I'm currently experimenting with using the InDesignServerService (windows service) as our means of starting and managing instances of InDesign Server.

 

I seem to have it working for the most part but the IOR files are not being created and I cannot figure out why. I have been messing around with the command line arguments in the InDesignServerService MMC for quite some time with no luck. The instances seem to startup fine and show "running" in the event viewer info message.

 

Command line arguments used -

-pluginpath Server/Corba -iorfile c:\IDSQueues\Default\ior1.txt -previews

 

I've made sure the account the service is running under has writes access to the ior file path. I truely don't know what else to try or why this is happening.

 

Any help would be great! thanks!

 

FYI

 

Using InDesign Developer Server CS5 (for testing) on Windows 7 64bit.

 
Replies
  • Currently Being Moderated
    Nov 16, 2011 8:19 PM   in reply to jeremiah-swanson

    Dear Jeremiah,

     

    Please use the below code in the command line...

     

    InDesign Server Path[folder]> Indesignserver -iorfile d:\ior\ior.txt -pluginpath server\corba -port 12345

     

    definitely it would helps you. All the best...

     

    Regards

    T.R.Harihara SudhaN

     
    |
    Mark as:
  • Currently Being Moderated
    Nov 17, 2011 6:03 AM   in reply to jeremiah-swanson

    Hello,

     

    do you get any kind of error? You can use the "-LogToApplicationEventLog" parameter while starting and then take a look into the Application Log. While starting the instance normaly some events are logged. The last two are the ior content and the path where it was written to. If something went wrong you should be able to see some error instead.

     

    The "port" parameter is only needed if you're using the SOAP interface. To specify the port for CORBA you can attach the following parameter at the end (otherwise any free port is chosen randomly):

    -ORBendPoint giop:tcp:<IP|hostname>:<portNumber>

     

    This is not well documented for IDS (and that's a shame). IDS uses omniORB and that's where the parameter comes from.

     

    Good luck.

     

    PS: I'm using CS4 tough, but there shouldn't be much differences in this concern

     
    |
    Mark as:
  • Currently Being Moderated
    Dec 15, 2011 11:51 AM   in reply to jeremiah-swanson

    Jeremiah,

     

    Are you using the 32-bit service, or the 64-bit service?

     

    The screenshot above shows the 32-bit service running.  Perhaps you are configuring the 64-bit service with the MMC.

     

    -John Phillips

     
    |
    Mark as:
  • Currently Being Moderated
    Jul 30, 2012 12:13 PM   in reply to jphillips

    Did you ever find the solution to this? I am in the same boat with CS6. Everything works great from the command line, but not from the service. Even used a combination of Procmon and Security Auditing to determine that it doesn't even attempt to create the IOR files. With or without port, configuration, etc. No errors in event log, but startup messages are there.

     
    |
    Mark as:
  • Currently Being Moderated
    Jul 30, 2012 2:03 PM   in reply to RDrogo

    Ok - I just found my root cause. Posting here in case anyone else needs it.

     

    The problem was the fact that my PATH environment variable (system level, not user) was already very long, so when the service starter module went to append some extra directories to it, it hit up against the max length and ended up being truncated. I was able to verify this using process explorer. I removed some other stuff to try it out, and sure enough - IOR files aplenty.

     

    Oh - and just in case it helps, here were my instance arg strings:

     

    -iorfile F:\IDServerTests\LBQ\iors\ior_4.txt -pluginpath Server\Corba -configuration 62s_4

    -iorfile F:\IDServerTests\LBQ\iors\ior_3.txt -pluginpath Server\Corba -configuration 62s_3

    -iorfile F:\IDServerTests\LBQ\iors\ior_2.txt -pluginpath Server\Corba -configuration 62s_2

    -iorfile F:\IDServerTests\LBQ\iors\ior_1.txt -pluginpath Server\Corba -configuration 62s_1

     

    It's key to make sure you have a unique config specified, or you'll only end up with one IOR file.

     

    Hope that helps someone!

     
    |
    Mark as:

More Like This

  • Retrieving data ...

Bookmarked By (0)

Answers + Points = Status

  • 10 points awarded for Correct Answers
  • 5 points awarded for Helpful Answers
  • 10,000+ points
  • 1,001-10,000 points
  • 501-1,000 points
  • 5-500 points