SBL-NET-01020: Internal: unknown hostname

Applies to:

Siebel System Software - Version: 7.8.2.5 [19227] and later   [Release: V7 and later ]
z*OBSOLETE: Microsoft Windows 2000
Product Release: V7 (Enterprise)
Version: 7.8.2.5 [19227]
Database: Oracle 9.2.0.8
Application Server OS: Microsoft Windows 2000 Server SP 4
Database Server OS: Microsoft Windows 2003 Server SP2

This document was previously published as Siebel SR 38-3358339279.

Symptoms

Hi,
During the upgrade we have installed our web servers on a new machines. After moving external web server to DMZ zone we cannot log to echannel , eservice or wireless application.
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.[21:02:58]
The web server log shows:
GenericLog    GenericError    1    0    2007-05-23 22:23:02    (smconn.cpp (271) err=1801020 sys=1300230) SBL-NET-01020: Internal: unknown hostname
GenericLog    GenericError    1    0    2007-05-23 22:23:04    (smconn.cpp (271) err=1801020 sys=1300230) SBL-NET-01020: Internal: unknown hostname
GenericLog    GenericError    1    0    2007-05-23 22:23:07    (smconn.cpp (271) err=1801020 sys=1300230) SBL-NET-01020: Internal: unknown hostname
GenericLog    GenericError    1    0    2007-05-23 22:23:09    (smconn.cpp (271) err=1801020 sys=1300230) SBL-NET-01020: Internal: unknown hostname
GenericLog    GenericError    1    0    2007-05-23 22:23:11    (smconn.cpp (271) err=1801020 sys=1300230) SBL-NET-01020: Internal: unknown hostname
GenericLog    GenericError    1    0    2007-05-23 22:23:11    (ssmsismgr.cpp (635) err=5600003 sys=0) SBL-SSM-00003: Error opening SISNAPI connection.

.....cont

Cause

Configuration/ Setup

Solution

ObjMgrSessionLog    Error    1    0    2007-05-23 22:23:11    Login failed for Login name : SiebelAnontst
ProcessPluginState    ProcessPluginStateError    1    0    2007-05-23 22:23:11     3908: [SWSE] Open Session failed (0x56bf) after     11.2381 seconds.
......
ProcessPluginRequest    ProcessPluginRequestError    1    0    2007-05-23 22:23:56     3548: [SWSE] Failed to obtain a session ID. Login failed attempting to connect to %1
ProcessPluginRequest    ProcessPluginRequestError    1    0    2007-05-23 22:23:56     3548: [SWSE] Set Error Response (Session: Error: 00022207 Message: Login failed attempting to connect to siebel.TCPIP.None.None://xxxxxxxx:2321/sieb78tst/WirelessServiceObjMgr_enu)


We have 2 load balanced application servers running call center OM that are accessed via internal web server and one external web server that connects to echannel, eservice and Siebel wireless using the external web server (xxxxxxxx) .  
Before moving the external web server to the dmz we could successfully test the access to those 3 applications using internal network.
We have opened port 2320 and 3 Static ports for each application (specified in the OMs configuration).
The network configuration seems to be fine.
The xxxxxxxx server referenced in the error log is our apps server
Please could you help us with this problem.
Please note attached files.

Comment:

According to the description:

The client had moved the web server to a DMZ and since that moment they haven’t been able to access eChannel , eService and Wireless applications.
They have opened port 2320 and 3 Static ports for each application and they were using a load balancing solution.

Solution:
   
    When a load balancing solution is used the web server must be able to access the SCBroker port on each Siebel Server. After the ScBroker(2321) port was opened they have been able to access the applications.

Thank You,

Applies to:

Siebel System Software - Version: 7.5.2.7 SIA [15058] and later   [Release: V7 and later ]
Oracle Solaris on SPARC (64-bit)
Product Release: V7 (Enterprise)
Version: 7.5.2.7 [15058] Com/Med
Database: Oracle 8.1.7
Application Server OS: Sun Solaris 8
Database Server OS: Sun Solaris 8

This document was previously published as Siebel SR 38-1013977611.

Symptoms

SBL-SRB-00040, SBL-NET-01020We are installing our production environment, with many Siebel Servers on solaris machine(s)
Some errors appear in the Gateway and SRBroker logs. See attached.
Symptoms:
- When connecting via Dedicated Web Client it is not possible to view the Servers in the Server Admin screens- error message is "No connections found to any active servers".
- When connecting via command line srvrmgr from one of the Siebel Server boxes I can see all Servers up, running and all Components healthy.
- When connecting via Web Client (this is possible via the PRMManager OM) I get the strangest view: I can only see two Siebel Servers: the SRVREAI1 and the one my connection was picked up by. The other ones are listed but all fields (Status, etc.) read blank.
-
- When doing all the steps above against Dportal (another environment) everything looks fine. Also, the two errors do not appear in the Dportal environment.
Please check with our TAM Emidio Cignarella
Regards

Cause

Configuration/ Setup

Solution

Message 1

The Server Request Broker (SRBroker) log showed the error message:

GenericLog      GenericError    1       2003-05-23 14:35:28     (srbthrd.cpp 44(2431) err=1801020 sys=0) NET-01020: Internal: unknown hostname
GenericLog      GenericError    1       2003-05-23 14:35:28     (srbthrd.cpp 44(2431) err=5700040 sys=1) SRB-00040: can't open asynchronous SISNAPI connection

Resolution:
The /etc/hosts file of siebel Server(s) did not report the host name(s) related to ip addresses.
Adding the host names to the /etc/hosts resolved the reported behavior.


Siebel Technical Support

Keywords: name resolution, SRBroker, log file, hostname, host, unix, solaris

ymptoms

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 unpublished
Bug: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 \. 

Applies to:

Siebel Financial Services CRM - Version 8.1.1 SIA [21111] and later
Information in this document applies to any platform.

Symptoms

 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)

Cause

 After some review, the cause is found that there are some invalid character in load balancing configuration file (lbconfig.txt) as below.

<lbconfig.txt>
・ｿ#This is the load balance configuration file generated by the Siebel srvrmgr "generate lbconfig" command.
#It contains two sections. Section one contains load balancing rules to be used by Siebel session manager.
#Section two is intended for 3rd party load balancers. Before modifying the content of this file please
#read the chapter on SWSE configuration in the Siebel Bookshelf.

#Section one -- Session Manager Rules:
VirtualServer=1:jw3s8111:2321; 3:jw3s8112:2321;


On the first line, there are some invalid characters before "#" sign. Therefore this line is treated as the actual parameter line instead of a comment, with invalid contents. Therefore the rest of settings are ignored and "VirtualServer" in eapps.cfg is not replaced.

In this case, lbconfig.txt was edited to remove unnecessary server entry. However, the editor used for this operation did not recognize lbconfig.txt was UTF-8 encoded file. Therefore the first three characters (Byte order mark or BOM that consists of hexadecimal 'ef bb bf' in UTF-8 encoding) were converted to (invalid) characters.

Solution

 Once these invalid characters are removed from lbconfig.txt file, "VirtualServer" in eapps.cfg file is replaced correctly so that web clients can connect to either jw3s8111 or jw3s8112 in the round robin fashion.

Applies to:

Siebel System Software - Version: 7.7.2 SIA [18325] to 8.1.1.3 SIA[21219] - Release: V7 to V8
Oracle Solaris on SPARC (64-bit)
Product Release: V7 (Enterprise)
Version: 7.5.3 [16157] Auto
Database: Oracle 9.2.0.6
Application Server OS: Sun Solaris 8
Database Server OS: Sun Solaris 9

This document was previously published as Siebel SR 38-2564725051.

***Checked for relevance on 06-Oct-2010***

Symptoms

Folllowing upgrade from 753 to 77 we have got our siebel servers back on line but am having problems connecting with the web client. Have attached web server logs, web config files, web server logs, eapps and sia, cfg files.

Please advise soonest. thanks.

Cause

Incorrect lbconfig setting

Solution

For the benefits of other users:

Customer having login issue after upgraded Siebel application from 753 to 77. SWSE logs reported following error which indicated the cause of the connection issue.

GenericLog    GenericError    1    0    2005-10-07 14:40:43    (smconn.cpp (395) err=1801020 sys=1300230) SBL-NET-01020: Internal: unknown hostname

eapps.cfg showed EnableVirtualHosts set to True and component connect string has VirtualServer configured where lbconfig.txt has the following configured.

VirtualServer=2:1:chqs07005:2321;2:chqs07006:2321;
#Component Rules:
/gmitprdent/edealerObjMgr_enu/=chqs07006:2321;chqs07005:2321;gmitprdsrvr:2321;
/gmitprdent/eautoObjMgr_enu/=chqs07006:2321;chqs07005:2321;gmitprdsrvr:2321;
/gmitprdent/edealerObjMgr_fra/=chqs07006:2321;chqs07005:2321;gmitprdsrvr:2321;
/gmitprdent/eautoObjMgr_fra/=chqs07006:2321;chqs07005:2321;gmitprdsrvr:2321;
#Server Rules:
*/!1.*=chqs07005:2321;
*/!2.*=chqs07006:2321;

Resolution:

Verify and make sure that hostnames chqs07005, chqs07006 and gmitprdsrvr are all DNS resolvable (using nslookup) to the correct IP addresses from the web server and correct the component rules where hostname gmitprdsrvr shall be removed as it is not in the VirtualServer entries.

Thank you,