" /> Problem starting G3 TServer - Genesys CTI User Forum
« previous next »
Pages: [1]   Go Down

Author Topic: Problem starting G3 TServer  (Read 4302 times)

This topic contains a post which is marked as Best Answer. Press here if you would like to see it.

Vic

  • Guest
Problem starting G3 TServer
« on: January 01, 1970, 12:00:00 AM »
Advertisement
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
Logged

Ritchie

  • Guest
Problem starting G3 TServer
« Reply #1 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....
Logged

Z

  • Guest
Problem starting G3 TServer
« Reply #2 on: January 01, 1970, 12:00:00 AM »
Check Tenant and permissions
Logged

gauthier

  • Guest
Problem starting G3 TServer
« Reply #3 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
Logged

Kim

  • Guest
Problem starting G3 TServer
« Reply #4 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.
Logged

Stephanie

  • Guest
Problem starting G3 TServer
« Reply #5 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.
Logged
Marked as best answer by on Today at 02:04:05 PM

Haldane

  • Guest
Problem starting G3 TServer
« Reply #6 on: January 01, 1970, 12:00:00 AM »
  • Undo Best Answer
    • 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.
    Logged
    Pages: [1]   Go Up
    « previous next »