" /> Contact server is not starting from SCI and services but started thru start menu - Genesys CTI User Forum

Author Topic: Contact server is not starting from SCI and services but started thru start menu  (Read 4318 times)

vinodgujja

  • Guest
Advertisement

Hello All-

1.Contact server is not starting from SCI and services , But starting through start menu, what could be the problem?

vinodgujja

  • Guest
Same is the case with email server also...

Thanks in advance

Offline catanirex

  • Sr. Member
  • ****
  • Posts: 272
  • Karma: 11
How does the configuration in CME look like for these apps?
Start Info Tab -Working dir, Command Line and Command line arguments

Example
Working dir:        C:\GCTI\MCR75\Universal Contact Server\UCS
Command Line :  ContactServerDriver.exe
Command line arguments:        -service GenesysUniversalContactServer

vinodgujja

  • Guest
Hello Catanirex-

This is how  the configuration in CME look like for these apps?
Start Info Tab -Working dir, Command Line and Command line arguments

Working dir:        C:\GCTI\MCR75\Universal Contact Server\UCS
Command Line :  ContactServerDriver.exe
Command line arguments:        -service GenesysUniversalContactServer.

For Email server also:
-service GenesysEmailServerJava

Can you please let me know what could be the reason?

Offline victor

  • Administrator
  • Hero Member
  • *****
  • Posts: 1419
  • Karma: 18
Ok,

let's take a step back and think:

1. SCS uses LCA to launch your server
2. LCA issues a command
3. your application runs

here is the quick way to see what is going wrong:

1. kill your LCA
2. start LCA from command prompt so that you can see what it is doing
3. issue start command again

watch what LCA screen will show - are there any errors?

Vic

tony

  • Guest
A couple of things from me;

For the email service, it may well be functional but not shown as working.  This is because the local application (xxx.exe) may have stopped responding but one or many of the the java session(s) it continually spawns [i]could [/i] still be running... I would suggest that, if you are stopping and starting the types of applications which invoke java sessions, you leave a gap of 15 minutes (as a rule of thumb) before attempting to restart them, to ensure you are not running the same java processes concurrently.

If you have stopped the application by killing the PID on the Server (I see that you are using Windows), then it is possible that LCA may not have picked this up.  A "Best Practice" rule would be to always start/stop applications using either SCI/SCS/LCA [b]or [/b] the local Server Application but do not mix up starting and stopping using different methods - it will certainly cause less confusion!

I hope these help?

Tony