Applies to:
Siebel System Software - Version 7.7.2 [18325] to 8.2.2 SIA[22320] [Release V7 to V8]z*OBSOLETE: Microsoft Windows 2000
Product Release: V7 (Professional)
Version: 7.8.2.3 [19221] FRA
Database: Oracle 9.2.0.6
Application Server OS: Microsoft Windows 2000 Server SP 2
Database Server OS: HP-UX 11i
***Checked for relevance on 07-Feb-2013***
Symptoms
SBL-SSM-00044, SBL-SSM-00006During benchmark tests to simulate login of numerous users, we experienced that after reaching one limit, no connections are allowed anymore. (the limit is not the same for each test)
The contengency seems to be at Web Server level, the connection attempt doesn't reach the Siebel Server.
The following error were reported in the SWSE logs:
Code= SBL-SSM-00044: Virtual host is invalid.
Solution
Message 1
The error message "SBL-SSM-00044: Virtual host is invalid" usually points to a problem with the configuration of the eapps.cfg file or lbconfig.txt file used for load balancing.It was found that the Server SIDs in the Session Manager Rules under Section One of the lbconfig.txt file required reconfiguration. To verify the correct Server SIDs log into Server Manager at the enterprise level. Then run the following command to output the IDs
srvrmgr> list server show SBLSRVR_NAME, SV_SRVRID
More details on how to structure the lbconfig.txt file can be seen in the document "Siebel System Administration Guide > Structure of the lbconfig.txt File" on SupportWeb.
The customer was implementing Siebel Native Load-Balancing however they had configured Section Two of the lbconfig.txt file which is only used for Third Party Load Balancer Rules, so they also removed these references.
Following these changes there were no more errors experienced.
Applies to:
Siebel Reports - Version: 8.1.1.3 SIA[21219] and later [Release: V8 and later ]Information in this document applies to any platform.
Symptoms
When running BI Publisher reports it was found that normal reports run from the UI would execute completely but that scheduled reports would fail.Upon examination of the BI Publisher xdo.log the following error messages could be found :
[090811_090327227][][STATEMENT] initConfig(): config file used :null
[090811_090327227][][STATEMENT] initCustomFactories(): loading custom delivery channels :{}
[090811_090327228][][STATEMENT] initConfig(): config input stream was used.
[090811_090327228][][STATEMENT] initCustomFactories(): loading custom delivery channels :{}
[090811_090327228][oracle.apps.xdo.delivery.DeliveryManager][STATEMENT] initConfig(): loading default properties :{}
[090811_090327228][][EVENT] SiebelValidator(Properties prop)
[090811_090327229][][EVENT] endpoint:http://siebel.oracle.com/bipeai_enu/start.swe?SWEExtSource=WebService&SWEExtCmd=Execute
[090811_090327229][][EVENT] adminUsername:SADMIN
[090811_090327230][][EVENT] adminPassword:********
[090811_090327230][][EVENT] Endponit contains no UserName or Password, appending it with Admin's
[090811_090327243][][EXCEPTION] AxisFault
faultCode: {http://xml.apache.org/axis/}HTTP
faultSubcode:
faultString: (500)Internal Server Error
faultActor:
faultNode:
faultDetail:
{}:return code: 500
<html><head><title>Message:</title></head>
<body><h1>Message:</h1>
<p>An
error occurred while trying to process your request. This error
indicates a problem with the configuration of this server and should be
reported to the webmaster (along with any errors listed below). We
apologize for the inconvenience</p>
<p>Error(s):<ol><li>Login
failed attempting to connect to
siebel.TCPIP.None.None://ABC:1534/xyz/BIPEAIObjMgr_enu<li>Login
failed.
SBL-SSM-00044: Virtual host is invalid.
</ol></p>
</body></html>
{http://xml.apache.org/axis/}HttpErrorCode:500
(500)Internal Server Error
at org.apache.axis.transport.http.HTTPSender.readFromSocket(HTTPSender.java:744)
at org.apache.axis.transport.http.HTTPSender.invoke(HTTPSender.java:144)
at org.apache.axis.strategies.InvocationStrategy.visit(InvocationStrategy.java:32)
at org.apache.axis.SimpleChain.doVisiting(SimpleChain.java:118)
at org.apache.axis.SimpleChain.invoke(SimpleChain.java:83)
at org.apache.axis.client.AxisClient.invoke(AxisClient.java:165)
at org.apache.axis.client.Call.invokeEngine(Call.java:2784)
at org.apache.axis.client.Call.invoke(Call.java:2767)
at org.apache.axis.client.Call.invoke(Call.java:2443)
at org.apache.axis.client.Call.invoke(Call.java:2366)
at org.apache.axis.client.Call.invoke(Call.java:1812)
at com.siebel.apps.shared.xmlp.security.BIPSiebelSecurityWSPortStub.authenticate(BIPSiebelSecurityWSPortStub.java:298)
at oracle.apps.xdo.security.SiebelValidator.validate(SiebelValidator.java:124)
at oracle.apps.xdo.servlet.security.SecurityManagerImpl.getSiebelPrincipal(SecurityManagerImpl.java:1366)
at oracle.apps.xdo.servlet.security.SecurityManagerImpl.impersonate(SecurityManagerImpl.java:496)
at oracle.apps.xdo.servlet.scheduler.XDOJob.execute(XDOJob.java:325)
at org.quartz.core.JobRunShell.run(JobRunShell.java:195)
at org.quartz.simpl.SimpleThreadPool$WorkerThread.run(SimpleThreadPool.java:520)
[090811_090327245][oracle.apps.xdo.servlet.scheduler.XDOJob][EXCEPTION]
[ID:651] Unexpected exception occurred while running the job.
AxisFault
Cause
The xdo.log file shows the following error message being returned from the Siebel EAI Object Manager :Login failed attempting to connect to siebel.TCPIP.None.None://ABC:1534/xyz/BIPEAIObjMgr_enu<li>Login failed.
SBL-SSM-00044: Virtual host is invalid.From this it was confirmed that a custom EAI Object Manager was being used for which a custom virtual directory had been defined in the eapps.cfg file. Reviewing the configuration for this it was established that whilst the configuration showed that a VirtualServer should be used (through the 'EnableVirtualHosts=true' parameter) no VirtualServer existed in the lbconfig.txt with the name that was referenced in the ConnectString, in this case 'xyz'.
Solution
In order to resolve this behaviour it was necessary to ensure that the ConnectString for the virtual directory definition in the eapps.cfg included a reference to a valid VirtualServer definition in the lbconfig.txtFor further information on this topic please review the following documentation in the Siebel Bookshelf :
Siebel System Administration Guide > Configuring the System Architecture > Configuring Siebel Server Load Balancing
Applies to:
Siebel CRM - Version 8.0 [20405] to 8.1 [21039] [Release V8]Information in this document applies to any platform.
***Checked for relevance on 01-Mar-2013***
Symptoms
When load balancing is implemented, the following error is seen in the browser:
"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 ..."
The following errors are reported in the SWSE log files:
SBL-NET-01020: Internal: unknown hostname
SBL-SSM-00044: Virtual host is invalid.
This occurs even when lbconfig.txt contains IP addresses instead of hostnames.
Changes
Implementing Load Balancing triggered the problem.Cause
There is an error in the eapps.cfg file created by the SWSE installation. This has been identified in unpublishedBug:10534386 VirtualHostsFile refers to lbconfig.cfg instead of lbconfig.txt
Solution
Making the following change to SWSE_ROOT/bin/eapps.cfg resolves the issue:[ConnMgmt]
…
VirtualHostsFile = $(SWSE_ROOT)/admin/lbconfig.txt
That is, change lbconfig.cfg to lbconfig.txt and make sure that the path contains / instead of \.
No comments:
Post a Comment