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 --
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.
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)
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.
No comments:
Post a Comment