" /> why I can't start GAD in SCI? but I can start it using startup.bat - Genesys CTI User Forum

Author Topic: why I can't start GAD in SCI? but I can start it using startup.bat  (Read 3065 times)

Offline kevinwang

  • Full Member
  • ***
  • Posts: 159
  • Karma: 0
Advertisement
START info in cme as below:
Working directory D:\GCTI\GAD\bin
Command Line GDesktopDriver.exe
Arguments -service GDesktop



Offline basdi2000

  • Newbie
  • *
  • Posts: 9
  • Karma: 0
Re: why I can't start GAD in SCI? but I can start it using startup.bat
« Reply #1 on: May 14, 2010, 10:07:22 PM »
Hi,

Check your JAVA_HOME directory in Environment variables. Also make sure ProcessParameters.ini file has correct path to Java.

Artur

Offline kevinwang

  • Full Member
  • ***
  • Posts: 159
  • Karma: 0
Re: why I can't start GAD in SCI? but I can start it using startup.bat
« Reply #2 on: May 20, 2010, 05:58:50 PM »
Thank your very much, it's java home directory problem, there should not be any space, I just used default installation directory for jsdk installation.

Offline mlow

  • Newbie
  • *
  • Posts: 7
  • Karma: 0
Re: why I can't start GAD in SCI? but I can start it using startup.bat
« Reply #3 on: June 24, 2010, 01:53:17 PM »
We also had this problem that ended up being caused by an incorrect IP address in the hostname table on the linux server. We did an nslookup on the server noticed the incorrect IP address then vi etc/hosts. The Apps would start ok in SCI but would not shut down. We could stop them via the command line.

Offline nino

  • Newbie
  • *
  • Posts: 1
  • Karma: 0
Re: why I can't start GAD in SCI? but I can start it using startup.bat
« Reply #4 on: June 03, 2021, 09:22:39 AM »
start it with a particular user , not system

Offline Dionysis

  • Sr. Member
  • ****
  • Posts: 408
  • Karma: 8
Re: why I can't start GAD in SCI? but I can start it using startup.bat
« Reply #5 on: June 28, 2021, 04:03:42 PM »
Environment variables for specific users are often the cause of this kind of issue.  The user that runs the LCA is how the applications will start, so you need to make sure you test from the command line with that user.
Also, pro tip - never ever ever run LCA as root.  That's just asking for trouble, even more relevant for GDA if you run that.