Initialization Error: Unable To Get The Seed From Binary File

This error occurred after upgrading Siebel to IP2015. Siebel upgrade is done successfully. Resolved Siebel Server related issues and updated WebServer files. When accessing the url we can see error message in browser --
Initialization Error: Unable To Get The Seed From Binary File

This issue occurred after the Upgrade is done to IP2015. To resolve the issue we have to create seed file and put it in bin directory under WebServer. Goto SWEApp\bin directory in WebServer and execute the below command --
seedgeneratorutil c:\Siebel\eappweb\BIN\myseed.dat abcdef
abcdef -- SWSE Cryptographic Seed, which we set during first installation of Siebel Env
It'll create myseed.dat under bin directory.

Update the eapps.cfg file with the Seed value under swe section --
seedfile = myseed.dat

Restart the webserver


For Linux: Copy libmod_swe.so from the eappweb/bin folder to the eappweb/modules directory and restart web server.

Memory fault(coredump)

This issue can occur on any Siebel Env, servers hosting on Linux. The issue can occur in an existing running env or on an upgraded env.

After starting the server, we can see the start_server command is successful but the services did not start properly.

[parthod@server1 siebsrvr]$ list_server all
Siebel Server "server1" (Enterprise "PROD_ENT")
started at Sat May 28 10:57:34 2016, pid: 8409 (Service process is not running), autostart: no

Even after stopping the server and starting it again will give error something like below --
[parthod@server1 siebsrvr]$ start_server all

Cleaning up previous execution of PROD_ENT::server1 ...

/server1/siebsrvr/bin/reset_server: line 119: 9978: Memory fault(coredump)
already stopped at Sat May 28 11:05:24 2016
Siebel Server "server1" (Enterprise "PROD_ENT")
started at Sat May 28 11:07:37 2016, pid: 10374


Even doing a clean startup(see this link), is not helping and the services are not starting properly. This issue occurs when core services are not starting properly. Even stopping the core services and starting the server will not help.

Solution -- Delete the core services directory from the server and then start the server. Core services directory is located under /server1/siebsrvr/mw/.mw/core_data
In my case, I removed the directory name server1 which was present under core_data

For further details and alternate solution see this link

not started: Could not copy service entry file into memory

After Siebel upgrade to IP2015, while starting gateway services the below error has been faced.
not started: Could not copy service entry file into memory

On checking gateway logs, the below error was found --

[parthodas@server log]$ more NameSrvr_01.log
2021 2016-05-02 04:17:19 2016-05-02 04:24:17 -0700 0000000b 001 003f 0001 09 GtwyNS 3870 1439811376 /gtwysrvr/log/NameSrvr.log 15.5.0.0 [2304
8] ENU
GenericLog      GenericError    1       0000000257270f1e:0      2016-05-02 04:17:19     (secmgr.cpp (2768) err=4597538 sys=0) SBL-SEC-10018: data source connect string or table owner is empty.
GenericLog      GenericError    1       0000000257270f1e:0      2016-05-02 04:17:19     (secmgr.cpp (2840) err=4597521 sys=0) SBL-SEC-10001: An internal error has occurred within the authentication subsystem for the Siebel application. Please contact your system administrator for assistance.
GenericLog      GenericError    1       0000000257270f1e:0      2016-05-02 04:17:19     (client.cpp (395) err=4597521 sys=0) SBL-SEC-10001: An internal error has occurred within the authentication subsystem for the Siebel application. Please contact your system administrator for assistance.
SisnTcpIp       SisnSockError   1       0000000257270f1e:0      2016-05-02 04:17:19      1448610672: [TCPIP-server] recv() failed for sd=-1 (err=9 | Bad file descriptor)
SisnTcpIp       SisnSockError   1       0000000257270f1e:0      2016-05-02 04:17:19      1448610672: [TCPIP-server] send() failed for sd=-1 (err=9 | Bad file descriptor)

Copy the svc file for gateway from the backup directory. Also, need to copy gateway.cfg file from backup directory to gtwysrvr/bin. Ideally these two files get copied from backup when upgrade is done. But sometimes, it might not due and thus lead to this error.
Then start the gateway services and it should come up without any issue.

Furthermore, this particular error can be divided into two parts --
1) not started: Could not copy service entry file into memory --- This happens when our svc file is not present or it is corrupt
2)  SBL-SEC-10018: data source connect string or table owner is empty. --- This happens when there is some issue with the Authentication system, like LDAP. In my case, svc file was not present hence further communication was failing.

Cannot open Siebel Web Template files (SBL-UIF-00276)

Sometimes, while accessing Siebel url, we might get the below error --
Cannot open file: siebsrvr/webtempl/CCPageContainer_ss.swt.(SBL-UIF-00276)

I'll get this section divided into different parts --
i) Normal environment where we are getting this error -- This error message pops up when certain webtemplate files are missing. A particular webtemplate has been modified and have not been migrated to server. Need to check for any modifications made by Developers for the webtemplate and if those have been properly migrated to the Siebel servers.
For further reference, look for Bug: 10481485. Issue related to obsolete webtemplate has been resolved under this bug.


ii) Upgraded environment to IP2015 -- This error is faced when a particular prm url is being hit. Other urls are working fine. The webtemplate is oui webtemplate and is present under ouiwebtmpl. But it is not checking under right directory. On checking, it is observed that for prm comp, HighInteractivity has been set to False. Setting it to true and bouncing the comp, resolved the issue.
Ideally, if OpenUI is Enables, comp looks for webtemplate under ouiwebtmpl. In this case, it was not happening and turning HighInteractivity to True resolved our issue.


iii) Issue with Tools or Client -- Check if the right webtemplates are available to Tools/Client. Also check if the right path has been set for Tools/Client.