GenericLog GenericError 1 0005930e59d32554:0 2017-10-10 00:10:37 (bsvcmgr.cpp (932) err=1310827 sys=0) SBL-SVR-00107: Internal:The configured component is not based upon a CSSService

GenericLog GenericError 1 0005930e59d32554:0 2017-10-10 00:10:37 (bsvcmgr.cpp (1044) err=1310827 sys=0) SBL-SVR-00107: Internal:The configured component is not based upon a CSSService

GenericLog GenericError 1 0005930e59d32554:0 2017-10-10 00:10:37 (smimtsrv.cpp (1203) err=1310827 sys=0) SBL-SVR-00107: Internal:The configured component is not based upon a CSSService

SmiLayerLog Error 1 0005930e59d32554:0 2017-10-10 00:10:37 Terminate process due to unrecoverable error: 1310827. (Main Thread)

GenericLog GenericError 1 0000000759dc0cfc:0 2017-10-10 00:10:43 (scfdata.cpp (9624) err=1319736 sys=0) SBL-SVR-09016: Failed to get task instance: task number 23068693.  The task may have exited or does not exist.

srvrmgr > create component definition WfProcMgrADP for component type BusSvcMgr component group Workflow run mode Batch full name "Workflow Process Manager ADP" description "Executes real-time Business ADP Processes" with fixparam ServiceName="Workflow Process Manager"

srvrmgr > enable compdef WfProcMgrADP


<a href="https://www.sejda.com/mgl/compress-pdf-online">Compress PDF</a>

SBL-SRM-00016: Unable to initialize the Database environment -- Unable to start common api

I upgraded the Env to IP2016 with patchset7 on Windows 2012 R2. The installation and configuration was successful. On starting the Enterprise, I can see the processes are not getting created properly. On checking the logs, I can see multiple SvrTaskPersist & SvrTaskPersist logs. 

In these Logs I can see below error --

GenericLog GenericError 1 0000267559780d78:0 2017-07-26 15:56:36 (srmconn.cpp (908) err=1313725 sys=0) SBL-SVR-03005: No server connect string for Siebel Component SRBroker in Siebel Enterprise SBA_82_TEST, Siebel Server SIEBELSERVERSrmLayerLog Error 1 0000267559780d78:0 2017-07-26 15:56:36 Please check whether SRBroker is running on server SIEBELSERVER in enterprise SBA_82_TEST.

On checking SRBroker & SRProc logs, I can see below error --

GenericLog GenericError 1 0000265159780d78:0 2017-07-26 15:55:36 (srpdb.cpp (1000) err=2097168 sys=0) SBL-SRM-00016: Unable to initialize the Database environment -- Unable to start common api

This error can occur due to multiple reasons. I'll put step by step debug method here. Hope this helps.

1) Check if DB connectivity is proper. Check odbcsql connectivity

2) Check if you are using 32-bit client

3) If Unix server, then check .odbc.ini file and all its parameters

4) if SADMIN & SIEBEL user has sse_role assigned and password is not UNLIMITED

5) Login to srvrmgr and check if you can see the server. Set server servername for all the servers configured. This will check if all the servers are configured properly.

srvrmgr> list server

SBLSRVR_NAME  SBLSRVR_GROUP_NAME  HOST_NAME        INSTALL_DIR        SBLMGR_PID  SV_DISP_STATE  SBLSRVR_STATE  START_TIME           END_TIME  SBLSRVR_STAT
US
------------  ------------------  ---------------  -----------------  ----------  -------------  -------------  -------------------  --------  ------------
---------------------
SIEBSERVER                          HOSTNAME  D:\sba81\siebsrvr  4960        Running        Running        2017-07-27 07:53:40            16.7.0.0 [23
057] LANG_INDEPENDENT

1 row returned.

srvrmgr> set server SIEBSERVER

set server SIEBSERVER

           *
Do this for all the servers. If this error is coming, then either the siebns.dat is corrupted or the configuration was not proper. Reconfigure your Enterprise.

6) If all the servers are properly configured, then check the DSN setting.
srvrmgr> list param DSConnectString for named subsystem ServerDataSrc

PA_ALIAS                                                                      PA_VALUE

                          PA_DATATYPE                      PA_SCOPE                         PA_SUBSYSTEM                     PA_SETLEVEL
   PA_DISP_SETLEVEL                                               PA_EFF_NEXT_TASK  PA_EFF_CMP_RSTRT  PA_EFF_SRVR_RSTRT  PA_REQ_COMP_RCFG  PA_NAME

----------------------------------------------------------------------------  -----------------------------------------------------------------------------
---------------------------------------  -------------------------------  -------------------------------  -------------------------------  ---------------
----------------  -------------------------------------------------------------  ----------------  ----------------  -----------------  ----------------  -
---------------------------------------------------------------------------
DSConnectString                                                               DBCONN

                          String                           Subsystem                        Datasources Subsystem            Enterprise level
   Enterprise level set                                           Y                 N                 N                                    Data source Conn
ect String


1 row returned.

Here ServerDataSrc is incorrect. It should be the EnterpriseName_DSN.
change param DSConnectString=SBA_82_TEST_DSN for named subsystem ServerDataSrc

7) Check the USERNAME for the Enterprise and the value should SADMIN.
list parameter Username for server SIEBSERVER

8) Also check in SvrTaskPersist & SvrTaskPersist logs, if below error is found -
ORA-28365: wallet is not open --- We have to make sure that Wallet is open for all Siebel DBs

9) Even if error is not found, check with DBA if DB Wallet is in open mode. 
Also, check if Case Sensitivity is enabled for ids. Ask DBA to disable the Case Sensitivity, till the issue is resolved.

10) Parallel check if the 32-bit version of Oracle Client is installed and not 64-bit. Also, there should be only version of Oracle Client and that should be 32-bit.

SBL-SMI-00094: Internal: Could not get the IP address

This issue was faced when Siebel application was upgraded along with DB upgrade & OS upgrade. The Siebel services were starting and getting killed after sometime. On checking logs, we could see the below errors -
[parthodas@server1 log]$ more TEST_ENT.server1.log
2021 2016-06-22 01:40:26 2016-06-22 01:40:39 -0700 00000007 001 003f 0001 09 SiebSrvr 0 3385 1439811376 /server1/siebsrvr/enterprises/TEST_ENT/server1/log/TEST_ENT.server1.log 15.5.0.0 [23048] ENU
ServerLog       ServerStartup   1       0000ec04576952b3:0      2016-06-22 01:40:26     Siebel Enterprise Applications Server is starting up
GenericLog      GenericError    1       0000ed02576952b3:0      2016-06-22 01:40:27     (smilobj.cpp (1101) err=1376350 sys=1) SBL-SMI-00094: Internal: Could not get the IP address: Internal: gethostbyname_r ()failed with error. (%sysError)
GenericLog      GenericError    1       0000ed02576952b3:0      2016-06-22 01:40:27     (smilobj.cpp (396) err=1376350 sys=0) SBL-SMI-00094: Internal: Could not get the IP address: Internal: gethostbyname_r ()failed with error. (%sysError)

Siebel upgraded to IP2015. DB upgraded to 12c. OS was upgraded to Linux6. On checking for solutions, nothing fruitful was found. We run the startup script in debug mode to check where it is getting stuck.

Solution:- We need to add one more line at siebenv.csh file. This will help is resolve the issue. Edit siebenv.csh file and add below line --
setenv RESOLV_MULTI off

Siebel server not coming up after Upgrade

After upgrading Siebel to IP2015, the siebel servers are not coming up.  The svc service for Siebel server is starting and after sometime, it is getting killed. Only watchdog process is running. Other processes(like siebmtsh or siebmtshmw or siebproc, etc.) are not starting. Once checking services, we see the below details --
 [parthodas@server1 siebsrvr]$ list_server all
Siebel Server "server1" (Enterprise "TEST_ENT")
started at Wed Jun 22 00:59:19 2016, pid: 2146 (Service process is not running), autostart: no

Issue:- On starting the server, the services are getting killed. No log file is getting created.
The issue is related to encryption issue. With IP2015, Siebel has changed the encryption method from RC4 to AES. So, the old password set at the enterprise level won't work. We need to set the password at the enterprise level and serve level.

• Start Gateway service
• Once Gateway is up, connect to Srvrmgr at enterprise level
                 srvrmgr /g <gatewayhost> /e <enssterprise> /u SADMIN /p SADMIN
  And update enterprise password as below
                 change ent param Password=SADMIN
• Once password is updated, create siebel service file
• Delete the Siebel Server system service using the following command (on Windows, this requires being logged in as user Administrator, or a username that belongs to the Administrators group AND User Agent Control (UAC) disabled):
  siebctl -d -S siebsrvr -i "EnterpriseName_SiebelServerName" (Please change enterprise name and Siebelservername according to your environment)
• Create new siebel service file
  siebctl -h SIEBSRVR_ROOT -S siebsrvr -i "EnterpriseName_SiebelServerName" -a -g "-g GatewayServerHostname:port -e EnterpriseName -s SiebelServerName -u sadmin" -e sadmin

NOTE:--In Windows machine, under certain situation, creation of new Siebel Server service may fail with the following error.

siebctl: Add Service error 1703955

It occurs when the extra registry key exists. Here are the steps to find the and fix it.

•  - Run regedit.
• Locate the registry key HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\_BKP_siebsrvr_EnterpriseName_SiebelServerName
  Example: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\_BKP_siebsrvr_sia81_app01
• Export the key for backup reason
• Delete the key

Once it is done, 'siebctl -a' should be able to create new Siebel Server service.

For further details look into the Oracle doc ID 1957428.1.