SBL-GEN-09603: Unable to connect to named pipe

Applies to:

Siebel Remote - Version 8.0.0.6 SIA [20423] to 8.1 [21039] [Release V8]
Information in this document applies to any platform.

***Checked for relevance on 30-Aug-2012***

Symptoms

We are trying to run the Database Extract for our developers. It
worked for two users but is not working for other users.  It looks like
it uses a lot of I/O on the DB server and finally crashed.


The following error messages are found:

GenericLog GenericError 1 000000054a0405f4:0 2009-05-08 14:35

:32 (scfmsgfac.cpp (805) err=9603 sys=0) SBL-GEN-09603: Unable to connect to

named pipe.



ScfMsgFacLog SCFMsgFacError 1 000000054a0405f4:0 2009-05-08 14:35

:32 SBL-GEN-09603: Unable to connect to named pipe.

Cause

The cause of this issue is due to problems with Server Database.

Solution

The following are the steps to fix the issue:

1. Run the Db statistics to keep the stats up-to-date.

2. Remove “dicdata.dat” from the Siebel server

3. Start the application and login as ‘SADMIN’ user

4. Run new database (GenNewDB)

5. Perform the extract for the developers

Applies to:

Siebel System Software - Version: 8.0.0.2 [20412] and later   [Release: V8 and later ]
HP-UX Itanium

Symptoms

Crash of Server task persistence component is observed.  If it is
reaching more than 1 GB and crashed the component, you may see the
following lines logged:



ScfMsgFacLog SCFMsgFacError 1 00000003492d0a5c:0 2008-11-26 17:22:50 SBL-GEN-09603: Unable to connect to named pipe.

GenericLog
GenericError 1 00000003492b6e7e:0 2008-12-01 18:29:00 (ipc.cpp (597)
err=1181399 sys=0) SBL-NET-01751: The system was unable to allocate
sufficient memory for the specified operation.
IPCLog IPCError 1
00000003492b6e7e:0 2008-12-01 18:29:00 [6] Error occured while
reading/decoding a message from the pipe, rc2 = 1181399, sysError = 0,
msgBuf = "SBL-NET-01751: The system was unable to allocate sufficient
memory for the specified operation."


This is causing crash
of server task persistence component on the Siebel server and requires
restart of Siebel service to restart this background component.

Cause

Cause is due to missing OS patches required for the server platform to run Siebel.

Solution

1. Perform a Siebel EVT output on the server. Refer to Environment Verification Tool (EVT) Overview (Doc ID 477105.1).


2. Ensure that all server requirements are met.


In this case, the HP server is missing the following OS patches as
mentioned in the Siebel System Requirements and Supported Platforms
Guide. Once applied, the crash no longer happen.
PHSS_31853
PHSS_31851
PHSS_32765
PHSS_31855

References

NOTE:477105.1 - Environment Verification Tool (EVT) Overview

NOTE:567662.1 - Error message in Siebel Server component log files: SBL-GEN-09603: Unable to connect to named pipe

Applies to:

Siebel CRM - Version: 8.0 [20405] to 8.0.0.10 SIA [20436] - Release: V8 to V8
Information in this document applies to any platform.

Goal

What is the reason for the following error message in many of the Siebel 8.0 SIEBEL_ROOT/siebsrvr/log files?

"SBL-GEN-09603: Unable to connect to named pipe".

Solution

This is a known defect in Siebel 8.0 where SBL-GEN-09603 occurs in the component log files.

The error is benign and can be ignored.