Genesys CTI User Forum

Genesys CTI User Forum => Genesys CTI Technical Discussion => Topic started by: Vic on January 01, 1970, 12:00:00 AM

Title: Problem starting G3 TServer
Post by: Vic on January 01, 1970, 12:00:00 AM

Hi, I was wondering if any one knows how to fix this problem:
Requesting PrimaryApp information...
not found
Requesting host information...
success (LCA port: 4999)
Requesting tenant information...
success (DBID: 101, name: Resources, password: (len=0))
Requesting switch(bydbid) information...
ERROR: switch(bydbid) object not found
FATAL: cannot continue missing Switch
Thu Apr 24 19:48:32 2003.740 Standard tomcat TServer_G3_test GCTI05062 Application ini
tialization failed, reason incomplete configuration
@19:48:32.7405 [5062] TServer initialization failed, reason [incomplete configuration]
(conn_cleanup) clearing timers...
...1 timer(s) cleared
...0 background timer(s) cleared

Obviously, I have switch assigned to Tserver and Tserver assigned to switch in CME.
The version for config server is 6.5.000.08

Thanks,

Vic

Title: Problem starting G3 TServer
Post by: Ritchie on January 01, 1970, 12:00:00 AM

Is config server running? Host information OK? Have you checked the DB to make sure the data is not corrupt? App and Switch name spelled correctly with no spaces?
Not sure what else....

Title: Problem starting G3 TServer
Post by: Z on January 01, 1970, 12:00:00 AM

Check Tenant and permissions

Title: Problem starting G3 TServer
Post by: gauthier on January 01, 1970, 12:00:00 AM

Hi VIC,
I've seen this problem before, I even think I found the answer in the forum but can't remember the title of the subject. Anyways you need to upgrade you config server. That should resolve it.

Gauthier

Title: Problem starting G3 TServer
Post by: Kim on January 01, 1970, 12:00:00 AM

I had a similar problem before.
What we did was drop the current CME and then rebuild the whole thing. I recall that when we asked Genesys about it, we were told that if we use configuration wizard with CME on SQL server it is possible for our CME to get corrupted.

Title: Problem starting G3 TServer
Post by: Stephanie on January 01, 1970, 12:00:00 AM

DITTO.
We were using 6.5.000.08 with SQL server and we had our configuration manager environment get corrupted almost weekly. Upgrade. Upgrade. Upgrade.

Title: Problem starting G3 TServer
Post by: Haldane on January 01, 1970, 12:00:00 AM

On the security tab in the tserver application make sure the user default and system are there. Then make sure both accounts exist on the security tab of the switch folder.