"VirtualServer" in eapps.cfg is not replaced by the actual Siebel Server name stored in lbconfig.txt.
(Doc ID 1493903.1)
Last updated on SEPTEMBER 22, 2017
Applies to:Siebel Financial Services CRM - Version 8.1.1  and later
Information in this document applies to any platform.
***Checked for relevance on 04-Mar-2014***
To enable Siebel Native Load Balancing, following conditions must be met.
1) [ConnMgmt] section in eapps.cfg
EnableVirtualHosts parameter is set to "TRUE".
VirtualHostsFile parameter points to the load balancing configuration file.
2) load balancing configuration file
It must be generated by "generate lbconfig" command in srvrmgr. File name can be lbconfig.txt, lbconfig.cfg, or other name as long as it matches to the path name specified by VirtualHostsFile parameter in eapps.cfg file. It can be edited to remove unnecessary entries.
Even though all of the above conditions seem to be met, web clients cannot see the login page and receive the error message "The server you are trying to access is either busy or experiencing difficulties. Please close the Web browser, open a new browser window, and try logging in again. [hh:mm:ss]"
Also, the corresponding SWSE log shows following error messages to indicate "VirtualServer" is not replaced with the actual Siebel Server name.
SBL-SSM-0044: Virtual host is invalid
SBL-NET-01020: Internal: unknown hostname
[SWSE] Set Error Response (Session: Error: 10879185 Message: Login failed attempting to connect to siebel.TCPIP.None.None://VirtualServer/SIA81/ FINSObjMgr_jpn)
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document