on 04-04-2008 2:23 PM
NW04 SP17 Solaris 5.8 Oracle 9.2.0.6. 2sdk1.4.2_13
After stopping and restarting our portal, std_server0.out shows:
service com.sap.security.core.ume.service ================= ERROR =================
Cannot start service security; it has hard reference to service com.sap.security.core.ume.service which is not started.
Cannot start service applocking; it has hard reference to service security which is not started.
And default trc:
Service properties load error com.sap.security.core.ume.service. Detailed info is: No such algorithm: DESede#
The database is up and running, the listener is running
I can connect to the database using sqlplus sap<sid>db/<pass>@<SID>
I can not connect via the visual admin tool, I get message ID:011781: Object <security>. Ditto when using the configtool. The only tool that works is the offline config tool. In the offline configtool when I select Cluster_data -> Server -> cfg -> services -> Propertysheet com.sap.security.core.ume.service I get the same errror
"No such algorithm: DESede."
I installed this portal years ago using strong encryption. The cryto libraries are under /usr/j2sdk1.4.2_13/jre/lib/security
And browsing to http://<fqn servername>:port/index.html gives me a 503 error
The issue was fixed. I had to redeploy the SAP Java Cryptotoolkit in order for the instance to come online. I have asked SAP why the cryptography code had to be reinstalled.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Stephen,
I believe the DESede error is to do with your SSL. Can you possibly turn off encryption or check if the certificate is valid?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hai,
Check by restarting the SAP instance once and open the offlinecfgeditor.sh and check the settings for the ume.persistance.data_source_configuration in cluster_data->server->cfg->services->Propertysheet com.sap.security.core.ume.service.
And also check whether the database is open position or not.
Check the size of your file systems also.
You can access the Netweaver homepage,http://hostname:portnumber/index.html, unless the JAVA instance is started successfully.
Thanks and Regards,
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Venkaka, like a mention in the original post, when I click on com.sap.security.core.ume.service I get an error message "No such algorithm: DESede". Also as I mentioned, I cannot access the index.html page I get a 503 error "Web Container service is currently unavailable."
The file system has lots of free space.
Thanks
Hai,
Restart and open the database once again and check.If the database is opened.Also check the configtool.log in the \usr\sap\<SID>\DVEBMGS<instno>\j2ee\configtool and also check the logs in the work directory and also in the \usr\sap\<SID>\DVEBMGS<instno>\j2ee\cluster\server0\log\system.
Is the dispatcher is started?
Thanks and Regards,
Hi Venkata, the configtool.log states :
Error occurred during DB access: KeyGenerator!
Properties successfully stored for com.sap.security.core.ume.service
ChangeServicePropsTask has finished successfully. Service: com.sap.security.core.ume.service on server
Start saving properties for com.sap.security.core.ume.service
ChangeServicePropsTask has finished successfully. Service: com.sap.security.core.ume.service on server
Start saving properties for com.sap.security.core.ume.service
I have looked at the logs in the work dir, std_dispatcher is ok, std_server0 reports:
Service webservices started. (1362 ms).
Service dbpool started. (1991 ms).
service com.sap.security.core.ume.service ================= ERROR =================
Cannot start service security; it has hard reference to service com.sap.security.core.ume.service which is not started.
In the system directory, server.log states:
Service com.sap.security.core.ume.service error. Nested exception is: com.sap.engine.frame.ServiceException: <Localization failed: ResourceBundle='com.sap.engine.frame.KernelResourceBundle', ID='Error in configuration of UME Service', Arguments: []> : Can't find resource for bundle java.util.PropertyResourceBundle, key Error in configuration of UME Service
Yes, the dispatcher and bother server noeds are running as seen by the tool jcmon
-- Steve
User | Count |
---|---|
90 | |
10 | |
10 | |
10 | |
7 | |
7 | |
6 | |
5 | |
4 | |
3 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.