" /> LCA Connecting to Wrong SCS - Genesys CTI User Forum

Author Topic: LCA Connecting to Wrong SCS  (Read 4648 times)

Offline PFCCWA

  • Hero Member
  • *****
  • Posts: 655
  • Karma: -7
LCA Connecting to Wrong SCS
« on: May 18, 2017, 09:27:12 AM »
Advertisement
Hello,

I have installed LCA (64bit) on a server (win2008r2) which has network connectivity on both production and preproduction environments.
When I start the service, it connects with the production backup SCS - even though I connected it with the preproduction config server during installation.
It was originally deployed with a connection to production but was removed so not sure why it is still connecting to production SCS (albeit backup).
logs below:

09:44:48 GPRERFORM: Local OS is 'Microsoft Windows Server 2008 R2 Standard x64 Edition,  (build 7600), 64-bit'
09:44:48 WMI initialized successfully.
09:44:48 GPERFORM initialized successfully.
09:44:48 UDP port 4999 is opened for hangup detection
09:44:48.670 Std 05060 Application started
09:44:48.670 Std 08005 No connections to LCA on host 'GENESYS_HOST' from SCSs.
09:44:48 Client: new client 596 connected.
09:44:48 Client's IP-address: x.x.x.x:49213
-AI[t/o:31000,trace]-<-596 @09:44:48.8580
-Ai[596]->-596 @09:44:48.8580
09:44:48 CREATE SCSRequester (socket:596, 'SCS_BK')
09:44:48.858 Std 08004 The host 'GENESYS_HOST' is under control of Management Layer. SCS 'SCS_BK' has connected from the host 'x.x.x.x:49213' on the socket 596.
09:44:48 SCS_BK: 09:44:48 [RequestGetHostInfo], gpf_method=
09:44:58 State of system NTP service <W32Time> has changed to 'APP_STATUS_RUNNING'.
-AP[1]-<-596 @09:45:13.7880
-Ap[1]->-596 @09:45:13.7880

Environment:
Production
SCS
SCS_BK

Preproduction
SCS_T
SCS_BK_T

thanks,

Offline Kubig

  • Hero Member
  • *****
  • Posts: 2755
  • Karma: 44
Re: LCA Connecting to Wrong SCS
« Reply #1 on: May 18, 2017, 09:33:07 AM »
What is the host configuration in Genesys env? What SCS is configured there?

Offline PFCCWA

  • Hero Member
  • *****
  • Posts: 655
  • Karma: -7
Re: LCA Connecting to Wrong SCS
« Reply #2 on: May 18, 2017, 09:38:23 AM »
In production env:
The host is configured with SCS
I have removed the LCA port on the host config (is 0 rather than 4999) but not disabled.

Same in Prepreoduction:
The host is configured with SCS_T
The LCA port is set as 4999.

thanks,

Offline vmc

  • Full Member
  • ***
  • Posts: 112
  • Karma: 0
Re: LCA Connecting to Wrong SCS
« Reply #3 on: May 18, 2017, 09:49:54 AM »
Any hosts file changes been done on that particular server?

Sent from my Redmi Note 3 using Tapatalk


Offline PFCCWA

  • Hero Member
  • *****
  • Posts: 655
  • Karma: -7
Re: LCA Connecting to Wrong SCS
« Reply #4 on: May 18, 2017, 09:53:57 AM »
we had the windows firewall disabled, nothing else.

thanks,

Offline Kubig

  • Hero Member
  • *****
  • Posts: 2755
  • Karma: 44
Re: LCA Connecting to Wrong SCS
« Reply #5 on: May 18, 2017, 10:15:02 AM »
Check the SCS logs as the SCS is connecting to the LCA, not vice-versa.

Offline n3vek7

  • Full Member
  • ***
  • Posts: 137
  • Karma: 3
    • ITKB
Re: LCA Connecting to Wrong SCS
« Reply #6 on: May 23, 2017, 02:07:13 AM »
Look at the "host" object in GA/GAX. This is where the port (usually 4999) and the SCS controlling the selected is set.

Offline catanirex

  • Sr. Member
  • ****
  • Posts: 272
  • Karma: 11
Re: LCA Connecting to Wrong SCS
« Reply #7 on: May 24, 2017, 07:09:08 AM »
A host can only be configured in one Genesys environment
So it is best to remove it from the environment were it is not needed

Offline PFCCWA

  • Hero Member
  • *****
  • Posts: 655
  • Karma: -7
Re: LCA Connecting to Wrong SCS
« Reply #8 on: May 24, 2017, 07:11:36 AM »
I believe the issue is caused by renaming the host, thus causing the issue against the SCS.
agree on the latest post that we should only have it defined within one env only.

thanks,

Offline cavagnaro

  • Administrator
  • Hero Member
  • *****
  • Posts: 7641
  • Karma: 56330
Re: LCA Connecting to Wrong SCS
« Reply #9 on: May 24, 2017, 09:42:08 PM »
Check windows service parameters
Full uninstall and reinstall will be best approach

Enviado de meu E6633 usando Tapatalk