This is the most generic error encounters, there can be different causes for this but below one fix mine issue. Found this on community but wanted to share, it really save my day.
Siebel Server Error: SBL-SVR-00029: Internal Shared memory has not been initialized.
SYMPTOMS
Siebel Server failed to start.
- No new enterprise log was created
- Siebel Server log contained the following errors:
(SiebSrvr.log)
2010-07-13 15:03:33 1: [TCPIP-client] socket() closed descriptor = 8 from 10.1.1.51:49976 to 10.1.1.51:2320
2010-07-13 15:03:33 (scfsis.cpp (80) err=2555932 sys=0) SBL-SCM-00028: Key not found
2010-07-13 15:03:33 (listener.cpp (172) err=2555932 sys=0) SBL-SCM-00028: Key not found
2010-07-13 15:03:33 (lstnsvc.cpp (150) err=2555932 sys=0) SBL-SCM-00028: Key not found
2010-07-13 15:03:33 (scisvc.cpp (1391) err=1311765 sys=0) SBL-SVR-01045: No components are configured.
2010-07-13 15:03:33 (scfsis.cpp (274) err=1310725 sys=0) SBL-SVR-00005: Stale or invalid Task handle
2010-07-13 15:03:33 scfEventFac::s_pEvtFacLock is NULL and hence SCF event facility cannot be initialised
2010-07-13 15:03:33 (scfeventfac.cpp (3790) err=1319869 sys=0) SBL-SVR-09149: Could not initialize the event facility.
2010-07-13 15:03:33 SCFMessageFacility::s_pSCFMsgFacLock is null and hence the SCFMessageFacility cannot be initialized
2010-07-13 15:03:33 ipcFacility GetInstance called before initialization – object is null
2010-07-13 15:03:33 (scfsis.cpp (64) err=1310749 sys=0) SBL-SVR-00029: Internal: Shared memory has not been initialized.
CAUSE
Siebel Server definition is missing from Siebel Gateway Name Server Data file (siebns.dat).
Solution
Either of the following actions should resolve the issue:
A. Restore a copy of the Gateway Name Server backup file (siebns.dat).
B. Configure a “new” Siebel Server, by running the configuration wizard.
[su_divider style=”dotted”]
@AskmeSiebel