问题 : Siebel Server does not start after changing the SADMIN password on Siebel 8.1.1
2012-03-26 14:21
597 查看
问题 : Siebel Server does not start after changing the SADMIN password on Siebel 8.1.1
Customer changed the sadmin's password following the Siebel Security Guide > Changing or Adding Passwords > Changing Passwords > Changing System Administrator Passwords on Microsoft Windows, but after changing the password the Siebel Server did not come up
.
In the Siebsrvr.log file it was found the following error message:
GenericLog GenericError 1 00000002499b0e08:0 2009-02-17 16:41:28 (scmnsclnt.cpp (135) err=2555922 sys=0) SBL-SCM-00018: Could not open connection to Siebel Gateway configuration store (siebel03:2320).
The following errors were just a symptom of the failure to connect to the Siebel Gateway:
GenericLog GenericError 1 00000002499b0e08:0 2009-02-17 16:41:28 (scisvc.cpp (1391) err=1311765 sys=0) SBL-SVR-01045: No components are configured.
GenericLog GenericError 1 00000002499b0e08:0 2009-02-17 16:41:28 (scfsis.cpp (274) err=1310725 sys=0) SBL-SVR-00005: Stale or invalid Task handle
ScfEventLog SubEvtFacFatal 0 00000002499b0e08:0 2009-02-17 16:41:28 scfEventFac::s_pEvtFacLock is NULL and hence SCF event facility cannot be initialised
GenericLog GenericError 1 00000002499b0e08:0 2009-02-17 16:41:28 (scfeventfac.cpp (3790) err=1319869 sys=0) SBL-SVR-09149: Could not initialize the event facility.
ScfMsgFacLog SCFMsgFacFatalError 0 00000002499b0e08:0 2009-02-17 16:41:28 SCFMessageFacility::s_pSCFMsgFacLock is null and hence the SCFMessageFacility cannot be initialized
IPCLog IPCFatal 0 00000002499b0e08:0 2009-02-17 16:41:28 ipcFacility GetInstance called before initialization - object is null
GenericLog GenericError 1 00000002499b0e08:0 2009-02-17 16:41:28 (scfsis.cpp (64) err=1310749 sys=0) SBL-SVR-00029: Internal: Shared memory has not been initialized.
Cause
The issue was due to the new security feature that was introduced on Siebel 8.1.1 to avoid access to the Gateway Server without being properly authenticated.
There are now in Siebel 8.1.1 user and password information in the Windows registry for the Siebel Server service. This can be verified by on "Path to executable:" field on General tab for the respective Siebel Server service in Administrative Tools > Services.
See the example below:
C:\sia81\siebsrvr\bin\siebsvc -s siebsrvr -i Siebel_app01 -a "-g localhost:2320 -e Siebel -s app01 -l ENU -u SADMIN -ep 9ntkUOUf" -t 120 -h C:\sia81\siebsrvr
Solution
Follow the instructions below to reflect the sadmin's password to all Siebel Serves in the Enterprise, i.e. repeat the process on all Siebel Servers in the Enterprise.
a) Delete the Siebel Server service
syntax:
siebctl -d -S siebsrvr -i "<enterprise name>_<siebel server name>"
example:
siebctl -d -S siebsrvr -i "SBA_81:XXXX"
b) Restart the machine
c) Recreate the Siebel Server service providing the new password, it will be encrypted by siebctl.
syntax:
siebctl -h %SIEBEL_ROOT% -S siebsrvr -i "<enterprise name>_<siebel server name>" -a -g "-g <gateway hostname>:<port#> -e <enterprise name -s <siebel server name> -u sadmin" -e <new password> -u <NT Account> -p <NT password>
example:
siebctl -r "/app/siebel/sia811/siebsrvr/" -S siebsrvr -i SBA_81:XXX-a -g "-g XXX:2320 -e SBA_81 -s XXXX -u SADMIN" -e XXXX
d) Restart the machine
Customer changed the sadmin's password following the Siebel Security Guide > Changing or Adding Passwords > Changing Passwords > Changing System Administrator Passwords on Microsoft Windows, but after changing the password the Siebel Server did not come up
.
In the Siebsrvr.log file it was found the following error message:
GenericLog GenericError 1 00000002499b0e08:0 2009-02-17 16:41:28 (scmnsclnt.cpp (135) err=2555922 sys=0) SBL-SCM-00018: Could not open connection to Siebel Gateway configuration store (siebel03:2320).
The following errors were just a symptom of the failure to connect to the Siebel Gateway:
GenericLog GenericError 1 00000002499b0e08:0 2009-02-17 16:41:28 (scisvc.cpp (1391) err=1311765 sys=0) SBL-SVR-01045: No components are configured.
GenericLog GenericError 1 00000002499b0e08:0 2009-02-17 16:41:28 (scfsis.cpp (274) err=1310725 sys=0) SBL-SVR-00005: Stale or invalid Task handle
ScfEventLog SubEvtFacFatal 0 00000002499b0e08:0 2009-02-17 16:41:28 scfEventFac::s_pEvtFacLock is NULL and hence SCF event facility cannot be initialised
GenericLog GenericError 1 00000002499b0e08:0 2009-02-17 16:41:28 (scfeventfac.cpp (3790) err=1319869 sys=0) SBL-SVR-09149: Could not initialize the event facility.
ScfMsgFacLog SCFMsgFacFatalError 0 00000002499b0e08:0 2009-02-17 16:41:28 SCFMessageFacility::s_pSCFMsgFacLock is null and hence the SCFMessageFacility cannot be initialized
IPCLog IPCFatal 0 00000002499b0e08:0 2009-02-17 16:41:28 ipcFacility GetInstance called before initialization - object is null
GenericLog GenericError 1 00000002499b0e08:0 2009-02-17 16:41:28 (scfsis.cpp (64) err=1310749 sys=0) SBL-SVR-00029: Internal: Shared memory has not been initialized.
Cause
The issue was due to the new security feature that was introduced on Siebel 8.1.1 to avoid access to the Gateway Server without being properly authenticated.
There are now in Siebel 8.1.1 user and password information in the Windows registry for the Siebel Server service. This can be verified by on "Path to executable:" field on General tab for the respective Siebel Server service in Administrative Tools > Services.
See the example below:
C:\sia81\siebsrvr\bin\siebsvc -s siebsrvr -i Siebel_app01 -a "-g localhost:2320 -e Siebel -s app01 -l ENU -u SADMIN -ep 9ntkUOUf" -t 120 -h C:\sia81\siebsrvr
Solution
Follow the instructions below to reflect the sadmin's password to all Siebel Serves in the Enterprise, i.e. repeat the process on all Siebel Servers in the Enterprise.
a) Delete the Siebel Server service
syntax:
siebctl -d -S siebsrvr -i "<enterprise name>_<siebel server name>"
example:
siebctl -d -S siebsrvr -i "SBA_81:XXXX"
b) Restart the machine
c) Recreate the Siebel Server service providing the new password, it will be encrypted by siebctl.
syntax:
siebctl -h %SIEBEL_ROOT% -S siebsrvr -i "<enterprise name>_<siebel server name>" -a -g "-g <gateway hostname>:<port#> -e <enterprise name -s <siebel server name> -u sadmin" -e <new password> -u <NT Account> -p <NT password>
example:
siebctl -r "/app/siebel/sia811/siebsrvr/" -S siebsrvr -i SBA_81:XXX-a -g "-g XXX:2320 -e SBA_81 -s XXXX -u SADMIN" -e XXXX
d) Restart the machine
相关文章推荐
- Siebel Server does not start after changing the SADMIN password on Siebel 8.1.1
- unable to start debugging on the web server iis does not list an application that matches the launched url
- 关于The server does not support version 3.0 of the J2EE Web module specification.问题的解决方案
- 解决 MySQL 5.7 中 Your password does not satisfy the current policy requirements. 问题
- The requested URL /phpMyAdmin was not found on this server.问题解决方法
- Changing the ovs-agent password on Oracle VM Server 3.0
- The Apache Axis2 Web service runtime in Tomcat v7.0 Server does not support the service project 问题
- unable to start debugging on the web server. The web server could not find the requested resource
- Unable to start debugging on the web server. The project is not configured to be debugged.
- eclipse 中项目->run as->run on server无法在tomcat6下运行,提示The server does not support version 3.0 of the J2E
- Could not start the iis admin service on local computer ?
- 转载 "无法启动Web服务器。Web服务器无法找到请求的资源" 或 "unable to start debugging on the web server.the web server could not find the reques"
- "无法启动Web服务器。Web服务器无法找到请求的资源" 或 "unable to start debugging on the web server.the web server could not find the request"解决方法
- BUG: The Submit button on ASP.NET pages does not work after you install the .NET Framework 1.1 Service Pack 1
- Starting the application on Mac does not work(拷贝platforms到不同的位置,才能解决问题),还可设置DYLD_PRINT_LIBRARIES=1 观察动态库
- 问题排查:The requested URL /test/index.jsp was not found on this server
- 奇葩问题:This file could not be checked in because the original version of the file on the server was moved or deleted. A new version of this file has been saved to the server, but your check-in comments were not saved
- Could not start the iis admin service on local computer ?
- run on server的时候,报出The server does not support version 3.0 of the J2EE Web module specification
- VNC Server in Virtual Mode does not start correctly on Ubuntu 12.04