Search This Blog

2011-05-24

GAD Server Not Initialize Properly

Following will found in Genesys Agent Desktop server (GAD) log when it is not started in proper order. When accessing it using browser, error will shown in browser saying that "Login Failed. Server is already running. Server is not correctly initialized. Please contact your administrator"

The solution is to bounce the GAD server. This is a common problem if GAD server not started in correct order, such as when server reboot, VMware host rebooted, schedule reboot, server crashed, etc.


24 05 09:59:04:959 [               Outer] INFO                  ADDP  Sending init packet. Remote timeout: 250000 for tcp://gadsvr2.family.com.my:2020[Opened]/0
24 05 09:59:05:005 [b.PCT.invoker.Cfgsdk] INFO                  ADDP  Addp packet received: i from tcp://gadsvr2.family.com.my:2020[Opened]/0
24 05 09:59:05:084 [               Outer] INFO                  ADDP  Sending init packet. Remote timeout: 60000 for tcp://gadsvr1.family.com.my:5030[Closed]/1
24 05 09:59:05:115 [t/10.225.67.191:7090] WARN    Ail.Statlib.Driver  Unexpected SEvent, Unknown 23
IntValue        1
Server          2450
24 05 09:59:05:130 [ab.PCT.invoker.Omsdk] INFO                  ADDP  Addp packet received: i from tcp://gadsvr1.family.com.my:5030[Opened]/1
24 05 09:59:05:412 [      TelephonyQueue] WARN  ony.TelephonyService  Switch [Avaya_Switch] created.
24 05 09:59:05:990 [               Outer] INFO                  ADDP  Sending init packet. Remote timeout: 60000 for tcp://tserver1.family.com.my:3060[Closed]/3

No comments:

Blog Archive