Applies to:
Error Message Area:Networking Layer - NET
Version:Siebel 7.5.3
Purpose
This document is intended to provide cause and corrective action
information about Siebel Error Message SBL-NET-01023: Peer disconnected
Scope
This document is informational and intended for any user.
SBL-NET-01023: Peer disconnected
Explanation
The server has closed the network connection.
Below is a list of common causes for the error message:
1. The Web Server's Network cards did not have a Default Gateway Server IP Address configured correctly.
2. The 3rd party network connectivity software installed on the Siebel
server machine (for example Oracle's SQL*Net software and Resonate), was
not installed correctly. Additionally, the customer was encountering a
"Handshake Failed" error when trying to access the Server Administration
screens and one of the Siebel Object Managers had crashed and produced a
call stack.
3. Resonate is used for load balancing and the customer is using a
Network Interface Card (NIC) that is not certified. Additionally, the
customer has configured to use IPMP (Internet Protocol Network
Multipathing).
4. The customer had configured their Siebel application to allow for
anonymous browsing however the Anonymous Employee account GUESTCST was
not defined in the database. (Note: GUESTCST is only one possible user
name for anonymous browsing). Check the eapps.cfg file and see what
values you have defined for the AnonUserName parameter. Verify the
database user account exists in the Siebel database.
5. Resonate is used for load balancing between multiple Siebel servers
and some of the Resonate parameters and environment variables are not
configured correctly for example "Heartbeat Until down" and
RES_PERSIST_BLOCK_SIZE.
Corrective Action
Check the network configuration and restart the server process if necessary.
Below are some additional corrective actions to review and confirm:
1. Confirm the IP addresses are correct by running the ipconfig command
on the Web server machine. [Note: ipconfig exists on Windows machines
only - ifconfig may be required on UNIX machines]. Make any necessary
changes and restart the Siebel Web Server and IIS Services.
2. Use the Environment Verification Tool (EVT) to confirm that the 3rd
party network software is certified and installed properly. For
information about EVT, refer to Technical Note 467 or Siebel Bookshelf
version 7.7 > Siebel Installation Guide for (Microsoft Windows OR
UNIX): Servers, Mobile Web Clients, Tools > Verifying Your System
Using the Environment Verification Tool. If you are using Resonate for
load balancing, confirm it is installed and configured properly. You can
refer to Technical Notes 316, 543 and 419 for installation and
troubleshooting information on Resonate. Check the SRSP for a list of
certified versions and check the installation log files for any errors.
Reinstall the software if necessary.
3. If Resonate is installed, confirm the NIC card is certified by
reviewing the NIC Support Matrix document found on SupportWeb under
Product Documentation > Siebel System Requirements and Support
Platforms Guide & Miscellaneous Documentation > Network Interface
Card Support Matrix. Disable IPMP if it is enabled.
4. Make sure the value for the AnonUserName parameter exists in the
Siebel database. Or try setting the AnonUserName value to an account
that you know exists in the Siebel database. For more information, refer
to the following Siebel Bookshelf references:
- Siebel Bookshelf version 7.7 > Security Guide for Siebel eBusiness
Applications > User Administration > Configuring Anonymous
Browsing > Implementing Anonymous Browsing.
- Siebel Bookshelf version 7.5.3 > Security Guide for Siebel
eBusiness Applications > User Administration > Unregistered Users
and Anonymous Browsing > Implementing Anonymous Browsing.
5. For more information about troubleshooting and configuring Resonate, refer to Technical Note 419, 316 and 543.
Applies to:
Siebel System Software - Version: 7.8.2.3 [19221] and later [Release: V7 and later ]
z*OBSOLETE: Microsoft Windows Server 2003
Product Release: V7 (Enterprise)
Version: 7.8.2.3 [19221]
Database: Oracle 9.2.0.6
Application Server OS: Microsoft Windows 2003 Server SP1
Database Server OS: IBM AIX 5L 5.2
This document was previously published as Siebel SR 38-3196279459.
Symptoms
SBL-MBL-02087, SBL-MBL-00211, SBL-OMS-00203, SBL-SVR-01014, SBL-NET-01023We have installed SSSE in our acceptance environment, by following exactly the same process, we
try to install it into our production environment but it fails because the PIMSI Engine component
remains unavailable.
I join the log file to the SR
Cause
Configuration/ Setup
Solution
Message 1
For the benefit of other users:
Customer installed SSSE in their acceptance environment without any
problems but when they tried to install it into their production
environment, by following exactly the same process, it failed because
the PIMSI Engine component remained unavailable.
We found following errors in PIMSIEng*.log.
“An existing connection was forcibly closed by the remote host (peer)”.
SBL-NET-01023: Peer disconnected
SBL-SVR-01014: Internal: Could not send the HELLO message: (null)
SBL-MBL-51024: Opened compound file: \\MSAPP024P\WINSHARE\pimsimon.exc.
SBL-MBL-00211: Method GetRunningApps (), Error = 0x8000401A.
SBL-MBL-00211: Method RefreshAppMap (), Error = 0x8000401A.
SBL-MBL-02087: Exchange 2000 connector failed to initialize. Error = 0x8000401A.
DataMgr: Connector Manager Failed to load the connectors ErrCode: 0x7d3
SBL-OMS-00203: Error 2008 invoking method "BusSvcMgrInit" for Business Service "PIMSI Engine Service"
“Terminate process due to unrecoverable error: 4300203. (Main Thread)”
According to the Error messages knowledge base, following are the causes and corrective actions for these errors:
==================================================================
SBL-NET-01023
Cause: The server has closed the connection.
Corrective actions: Restart the server process if necessary and check the network configuration.
SBL-SVR-01014
Cause: SISNAPI hello failed. %1 in the error message is replaced by the ...
Cause: SISNAPI hello failed. %1 in the error message is replaced by the error code from the SISNAPI layer.
Corrective actions: The error is meant for internal diagnostic and
debugging by Siebel Engineering. If you encounter it, please contact
Siebel Technical Support.
=====================================================================
We got customer to check whether they have experienced any Network
problems in their environment before encountering these errors and also
whether they have any major differences between their acceptance
environment and the production environment.
Customer checked and confirmed that in the security setting for the dcom
object, the domain was missing into the user name and by adding this
domain to the user the PIMSI Engine component started correctly and
stayed in available status and the behaviour is resolved with this.
Thank you.
Oracle | Siebel Technical Support
Keywords: SSSE, PIMSI Engine component, unavailable, SBL-NET-01023,
SBL-SVR-01014, SBL-MBL-51024, SBL-MBL-00211, SBL-MBL-02087,
SBL-OMS-00203.
Applies to:
Siebel CRM - Version 8.1.1.1 SIA [21211] and later
Information in this document applies to any platform.
Symptoms
Number of srvrmgr command session (CP_NUM_RUN_TASKS for ServerMgr
component) may reach Maxtasks (20 by default) even though the number of
actual sessions are much less. As a result, following error is reported.
-------------------------------------------------
Connected to 0 server(s) out of a total of 4 server(s) in the enterprise
SBL-NET-01023: Peer disconnected
SBL-SSM-00004: SISNAPI Hello failed. The server component could be down.
-------------------------------------------------
Cause
It is possible to start srvrmgr command without /S parameter then
specify the Siebel Server name to run various operation such as "run
task". Doing so the number of active tasks on ServerMgr component on
each Siebel Server is increased. If /S parameter is specified to start
srvrmgr command, the active task count is increased only on the
specified Siebel Server. Here are some examples for each scenario.
<Example>: There are two Siebel Servers A and B. It is assumed
all srvrmgr command sessions keep running simultaneously, because tasks
are started by "run task" and they take some time to finish. Here is how
the number of active tasks on ServerMgr component is increased.
1) With /S parameter.
Number of active tasks for ServerMgr component
A B
- srvrmgr /s A 1 0
- srvrmgr /s B 1 1
- srvrmgr /s B 1 2
- srvrmgr /s A 2 2
2) Without /S parameter
Number of active tasks for ServerMgr component
A B
- srvrmgr 1 1
- srvrmgr 2 2
- srvrmgr 3 3
- srvrmgr 4 4
3) combination of 1) and 2)
Number of active tasks for ServerMgr component
A B
- srvrmgr 1 1
- srvrmgr /s B 1 2
- srvrmgr /s A 2 2
- srvrmgr 3 3
Even though all the scenario run four srvrmgr commands, the number of
active tasks for ServerMgr component have different values.
By default, Maxtasks parameter for ServerMgr component is set to 20.
If the number of Siebel Server is four and each runs five srvrmgr
command simultaneously, it reaches the maxtasks (4 * 5 = 20) therefore
starting the next srvrmgr command fails with the following error.
-------------------------------------------------
Connected to 0 server(s) out of a total of 4 server(s) in the enterprise
SBL-NET-01023: Peer disconnected
SBL-SSM-00004: SISNAPI Hello failed. The server component could be down.
-------------------------------------------------
To verify if this is the case, please monitor the value on CP_NUM_RUN_TASKS for ServerMgr component.
Solution
Here are several ways to resolve this behavior.
1) Increase number of Maxtasks parameter for component ServerMgr on each Siebel Server.
2) Specify /S parameter to start srvrmgr command.
3) Decrease the number of srvrmgr sessions that run simultaneously.
4) Use "start task" instead of "run task" to minimize the session time for srvrmgr.
Applies to:
Siebel System Software - Version: 7.5.3.5 [16183] to 8.1.1.3[21219] - Release: V7 to V8
z*OBSOLETE: Microsoft Windows 2000
Product Release: V7 (Enterprise)
Version: 7.5.3.5 [16183]
Database: Oracle 9.2.0.4
Application Server OS: Microsoft Windows 2000 Advanced Server SP 4
Database Server OS: Microsoft Windows 2000 Advanced Server SP 4
This document was previously published as Siebel SR 38-1490194987.
***Checked for relevance on 20-Oct-2010***
Symptoms
Hi,
I have configured the Web Server , Siebel Enterprise and
Siebel Server to communicate using SSL. But it doesn't seem to be able
to connect from the Web Server to the Enterprise and Server.
I get this error below.
User : SADMIN Attempting ( 7) to open a session ...
SSL not supported by server, failing connection.
SBL-SSM-00003: Error opening SISNAPI connection
Login failed for Login name : SADMIN
[SWSE] Open Session failed (0x6ce5) after 0.0057 seconds.
In
the Bookshelf, Security Guide for eBusiness Applications, on Page 70,
It mentions to Set the Additional Name Server Parameters for Siebel
Server SSL.
I am unclear on how to perform this. As there are no clear instructions.
We are using the "ePharma Object Manager (ENU)".
I tried to set the "Is Using Secure HTTP Connection = TRUE " but the value cannot be commited.
Please help.
Cause
Incorrect SSL setup.
Solution
For the benefits of other users:
Customer intends
to configure SSL for Siebel Enterprise and Siebel Server and set the
parameter "Communication Transport” to “SSL” for the respective Object
Manager. Error “SBL-NET-01023: Peer disconnected” reported.
Solution:
The
root cause of the issue is customer just rename the *.cer file
generated by Win2k Certificate Authority to *.pem file. It is documented
in Security Guide for Siebel eBusiness Applications that
1) Certificate files must use either ASN (Abstract Syntax Notation) or PEM (Privacy Enhanced Mail) format.
2) Private key files must use PEM format.
You
can't just rename the file name to .pem extension as the format of the
certificate file is encoding with different method. There are some tools
available on the Internet that can help to do the conversion; one of
the tools is Win32OpenSSL.
After corrected the certificate and
private key files; customers are able to connect and login with SSL
enabled. However, errors “SBL-NET-01559: Internal Error: CN entry does
not match hostname” reported in SWSE log.
This benign error
indicated that the value entered for common name when creating a new
certificate does not match the actual hostname. The normal practice for
web server certificate is it will tie to the actual hostname and there
should be a valid DNS entry. The error can be ignored and if there is
concern please generate a new certificate and enter the actual hostname
when prompted for the common name.
Thank you,
Applies to:
Siebel CRM - Version 7.8.2 [19213] to 8.1.1 SIA [21111] [Release V7 to V8]
z*OBSOLETE: Microsoft Windows Server 2003
Product Release: V7 (Professional) and later
Version: 7.8.2 [19213]
Database: Microsoft SQL Server 2005
Application Server OS: Microsoft Windows 2003 Server
Database Server OS: Microsoft Windows 2003 Server
This document was previously published as Siebel SR 38-3304776353.
*** Checked for Relevance on 11-Sep-2012 ***
Symptoms
SBL-NET-01023, SBL-SCB-00011, SBL-SSM-00004, SBL-SSM-00006
We have launched Siebel today. Users are seeing 4 problems:
1. Server busy or problem experienced browser error
2. White screen with progress bar
3. Siebel splash screen with progress bar (no login box)
4. Users get into the system and then get booted out.
When first launched, we had serious avaikability issues as above.
We then changed the following settings:
1. MAX TASKS params for all object managers from 20 to 100 (as recommended in PRR) except fo UK OM which was changd to 200.
2. MAX TASKS for connection broker from 1 to 2.
Since these changes users have been able to access, but within last 1 hour we have again seen the same issues.
Cause
Encryption for the communication between Siebel web server and Siebel servers is set to MSCRYPTO
Solution
Message 1
As per the client description their siebel web client became unavailable at certain times.
After investigations the symptoms were found to be as follows:
On the siebel application server there was a siebmtshmw process that
became to use 100% CPU. This process did not became unresponsive but
instead to became idle when no requests where processed it went to
100%CPU. On a 4 processor box when there were 4 siebmtshmw processes
that went in this state the machine begun to respond very slow this
resulting in dropping new sessions and overall log responses to
incomming requests.
On the web server machine (IIS) there was present the same situation
(the siebel extensions out of process begun to consume 100%CPU)
The thread that consumed CPU was identified from the performance monitor
logs and then core dump where taken from these processes. The thread
was a communication thread between the siebel web extensions (SWSE) and
object manager (OM). The call stack for the corresponding thread was:
sslcnapi!compress_write+0xdb
sslcnapi!zlib_inflate+0x8d
sslcnapi!CSSSISConn::_DecodeRawMsg+0x158
sslcnapi!CSSSISConn::SisAsyncThreadMain+0x8d
sslcosd!OSDThreadStart+0x1c0 sslcosd!OSDNTThreadStart+0xc
msvcr70!beginthreadex+0xba
kernel32!GetModuleFileNameA+0xeb
...
The relevant line in the communication call stack is
CSSSISConn::_DecodeRawMsg. The customer had the encryption for the
communication set to MSCRYPTO. This encryption is not largely used or
recommended by Siebel. After setting the encryption to NONE the problem
did not re-occurred.
Resolution:
The customer choose to check if they need encrypted communication
between the web server and the application servers and if this is the
case use SSL instead.
אין תגובות:
הוסף רשומת תגובה