Webdynpro application errors with SLD,J2EE Engine - JCOs probelem

Hi,
I have developed a small webdynpro application
1. Passing 2 values to RFC
2. Getting result contents from RFC and displayed in a table.
I am getting following errors:
u2022     SLD is not accessible. Check SLD Data Supplier service settings.
u2022     Insufficient permissions for getting SLD access information. You can add permissions for your application via the SLD service in the 'Visual Administrator'.
u2022     ACCESS.ERROR: Authorization check for caller assignment to J2EE security role [SAP-J2EE-Engine : administrators].
u2022     application [webdynpro/dispatcher] Processing HTTP request to servlet [dispatcher] finished with error.
The error is: com.sap.tc.webdynpro.clientserver.session.CloseResponseException: An attempt to write after the stream had been closed.
Exception id: [0002559A6FCB0077000000A0000CF0E8000460EC9406F721]
u2022     application [webdynpro/dispatcher] Processing HTTP request to servlet [dispatcher] finished with error. The error is: com.sap.tc.webdynpro.clientserver.session.CloseResponseException: An attempt to write after the stream had been closed.
at
Please suggest me.

Hi Kiran,
You need configure SLD and JCo destinations in your j2ee engine..
Check this [article |https://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/c0c1d495-048e-2b10-babd-924a136f56b5] to create the SLD and JCo destinations.
regards,
Siva

Similar Messages

  • Issue in Communication of SAP R/3 6.4C with SAP J2EE Engine 6.40.

    Hello,
    We have an application deployed in SAP J2EE engine 6.20. From SAP R3 (SAP R/3 version is 6.4C), We are communicating to the application deployed in SAP J2EE Engine 6.20 using RFC protocol. EJB module (Deployed in SAP J2EE Engine 6.20) which is being invoked from a Function Module using RFC protocol has the same name as the Function Module name. We were able to communicate to SAP J2EE Engine 6.20 this way.
    Currently, I have deployed the same application in SAP J2EE Engine 6.40. I have followed the same procedure which i have used while depolying and working with SAP J2EE Engine 6.20. But, it is not working, and i was not able to communicate to SAP J2EE 6.40, the same way i did in SAP J2EE Engine 6.20.
    Please let me know whether the procedure for communicating to SAP J2EE Engine 6.40 has changed in comparison with SAP J2EE Engine 6.20.
    Also,Any pointers regarding RFC and JCO implementation in SAP J2EE Engine 6.40 willl be helpful.
    Thank you.
    Regards,
    -Shabir Rahim.

    Hi,
    compare to 4.7
    1.New ABAP editor added like if u write code  in abap editor ,using if coditions and select statments it automatically shows the link endif,  like if .. endif,select ...endselect.
    2.New abap debugger compare to the classic debugger.
    3.DBACOCKPIT
       Missing indexes of various database tablesu2019 and the transaction to reactivate all the missing indexes  is u2018DBACOCKPITu2019. Below is the screenshot of the transaction DBACOCKPIT.
    Regards,
    Madhu

  • Deployment Error on sap-j2ee engine

    Hi
    I build an EJB project,Web project and added these to EAR project and built an '.ear' file. When i tried to deploy on sapj2ee engine. I got the following deployment error.
    My j2ee engine is up and running. What went wrong?
    Help me,
    Thanks
    ==========
    May 24, 2006 5:39:51 PM /userOut/deploy (com.sap.ide.eclipse.sdm.threading.DeployThreadManager) [Thread[Deploy Thread,5,main]] ERROR:
    [003]Deployment aborted
    Settings
    SDM host : sapep
    SDM port : 50018
    URL to deploy : file:/C:/DOCUME1/ADMINI1/LOCALS~1/Temp/temp22811JCP_EAR.ear
    Result
    => deployment aborted : file:/C:/DOCUME1/ADMINI1/LOCALS~1/Temp/temp22811JCP_EAR.ear
    Aborted: development component 'JCP_EAR'/'sap.com'/'localhost'/'2006.05.24.15.58.19':
    Caught exception during access of archive "D:\usr\sap\QN7\DVEBMGS00\SDM\root\origin\sap.com\JCP_EAR\localhost\2006.05.24.15.58.19\temp22811JCP_EAR.ear":
    java.lang.RuntimeException: ERROR: Cannot initialize EARReader: com.sap.engine.services.deploy.exceptions.BaseIOException: Cannot convert EAR D:\usr\sap\QN7\DVEBMGS00\SDM\root\origin\sap.com\JCP_EAR\localhost\2006.05.24.15.58.19\temp22811JCP_EAR.ear to J2EE 1.3.Exception is: com.sap.engine.services.deploy.exceptions.BaseIOException: Cannot convert EAR D:\usr\sap\QN7\DVEBMGS00\SDM\root\origin\sap.com\JCP_EAR\localhost\2006.05.24.15.58.19\temp22811JCP_EAR.ear to J2EE 1.3.
         at com.sap.engine.services.deploy.converter.EARConverter.convert(EARConverter.java:185)
         at com.sap.engine.deploy.manager.DeployManagerImpl.setEar(DeployManagerImpl.java:444)
         at com.sap.sdm.serverext.servertype.inqmy.extern.EngineApplOnlineDeployerImpl.initDeployManager(EngineApplOnlineDeployerImpl.java:300)
         at com.sap.sdm.serverext.servertype.inqmy.extern.EngineApplOnlineDeployerImpl.performDeployment(EngineApplOnlineDeployerImpl.java:134)
         at com.sap.sdm.serverext.servertype.inqmy.extern.EngineDeployerImpl.deploy(EngineDeployerImpl.java:96)
         at com.sap.sdm.serverext.servertype.inqmy.EngineProcessor.executeAction(EngineProcessor.java:224)
         at com.sap.sdm.app.proc.deployment.impl.PhysicalDeploymentActionExecutor.execute(PhysicalDeploymentActionExecutor.java:60)
         at com.sap.sdm.app.proc.deployment.impl.DeploymentActionImpl.execute(DeploymentActionImpl.java:186)
         at com.sap.sdm.app.proc.deployment.controllers.internal.impl.DeploymentExecutorImpl.execute(DeploymentExecutorImpl.java:46)
         at com.sap.sdm.app.proc.deployment.states.eventhandler.ExecuteDeploymentHandler.executeAction(ExecuteDeploymentHandler.java:83)
         at com.sap.sdm.app.proc.deployment.states.eventhandler.ExecuteDeploymentHandler.handleEvent(ExecuteDeploymentHandler.java:60)
         at com.sap.sdm.app.proc.deployment.states.StateBeforeNextDeployment.processEvent(StateBeforeNextDeployment.java:127)
         at com.sap.sdm.app.proc.deployment.states.InstContext.processEventServerSide(InstContext.java:73)
         at com.sap.sdm.app.proc.deployment.states.InstContext.processEvent(InstContext.java:59)
         at com.sap.sdm.app.sequential.deployment.impl.DeployerImpl.doPhysicalDeployment(DeployerImpl.java:119)
         at com.sap.sdm.app.sequential.deployment.impl.DeployerImpl.deploy(DeployerImpl.java:88)
         at com.sap.sdm.apiimpl.local.DeployProcessorImpl.deploy(DeployProcessorImpl.java:74)
         at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
         at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
         at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
         at java.lang.reflect.Method.invoke(Method.java:324)
         at com.sap.sdm.is.cs.remoteproxy.server.impl.RemoteProxyServerImpl.requestRemoteCall(RemoteProxyServerImpl.java:127)
         at com.sap.sdm.is.cs.remoteproxy.server.impl.RemoteProxyServerImpl.process(RemoteProxyServerImpl.java:38)
         at com.sap.sdm.apiimpl.remote.server.ApiClientRoleCmdProcessor.process(ApiClientRoleCmdProcessor.java:84)
         at com.sap.sdm.is.cs.session.server.SessionCmdProcessor.process(SessionCmdProcessor.java:67)
         at com.sap.sdm.is.cs.cmd.server.CmdServer.execCommand(CmdServer.java:76)
         at com.sap.sdm.client_server.launch.ServerLauncher$ConnectionHandlerImpl.handle(ServerLauncher.java:286)
         at com.sap.sdm.is.cs.ncserver.NetCommServer.serve(NetCommServer.java:43)
         at com.sap.sdm.is.cs.ncwrapper.impl.ServiceWrapper.serve(ServiceWrapper.java:39)
         at com.sap.bc.cts.tp.net.Worker.run(Worker.java:50)
         at java.lang.Thread.run(Thread.java:534)
    Caused by: java.io.IOException: The following archives that aredescribed in the ear descriptor are not found in the ear:      JCP_EJB.jar,Please check the ear content.
         at com.sap.engine.services.deploy.extended.ear.ExtendedEARReader.checkDescriptor(ExtendedEARReader.java:805)
         at com.sap.engine.services.deploy.extended.ear.ExtendedEARReader.getDescriptor(ExtendedEARReader.java:324)
         at com.sap.engine.services.deploy.extended.ear.ExtendedEARReader.<init>(ExtendedEARReader.java:87)
         at com.sap.engine.services.deploy.converter.EARConverter.convert(EARConverter.java:85)
         ... 30 more
    (message ID: com.sap.sdm.serverext.servertype.inqmy.extern.EngineApplOnlineDeployerImpl.performAction(DeploymentActionTypes).null)
    Deployment exception : The deployment of at least one item aborted

    Hi Amol!
    The password is admin for SDM, i redployed by building '.ear' file again.
    You suggested to deploy the ear file on SDM remote gui, how to do that?
    help me
    Thanks
    ==========
    I got the error as:
    May 25, 2006 11:22:11 AM /userOut/deploy (com.sap.ide.eclipse.sdm.threading.DeployThreadManager) [Thread[Deploy Thread,5,main]] ERROR:
    [001]Deployment aborted
    Settings
    SDM host : sapep
    SDM port : 50018
    URL to deploy : file:/C:/DOCUME1/ADMINI1/LOCALS~1/Temp/temp11022JCP_EAR.ear
    Result
    => deployment aborted : file:/C:/DOCUME1/ADMINI1/LOCALS~1/Temp/temp11022JCP_EAR.ear
    Aborted: development component 'JCP_EAR'/'sap.com'/'localhost'/'2006.05.25.11.17.51':
    Caught exception during access of archive "D:\usr\sap\QN7\DVEBMGS00\SDM\root\origin\sap.com\JCP_EAR\localhost\2006.05.25.11.17.51\temp11022JCP_EAR.ear":
    java.lang.RuntimeException: ERROR: Cannot initialize EARReader: com.sap.engine.services.deploy.exceptions.BaseIOException: Cannot convert EAR D:\usr\sap\QN7\DVEBMGS00\SDM\root\origin\sap.com\JCP_EAR\localhost\2006.05.25.11.17.51\temp11022JCP_EAR.ear to J2EE 1.3.Exception is: com.sap.engine.services.deploy.exceptions.BaseIOException: Cannot convert EAR D:\usr\sap\QN7\DVEBMGS00\SDM\root\origin\sap.com\JCP_EAR\localhost\2006.05.25.11.17.51\temp11022JCP_EAR.ear to J2EE 1.3.
         at com.sap.engine.services.deploy.converter.EARConverter.convert(EARConverter.java:185)
         at com.sap.engine.deploy.manager.DeployManagerImpl.setEar(DeployManagerImpl.java:444)
         at com.sap.sdm.serverext.servertype.inqmy.extern.EngineApplOnlineDeployerImpl.initDeployManager(EngineApplOnlineDeployerImpl.java:300)
         at com.sap.sdm.serverext.servertype.inqmy.extern.EngineApplOnlineDeployerImpl.performDeployment(EngineApplOnlineDeployerImpl.java:134)
         at com.sap.sdm.serverext.servertype.inqmy.extern.EngineDeployerImpl.deploy(EngineDeployerImpl.java:96)
         at com.sap.sdm.serverext.servertype.inqmy.EngineProcessor.executeAction(EngineProcessor.java:224)
         at com.sap.sdm.app.proc.deployment.impl.PhysicalDeploymentActionExecutor.execute(PhysicalDeploymentActionExecutor.java:60)
         at com.sap.sdm.app.proc.deployment.impl.DeploymentActionImpl.execute(DeploymentActionImpl.java:186)
         at com.sap.sdm.app.proc.deployment.controllers.internal.impl.DeploymentExecutorImpl.execute(DeploymentExecutorImpl.java:46)
         at com.sap.sdm.app.proc.deployment.states.eventhandler.ExecuteDeploymentHandler.executeAction(ExecuteDeploymentHandler.java:83)
         at com.sap.sdm.app.proc.deployment.states.eventhandler.ExecuteDeploymentHandler.handleEvent(ExecuteDeploymentHandler.java:60)
         at com.sap.sdm.app.proc.deployment.states.StateBeforeNextDeployment.processEvent(StateBeforeNextDeployment.java:127)
         at com.sap.sdm.app.proc.deployment.states.InstContext.processEventServerSide(InstContext.java:73)
         at com.sap.sdm.app.proc.deployment.states.InstContext.processEvent(InstContext.java:59)
         at com.sap.sdm.app.sequential.deployment.impl.DeployerImpl.doPhysicalDeployment(DeployerImpl.java:119)
         at com.sap.sdm.app.sequential.deployment.impl.DeployerImpl.deploy(DeployerImpl.java:88)
         at com.sap.sdm.apiimpl.local.DeployProcessorImpl.deploy(DeployProcessorImpl.java:74)
         at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
         at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
         at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
         at java.lang.reflect.Method.invoke(Method.java:324)
         at com.sap.sdm.is.cs.remoteproxy.server.impl.RemoteProxyServerImpl.requestRemoteCall(RemoteProxyServerImpl.java:127)
         at com.sap.sdm.is.cs.remoteproxy.server.impl.RemoteProxyServerImpl.process(RemoteProxyServerImpl.java:38)
         at com.sap.sdm.apiimpl.remote.server.ApiClientRoleCmdProcessor.process(ApiClientRoleCmdProcessor.java:84)
         at com.sap.sdm.is.cs.session.server.SessionCmdProcessor.process(SessionCmdProcessor.java:67)
         at com.sap.sdm.is.cs.cmd.server.CmdServer.execCommand(CmdServer.java:76)
         at com.sap.sdm.client_server.launch.ServerLauncher$ConnectionHandlerImpl.handle(ServerLauncher.java:286)
         at com.sap.sdm.is.cs.ncserver.NetCommServer.serve(NetCommServer.java:43)
         at com.sap.sdm.is.cs.ncwrapper.impl.ServiceWrapper.serve(ServiceWrapper.java:39)
         at com.sap.bc.cts.tp.net.Worker.run(Worker.java:50)
         at java.lang.Thread.run(Thread.java:534)
    Caused by: java.io.IOException: The following archives that aredescribed in the ear descriptor are not found in the ear:      JCP_EJB.jar,Please check the ear content.
         at com.sap.engine.services.deploy.extended.ear.ExtendedEARReader.checkDescriptor(ExtendedEARReader.java:805)
         at com.sap.engine.services.deploy.extended.ear.ExtendedEARReader.getDescriptor(ExtendedEARReader.java:324)
         at com.sap.engine.services.deploy.extended.ear.ExtendedEARReader.<init>(ExtendedEARReader.java:87)
         at com.sap.engine.services.deploy.converter.EARConverter.convert(EARConverter.java:85)
         ... 30 more
    (message ID: com.sap.sdm.serverext.servertype.inqmy.extern.EngineApplOnlineDeployerImpl.performAction(DeploymentActionTypes).null)
    Deployment exception : The deployment of at least one item aborted

  • Problem while Deploying WebDynpro application-error:java.rmi.RemoteExceptio

    Hi All,
       i installed WAS 6.40 sp 16 on my system its working fine. I can able to log in to the  SDM as remoteGUI.bat using my sdm password.But while deploying the webdynpro appliation i am getting error like "java.rmi.RemoteException: Only Administrators have the right to perform this operation".
    Using my administrator PWD i can log in to all the systems like Useradmin, SDM, J2E engine.
    can any one help me....thanks in advance

    hi all
    i also had the same problem, i am able to log into SDM GUI through Remotegui.bat
    but even though i had changed the password i am not able to deploy the applicaton to j2ee sever, through the NWDS. I tried deploying the applicaton in the
    GUI of SDM there also it is giving like "Only Administrators have the right to perform this operation".
    How to go to User Administration and where?is it in OS level or in Web AS Admin console?
    Adding user admin (default password is also admin) to the Administrators group,
    Go to: User Administration --> Groups and search for Administrators.
    Then add user with ID admin in this group

  • Webdynpro application automatic start after j2ee startup

    Hi ,
    Is there a way to automatically start any specific webdynpro applications after j2ee startup
    Oren

    I guess you can write batch file for that.
    Example
    suppose you have a bat file which starts J2EE engine, startJ2EE.
    You can write a new bat file with following commands.
    startJ2EE.bat
    explorer http://<server>:<port>/webdynpro/<URL as application>
    Let me know if you need more help
    Ashutosh

  • Installation error u2013 SAP J2EE Engine, error at step importJavaDump

    Dear All,
    I have installed NetWeaver Developer Studio but getting problem for SAP J2EE Engine installation
    I have given following parameter at the time of installation.'
               RDBMS MaxDB
               'package location' - C:\Program Files\NetWeaverDeveloperStudio\NW_JAVA_700SP14_SR3 \MAXDB76_NW07
               'Copy package To' - c:\sapdb
               UC Kernel nw 7.0 R3
               'package location' - C:\Program Files\NetWeaverDeveloperStudio\NW_JAVA_700SP14_SR3\NW05SR3_KRNL3
              'Copy package To' - Left empty
               Chose option - No SLD destination
    My operating system is Window Vista Home Basic. Is vista support SAP J2EE engine?
    MaxDB has been installed but how it can be checked whether it has been installed properly?
    sapinst.log u2013 Error description
    ERROR 2008-06-24 15:57:07.104
    CJS-30049  <html> <head> </head> <body> Execution of <font face="Monospaced">JLoad</font> tool 'C:\Program Files\Java\j2sdk1.4.2_09\bin\java.exe -classpath "C:\Program Files\sapinst_instdir\NW04S\SYSTEM\DEVWP\MAXDB\install\sharedlib\launcher.jar" -showversion -Xmx512m com.sap.engine.offline.OfflineToolStart com.sap.inst.jload.Jload "C:/Program Files/sapinst_instdir/NW04S/SYSTEM/DEVWP/MAXDB/install/lib/iaik_jce.jar;C:/Program Files/sapinst_instdir/NW04S/SYSTEM/DEVWP/MAXDB/install/sharedlib/jload.jar;C:/Program Files/sapinst_instdir/NW04S/SYSTEM/DEVWP/MAXDB/install/sharedlib/antlr.jar;C:/Program Files/sapinst_instdir/NW04S/SYSTEM/DEVWP/MAXDB/install/sharedlib/exception.jar;C:/Program Files/sapinst_instdir/NW04S/SYSTEM/DEVWP/MAXDB/install/sharedlib/jddi.jar;C:/Program Files/sapinst_instdir/NW04S/SYSTEM/DEVWP/MAXDB/install/sharedlib/logging.jar;C:/Program Files/sapinst_instdir/NW04S/SYSTEM/DEVWP/MAXDB/install/sharedlib/offlineconfiguration.jar;C:/Program Files/sapinst_instdir/NW04S/SYSTEM/DEVWP/MAXDB/install/sharedlib/opensqlsta.jar;C:/Program Files/sapinst_instdir/NW04S/SYSTEM/DEVWP/MAXDB/install/sharedlib/tc_sec_secstorefs.jar;C:\sapdb\programs\runtime\jar\sapdbc.jar" -sec AN2,jdbc/pool/AN2,
    AnupGarg-PC/sapmnt/AN2/SYS/global/security/data/SecStore.properties,
    AnupGarg-PC/sapmnt/AN2/SYS/global/security/data/SecStore.key -dataDir "C:/Program Files/NetWeaverDeveloperStudio/NW_JAVA_700SP14_SR3/NW05SR3_DEV_WP_1\JAVA_EXPORT\JDMP" -job "C:\Program Files\sapinst_instdir\NW04S\SYSTEM\DEVWP\MAXDB\IMPORT.XML" -log jload.log' aborts with return code 1.<br>SOLUTION: Check 'jload.log' and 'C:/Program Files/sapinst_instdir/NW04S/SYSTEM/DEVWP/MAXDB/jload.java.log' for more information. </body></html>
    ERROR 2008-06-24 15:57:07.104
    FCO-00011  The step importJavaDump with step key |NW_Workplace|ind|ind|ind|ind|0|0|NW_Onehost|ind|ind|ind|ind|0|0|NW_Onehost_System|ind|ind|ind|ind|2|0|NW_CreateDBandLoad|ind|ind|ind|ind|10|0|NW_Jload|ind|ind|ind|ind|9|0|importJavaDump was executed with status ERROR .
    jload.java.log u2013 Error description
    java version "1.4.2_09"
    Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.2_09-b05)
    Java HotSpot(TM) Client VM (build 1.4.2_09-b05, mixed mode)
    Jun 24, 2008 10:27:05 AM com.sap.inst.jload.Jload main
    INFO: Jload -sec AN2,jdbc/pool/AN2,
    AnupGarg-PC/sapmnt/AN2/SYS/global/security/data/SecStore.properties,
    AnupGarg-PC/sapmnt/AN2/SYS/global/security/data/SecStore.key -dataDir C:/Program Files/NetWeaverDeveloperStudio/NW_JAVA_700SP14_SR3/NW05SR3_DEV_WP_1\JAVA_EXPORT\JDMP -job C:\Program Files\sapinst_instdir\NW04S\SYSTEM\DEVWP\MAXDB\IMPORT.XML -log jload.log
    Jun 24, 2008 10:27:07 AM com.sap.inst.jload.Jload main
    SEVERE: couldn't connect to DB
    It would be great help if I can get any clue to solve this?
    Thanks & Regards,
    Anup Garg

    Hi Anup,
    If you  want to install developer studio then you need not to install J2ee engine for this.
    Actaully there are 2 products :
    1. Developer studio
    2. Developer workplace.
    In fact these are not 2 products but if you want to install developer studio with local runtime environment then you need to install developer workplace.
    So (J2EE engine + Developer studio)= developer workspace
    you can install developer studio on XP, windows 2003 server and NT platform but not sure for VISTA. But it should work on vista with no problem.
    but you can install developer workspace only on server platforms because it needs J2EE engine to be installed as a prerequisite.
    in your case , you need windows 2003 server instead of vista if you want j2ee engine and  developer studio both.
    In case you only want to install developer studio, you can install it from developer workplace DVD .
    browse to Dev workplace DVD( Example path for version 7.0)
    DVD>IDE>IDE70setup
    execute this setup. it will only installdeveloper studio.
    please award points if above info is helpful.
    regards
    Saurabh

  • Running ssl client from multiple applications fails in Sap j2ee engine

    There are two applications making ssl connections to third party.
    At a time only one application is able to make connection while other
    throws error message <b>"No trusted certificate found".</b>
    Currently we have  two j2ee applications running in SAP j2ee server. Both applications makes ssl connection to third party servers. Lets call first application as A1 and second application as A2.
    A1 is an internet shopping application . It makes ssl connection to third party services at two places . One is while fetching the shipping charges from UPS site.
    Code Snippet:
    java.security.Security.addProvider(new com.sun.net.ssl.internal.ssl.Provider());
    System.getProperties().put("java.protocol.handler.pkgs", "com.sun.net.ssl.internal.www.protocol");
    String lo_url = new URL("https://wwwcie.ups.com/ups.app/xml/Rate");
    lo_connection = (URLConnection) lo_url.openConnection();
    At other place A1 connects to cybersource service using webservice +ssl  for credit card authentication using cybersource API. It uses certificate in p12 format.
    Code Snippet:
    com.cybersource.ws.client.axis.soap.RequestMessage lo_requestMessage = new  com.cybersource.ws.client.axis.soap.RequestMessage();
    Properties lo_cybsProperties = new Properties();
    lo_cybsProperties.setProperty("merchantId","arvato");
    lo_cybsProperties.setProperty("merchantRefCode","1234")
    lo_requestMessage.setMerchantID( "arvato");
    lo_requestMessage.setMerchantReferenceCode( "1234" );
    lo_cybsProperties.setProperty("cybersourceURL","https://ics2wstest.ic3.com/commerce/1.x/transactionProcessor");
    lo_cybsProperties.setProperty("keysDir", "./WEB-INF/config");     
    lo_requestMessage.setBillTo(setBillToAddress(po_mdsBillingAddress) );
    // add ship to address
    lo_requestMessage.setShipTo(setShipToAddress(po_mdsShiToAddress));
    lo_requestMessage.setPurchaseTotals( setPurchaseTotal() );
    //set cc details
    lo_requestMessage.setCard( setCardDetails(po_mdsCreditCard) );
    Set Items and total tax calculation
    lo_replyMessage = com.cybersource.ws.client.axis.soap.Client.runTransaction( lo_requestMessage, lo_cybsProperties );
    A2 Application
    This application connects to Motorola secured web service to fetch details of mobile hand set. It uses keystore to create ssl connection with Motorola webservice.
    Code Snippet
    try {
    TrustManager[] trustAllCerts = new TrustManager[]{
    new X509TrustManager() {
    public java.security.cert.X509Certificate[] getAcceptedIssuers() {
              return new java.security.cert.X509Certificate[0];
         public void checkClientTrusted(java.security.cert.X509Certificate[] certs, String authType) {}
    public void checkServerTrusted(
    java.security.cert.X509Certificate[] certs, String authType) {
    SSLContext sc = SSLContext.getInstance("SSL");
    sc.init(null, trustAllCerts, new java.security.SecureRandom());
    } catch (Exception e) {
    e.printStackTrace();
    System.setProperty("javax.net.ssl.trustStore","SapWSM.keystore");
    System.setProperty("javax.net.ssl.trustStorePassword","xxxx");
    System.setProperty("javax.net.ssl.keyStore","SapWSM.keystore");
    System.setProperty("javax.net.ssl.keyStorePassword","xxxx");
    Problem Cases :
    Case 1
    Step 1 : Server starts
    Step 2 : User access A1 first
    Step3: A1 Connects to UPS using https (It is able to connect)
    Step4: A1 connects to cybersource using webservice+ssl  (It is able to connect)
    Step 5: Another user access A2
    Step6: A2 tries connection to Motorola webservice over ssl
    Result connectivity fails with description "No trusted certificate found".
    Case2
    Step 1 : Server starts
    Step 2 : User access A2 first
    Step3:  A2 tries connection to Motorola webservice over ssl (It is able to connect)
    Step 5: Another user access A1
    Step6: A1 connects to cybersource using webservice+ssl 
    Result connectivity fails with description "No trusted certificate found".
    Case3
    Step 1 : Server starts
    Step 2 : User access A2 first
    Step3:  A2 tries connection to Motorola webservice over ssl (It is able to connect)
    Step 5: Another user access A1
    Step6: A1 connects to  UPS using ssl
    Result connectivity fails with description "No trusted certificate found".

    Hi Please answer my query it is really <b>
    urgen
    t</b> and we are not able to run both the applications in same server

  • Error with SLD

    Dear Experts,
    when I am calling ctc installer (template installer) with /nwa , i become the following error message and the install dont start.
    "Validation Error: Test SLD connection:It was not possible to test the
    SLD system (SLD_HOST) with the user (SLD_ADMIN) and its password given
    in the property sheet. Please verify and retype the values in the
    corresponding fields. You can also go to visual administrator -> "SID" -> Server xx -> Services -> Configuration adaptor -> CTC ->
    Propertysheet SystemProperties, make sure that the parameters related
    to SLD are correctly typed and rerun the template."
    but in the visual administrator the parameters are correct.
    what can be the reason herefore? maybe the password for this slddsuser??
    Regards
    Engin Imal

    Hello Engin,
    Check if Note 923359
    and following link are useful :
    http://help.sap.com/saphelp_nw70/helpdata/en/25/5AEE4242217076E10000000A1550B0/frameset.htm     
    Regards,
    Snehal

  • Error while starting J2EE engine.

    Dear Friends,
    We are facing problem while starting of J2EE engine due to which we are unable to login in to EP.We have installed  ECC6.0 + Usage types EP and PI on the same box.We are getting VM related error and we have refered SAP note:723909
    Please find below the error messages in developer trace file of J2EE.
    trc file: "D:\usr\sap\DN1\DVEBMGS01\work\dev_dispatcher", trc level: 1, release: "700"
    node name   : ID11240300
    pid         : 5300
    system name : DN1
    system nr.  : 01
    started at  : Thu Sep 07 17:06:47 2006
    arguments       :
           arg[00] : D:\usr\sap\DN1\DVEBMGS01\exe\jlaunch.exe
           arg[01] : pf=D:\usr\sap\DN1\SYS\profile\DN1_DVEBMGS01_rbgtsa26
           arg[02] : -DSAPINFO=DN1_01_dispatcher
           arg[03] : pf=D:\usr\sap\DN1\SYS\profile\DN1_DVEBMGS01_rbgtsa26
           arg[04] : -DSAPSTART=1
           arg[05] : -DCONNECT_PORT=2483
           arg[06] : -DSAPSYSTEM=01
           arg[07] : -DSAPSYSTEMNAME=DN1
           arg[08] : -DSAPMYNAME=rbgtsa26_DN1_01
           arg[09] : -DSAPPROFILE=D:\usr\sap\DN1\SYS\profile\DN1_DVEBMGS01_rbgtsa26
           arg[10] : -DFRFC_FALLBACK=ON
           arg[11] : -DFRFC_FALLBACK_HOST=localhost
    [Thr 5304] Thu Sep 07 17:06:47 2006
    [Thr 5304] *** WARNING => INFO: Unknown property [instance.box.number=DN1DVEBMGS01rbgtsa26] [jstartxx.c   841]
    [Thr 5304] *** WARNING => INFO: Unknown property [instance.en.host=rbgtsa26] [jstartxx.c   841]
    [Thr 5304] *** WARNING => INFO: Unknown property [instance.en.port=3200] [jstartxx.c   841]
    [Thr 5304] *** WARNING => INFO: Unknown property [instance.system.id=1] [jstartxx.c   841]
    JStartupReadInstanceProperties: read instance properties [D:\usr\sap\DN1\DVEBMGS01\j2ee\cluster\instance.properties]
    -> ms host    : rbgtsa26
    -> ms port    : 3900
    -> OS libs    : D:\usr\sap\DN1\DVEBMGS01\j2ee\os_libs
    -> Admin URL  :
    -> run mode   : NORMAL
    -> run action : NONE
    -> enabled    : yes
    Used property files
    -> files [00] : D:\usr\sap\DN1\DVEBMGS01\j2ee\cluster\instance.properties
    Instance properties
    -> ms host    : rbgtsa26
    -> ms port    : 3900
    -> os libs    : D:\usr\sap\DN1\DVEBMGS01\j2ee\os_libs
    -> admin URL  :
    -> run mode   : NORMAL
    -> run action : NONE
    -> enabled    : yes
    Bootstrap nodes
    -> [00] bootstrap            : D:\usr\sap\DN1\DVEBMGS01\j2ee\cluster\instance.properties
    -> [01] bootstrap_ID11240300 : D:\usr\sap\DN1\DVEBMGS01\j2ee\cluster\instance.properties
    -> [02] bootstrap_ID11240350 : D:\usr\sap\DN1\DVEBMGS01\j2ee\cluster\instance.properties
    Worker nodes
    -> [00] ID11240300           : D:\usr\sap\DN1\DVEBMGS01\j2ee\cluster\instance.properties
    -> [01] ID11240350           : D:\usr\sap\DN1\DVEBMGS01\j2ee\cluster\instance.properties
    [Thr 5304] JLaunchRequestQueueInit: create named pipe for ipc
    [Thr 5304] JLaunchRequestQueueInit: create pipe listener thread
    [Thr 5312] WaitSyncSemThread: Thread 5312 started as semaphore monitor thread.
    [Thr 5308] JLaunchRequestFunc: Thread 5308 started as listener thread for np messages.
    [Thr 5304] NiInit3: NI already initialized; param 'maxHandles' ignored (1;202)
    [Thr 5304] CPIC (version=700.2005.12.02)
    [Thr 5304] [Node: dispatcher] java home is set by profile parameter
         Java Home: C:\j2sdk1.4.2_12
    [Thr 5304] JStartupICheckFrameworkPackage: can't find framework package D:\usr\sap\DN1\DVEBMGS01\exe\jvmx.jar
    JStartupIReadSection: read node properties [ID11240300]
    -> node name          : dispatcher
    -> node type          : dispatcher
    -> node execute       : yes
    -> jlaunch parameters :
    -> java path          : C:\j2sdk1.4.2_12
    -> java parameters    : -Djava.security.policy=./java.policy -Djava.security.egd=file:/dev/urandom -Dorg.omg.CORBA.ORBClass=com.sap.engine.system.ORBProxy -Dorg.omg.CORBA.ORBSingletonClass=com.sap.engine.system.ORBSingletonProxy -Djavax.rmi.CORBA.PortableRemoteObjectClass=com.sap.engine.system.PortableRemoteObjectProxy -XX:NewSize=182m -XX:MaxNewSize=182m -XX:NewRatio=3 -XX:DisableExplicitGC -verbose:gc -XX:UseConcMarkSweepGC
    -> java vm version    : 1.4.2_12-b03
    -> java vm vendor     : Java HotSpot(TM) Server VM (Sun Microsystems Inc.)
    -> java vm type       : server
    -> java vm cpu        : x86
    -> heap size          : 256M
    -> init heap size     : 545M
    -> root path          : D:\usr\sap\DN1\DVEBMGS01\j2ee\cluster\dispatcher
    -> class path         : .\bin\boot\boot.jar;.\bin\system\bytecode.jar;.
    -> OS libs path       : D:\usr\sap\DN1\DVEBMGS01\j2ee\os_libs
    -> main class         : com.sap.engine.boot.Start
    -> framework class    : com.sap.bc.proj.jstartup.JStartupFramework
    -> registr. class     : com.sap.bc.proj.jstartup.JStartupNatives
    -> framework path     : D:\usr\sap\DN1\DVEBMGS01\exe\jstartup.jar;D:\usr\sap\DN1\DVEBMGS01\exe\jvmx.jar
    -> shutdown class     : com.sap.engine.boot.Start
    -> parameters         :
    -> debuggable         : no
    -> debug mode         : no
    -> debug port         : 50000
    -> shutdown timeout   : 120000
    [Thr 5304] JLaunchISetDebugMode: set debug mode [no]
    [Thr 5324] JLaunchIStartFunc: Thread 5324 started as Java VM thread.
    JHVM_LoadJavaVM: VM Arguments of node [dispatcher]
    -> stack   : 262144 Bytes
    -> arg[  0]: exit
    -> arg[  1]: abort
    -> arg[  2]: vfprintf
    -> arg[  3]: -Djava.security.policy=./java.policy
    -> arg[  4]: -Djava.security.egd=file:/dev/urandom
    -> arg[  5]: -Dorg.omg.CORBA.ORBClass=com.sap.engine.system.ORBProxy
    -> arg[  6]: -Dorg.omg.CORBA.ORBSingletonClass=com.sap.engine.system.ORBSingletonProxy
    -> arg[  7]: -Djavax.rmi.CORBA.PortableRemoteObjectClass=com.sap.engine.system.PortableRemoteObjectProxy
    -> arg[  8]: -XX:NewSize=182m
    -> arg[  9]: -XX:MaxNewSize=182m
    -> arg[ 10]: -XX:NewRatio=3
    -> arg[ 11]: -XX:+DisableExplicitGC
    -> arg[ 12]: -verbose:gc
    -> arg[ 13]: -XX:+UseConcMarkSweepGC
    -> arg[ 14]: -Dsys.global.dir=D:\usr\sap\DN1\SYS\global
    -> arg[ 15]: -Dapplication.home=D:\usr\sap\DN1\DVEBMGS01\exe
    -> arg[ 16]: -Djava.class.path=D:\usr\sap\DN1\DVEBMGS01\exe\jstartup.jar;D:\usr\sap\DN1\DVEBMGS01\exe\jvmx.jar;.\bin\boot\boot.jar;.\bin\system\bytecode.jar;.
    -> arg[ 17]: -Djava.library.path=C:\j2sdk1.4.2_12\jre\bin\server;C:\j2sdk1.4.2_12\jre\bin;C:\j2sdk1.4.2_12\bin;D:\usr\sap\DN1\DVEBMGS01\j2ee\os_libs;D:\oracle\DN1\102\bin;C:\Program Files\Support Tools\;C:\Program Files\Windows Resource Kits\Tools\;C:\WINNT\system32;C:\WINNT;C:\WINNT\System32\Wbem;D:\usr\sap\DN1\SYS\exe\uc\NTI386
    -> arg[ 18]: -Dmemory.manager=256M
    -> arg[ 19]: -Xmx256M
    -> arg[ 20]: -Xms545M
    -> arg[ 21]: -DLoadBalanceRestricted=no
    -> arg[ 22]: -Djstartup.mode=JCONTROL
    -> arg[ 23]: -Djstartup.ownProcessId=5300
    -> arg[ 24]: -Djstartup.ownHardwareId=S1962625527
    -> arg[ 25]: -Djstartup.whoami=dispatcher
    -> arg[ 26]: -Djstartup.debuggable=no
    -> arg[ 27]: -DSAPINFO=DN1_01_dispatcher
    -> arg[ 28]: -DSAPSTART=1
    -> arg[ 29]: -DCONNECT_PORT=2483
    -> arg[ 30]: -DSAPSYSTEM=01
    -> arg[ 31]: -DSAPSYSTEMNAME=DN1
    -> arg[ 32]: -DSAPMYNAME=rbgtsa26_DN1_01
    -> arg[ 33]: -DSAPPROFILE=D:\usr\sap\DN1\SYS\profile\DN1_DVEBMGS01_rbgtsa26
    -> arg[ 34]: -DFRFC_FALLBACK=ON
    -> arg[ 35]: -DFRFC_FALLBACK_HOST=localhost
    -> arg[ 36]: -DSAPSTARTUP=1
    -> arg[ 37]: -DSAPSYSTEM=01
    -> arg[ 38]: -DSAPSYSTEMNAME=DN1
    -> arg[ 39]: -DSAPMYNAME=rbgtsa26_DN1_01
    -> arg[ 40]: -DSAPDBHOST=rbgtsa26
    -> arg[ 41]: -Dj2ee.dbhost=rbgtsa26
    Error occurred during initialization of VM
    Incompatible initial and maximum heap sizes specified
    [Thr 5324] JLaunchIAbortJava: abort hook is called
    [Thr 5324] JLaunchCloseProgram: good bye (exitcode = -2)
    Our configuration is as follows:
    1> Windows 2003 server with dual processor
    2> 3.7GB RAM
    3> VM around 12GB.
    Please suggest
    Kind Regards
    Neenad Kivalkar

    Hello all,
    Now the JAVA engine is started and we can see ( we changed the New size and Max heap size parameters)
    1> SDM
    2> dispatcher node
    3> server 0 node
    in green and status as running.
    But when we login using http://<FQDN HOST NAME>:<port>/irj/portal
    We can see only Welcome screen but nothing really is displayed. The links like search, Advanced search and personalize, logoff are not working.
    Kind Regards
    Neenad

  • UME error - cannot start j2ee engine

    I have configured UME to work with Active Directory and it works fine. I have changed the Active Directory service user password, now the j2ee engine is not starting anymore. I cannot revert back to the default UME repository ( I am stuck with AD not working)
    how can I resolve this?
    Tiberiu
    this is the error I get:
    Caused by: com.sap.security.core.persistence.datasource.PersistenceException: Initialisation of connection pool failed for UACC
         poolname [AD server name here]     java.naming.provider.url= ldap://[AD server name here]
         java.naming.factory.initial= com.sun.jndi.ldap.LdapCtxFactory
         java.naming.ldap.version= 3
         com.sun.jndi.ldap.connect.timeout= 25000
         connection_pool_name= [AD server name here]     java.naming.security.principal= [AD user account name here]
         java.naming.security.authentication= simple
         java.naming.security.credentials= ******
         [EXCEPTION: No connection to the ldap server]
    Critical shutdown was invoked. Reason is: Core service com.sap.security.core.ume.service failed. J2EE Engine cannot be started.#

    Hi Sasu,
    Check the steps in the below link.check the authorization for JSF user
    http://help.sap.com/saphelp_nw04/helpdata/en/20/361941edd5ef23e10000000a155106/frameset.htm
    Koti Reddy

  • Error While Using J2EE Engine

    Hi all,
    We have recently restarted our CRM Server and when we were trying to Start the J2EE Engine (version 6.2) server the following error is being displayed on the console after loading service manager.
    ID000539: Classload error; Can't load service telnet because referenced service
    shell not found
    Can someone help me in resolving this error.
    Thanks and regards,
    vijaya sai.v

    Hello Vijayasai,
    I cannot tell you why the shell service cannot be found as I need to have a look at the logs and even at the system. Most probably some manual changes were done, which cause these inconsistencies. I would suggest you to report a customer message.
    As for the other error, it is most probably caused by the fact that the native parts of the jco library are not found in the path/library path. As it is a CRM installation I think that the J2ee Engine is started from the R3 server. Have you changed the go script of the dispatcher? Usually it changes the path/library path so that the required libraries are loaded by default. The j2ee dispatcher starts the server node as its child process and it inherits its environment. Again this is just a suggestion as in order to investigate the problem I would need to have a look at the logs.
    Best Regards
    Vyara

  • Firefox will not start and I get firefox.exe Application Error with the code 0x00000000, I've tried reloading but always get the same error message!

    Firefox will not start, I've tried opening in safe mode, no joy. I get the firefox.exe application error 0x00000000
    == This happened ==
    Every time Firefox opened
    == Possibly after a windows update ==
    == User Agent ==
    Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 5.1; YPC 3.2.0; .NET CLR 1.1.4322; InfoPath.1)

    Do a clean reinstall and download a fresh Firefox copy from http://www.mozilla.com/firefox/all.html and save the file to the desktop.
    Uninstall your current Firefox version and remove the Firefox program folder before installing that copy of the Firefox installer.
    It is important to delete the Firefox program folder to remove all the files and make sure that there are no problems with files that were leftover after uninstalling.
    See http://kb.mozillazine.org/Standard_diagnostic_-_Firefox#Clean_reinstall

  • Error in starting J2ee Engine-- Pls Help!!!

    I am getting the following error. i have checked the property sheet within "services" folder many times but not sure how to change or what to change the value for "guest" user too...
    =======================ERROR=============================
    Service dbpool started. (3108 ms).
      Service com.sap.security.core.ume.service started. (2608 ms).
      service security ================= ERROR =================
    Core service security failed. J2EE Engine cannot be started.
    com.sap.engine.services.security.exceptions.SecurityServiceException: Unexpected exception:
         at com.sap.engine.services.security.SecurityServerFrame.start(SecurityServerFrame.java:186)
         at com.sap.engine.core.service630.container.ServiceRunner.startApplicationServiceFrame(ServiceRunner.java:201)
         at com.sap.engine.core.service630.container.ServiceRunner.run(ServiceRunner.java:142)
         at com.sap.engine.frame.core.thread.Task.run(Task.java:60)
         at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:73)
         at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:145)
    Caused by: com.sap.engine.services.security.exceptions.BaseSecurityException: Anonymous principal not configured
         at com.sap.engine.services.security.login.SecurityContext.setAnonymousPrincipal(SecurityContext.java:504)
         at com.sap.engine.services.security.SecurityServerFrame.start(SecurityServerFrame.java:150)
         ... 5 more
    Caused by: com.sap.security.core.server.userstore.UserstoreException: Could not get user J2EE_GUEST
         at com.sap.security.core.server.userstore.UserContextUME.engineGetUserInfo(UserContextUME.java:187)
         at com.sap.engine.services.security.userstore.context.UserContext.getUserInfo(UserContext.java:87)
         at com.sap.engine.services.security.login.SecurityContext.setAnonymousPrincipal(SecurityContext.java:498)
         ... 6 more
    Caused by: com.sap.security.api.NoSuchUserAccountException: USER_AUTH_FAILED: User account for logonid "J2EE_GUEST" not found!
         at com.sap.security.core.imp.AbstractUserAccount.<init>(AbstractUserAccount.java:334)
         at com.sap.security.core.imp.DBTextFileUserAccount.<init>(DBTextFileUserAccount.java:56)
         at com.sap.security.core.imp.UserAccountFactory.getUserAccountByLogonId(UserAccountFactory.java:339)
         at com.sap.security.core.imp.UserAccountFactory.getUserAccountByLogonId(UserAccountFactory.java:277)
         at com.sap.security.core.imp.UserAccountFactory.getUserAccountByLogonId(UserAccountFactory.java:371)
         at com.sap.security.core.imp.UserAccountFactory.getUserAccountByLogonId(UserAccountFactory.java:366)
         at com.sap.security.core.server.userstore.UserContextUME.engineGetUserInfo(UserContextUME.java:183)
         ... 8 more
    com.sap.engine.services.security.exceptions.SecurityServiceException: Unexpected exception:
         at com.sap.engine.services.security.SecurityServerFrame.start(SecurityServerFrame.java:186)
         at com.sap.engine.core.service630.container.ServiceRunner.startApplicationServiceFrame(ServiceRunner.java:201)
         at com.sap.engine.core.service630.container.ServiceRunner.run(ServiceRunner.java:142)
         at com.sap.engine.frame.core.thread.Task.run(Task.java:60)
         at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:73)
         at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:145)
    Caused by: com.sap.engine.services.security.exceptions.BaseSecurityException: Anonymous principal not configured
         at com.sap.engine.services.security.login.SecurityContext.setAnonymousPrincipal(SecurityContext.java:504)
         at com.sap.engine.services.security.SecurityServerFrame.start(SecurityServerFrame.java:150)
         ... 5 more
    Caused by: com.sap.security.core.server.userstore.UserstoreException: Could not get user J2EE_GUEST
         at com.sap.security.core.server.userstore.UserContextUME.engineGetUserInfo(UserContextUME.java:187)
         at com.sap.engine.services.security.userstore.context.UserContext.getUserInfo(UserContext.java:87)
         at com.sap.engine.services.security.login.SecurityContext.setAnonymousPrincipal(SecurityContext.java:498)
         ... 6 more
    Caused by: com.sap.security.api.NoSuchUserAccountException: USER_AUTH_FAILED: User account for logonid "J2EE_GUEST" not found!
         at com.sap.security.core.imp.AbstractUserAccount.<init>(AbstractUserAccount.java:334)
         at com.sap.security.core.imp.DBTextFileUserAccount.<init>(DBTextFileUserAccount.java:56)
         at com.sap.security.core.imp.UserAccountFactory.getUserAccountByLogonId(UserAccountFactory.java:339)
         at com.sap.security.core.imp.UserAccountFactory.getUserAccountByLogonId(UserAccountFactory.java:277)
         at com.sap.security.core.imp.UserAccountFactory.getUserAccountByLogonId(UserAccountFactory.java:371)
         at com.sap.security.core.imp.UserAccountFactory.getUserAccountByLogonId(UserAccountFactory.java:366)
         at com.sap.security.core.server.userstore.UserContextUME.engineGetUserInfo(UserContextUME.java:183)
         ... 8 more
    [Framework -> criticalShutdown] Core service security failed. J2EE Engine cannot be started.
    Mar 6, 2005 9:41:21 PM              com.sap.engine.core.Framework [SAPEngine_System_Thread[impl:5]_45] Fatal: Critical shutdown was invoked. Reason is: Core service security failed. J2EE Engine cannot be started.
    ==========================================================

    Hi Tony,
    This is a known issue:
    Please check
    SAP Note 956867 - USER_AUTH_FAILED: User account for logonid "Guest" not found
    Regards,
    Siddhesh

  • Error while starting J2EE Engine:com.sap.security.core.persistence.datasour

    I would like to ask for your help to look into the problem being encountered  in starting J2EE Engine
    Caused by: com.sap.security.core.persistence.datasource.PersistenceException: Name or password is incorrect (repeat logon)
    At first we identified that the user EPQASCONNECT was not created in R3 QAS system, we have created this one. At the same time, we have changed the ume.r3.connection.master.passwd to reflect the password set in R3 QAS. But still it is not working.
    Also, checking the trace file for server0, the rc code is -11113.
    The following users SAPJSF,J2EE_GUEST and J2EE_admin were not locked.
    Followed the http://help.sap.com/saphelp_nw70/helpdata/EN/45/1bbdccc7850064e10000000a1553f7/frameset.htm. link to make changes.
    The problem raised after the system refresh in QAS system. License was also installed after System refresh.
    ERROR:
    stdout/stderr redirect
    node name   : server0
    pid         : 5088
    system name : EQ7
    system nr.  : 03
    started at  : Tue Nov 25 17:24:12 2008
    Reserved 1610612736 (0x60000000) bytes before loading DLLs.
    [Thr 5444] MtxInit: -2 0 0
    CompilerOracle: exclude com/sapportals/portal/pb/layout/taglib/ContainerTag addIviewResources
    CompilerOracle: exclude com/sap/engine/services/keystore/impl/security/CodeBasedSecurityConnector getApplicationDomain
    CompilerOracle: exclude com/sap/engine/services/rmi_p4/P4StubSkeletonGenerator generateStub
    CompilerOracle: exclude com/sapportals/portal/prt/util/StringUtils escapeToJS
    CompilerOracle: exclude com/sapportals/portal/prt/core/broker/PortalServiceItem startServices
    CompilerOracle: exclude com/sap/engine/services/webservices/server/deploy/WSConfigurationHandler downloadFile
    CompilerOracle: exclude com/sapportals/portal/prt/jndisupport/util/AbstractHierarchicalContext lookup
    CompilerOracle: exclude com/sapportals/portal/navigation/cache/CacheNavigationNode getAttributeValue
    CompilerOracle: exclude com/sapportals/portal/navigation/TopLevelNavigationiView PrintNode
    CompilerOracle: exclude com/sapportals/wcm/service/ice/wcm/ICEPropertiesCoder encode
    CompilerOracle: exclude com/sap/lcr/pers/delta/importing/ObjectLoader loadObjects
    CompilerOracle: exclude com/sap/engine/services/webservices/jaxrpc/encoding/InstanceBuilder readElement
    CompilerOracle: exclude com/sap/engine/services/webservices/jaxrpc/encoding/InstanceBuilder readSequence
    CompilerOracle: exclude com/sap/engine/services/webservices/jaxrpc/encoding/TypeMappingImpl initializeRelations
    CompilerOracle: exclude com/sap/engine/services/webservices/jaxrpc/encoding/GeneratedComplexType _loadInto
    SAP J2EE Engine Version 7.00   PatchLevel is starting...
    Error occurred while preloading classes of security providers from jre/lib/ext folder: java.util.zip.ZipException: The filename, directory name, or volume label syntax is incorrect
    Loading: LogManager ... 1078 ms.
    Loading: PoolManager ... 16 ms.
    Loading: ApplicationThreadManager ... 94 ms.
    Loading: ThreadManager ... 31 ms.
    Loading: IpVerificationManager ... 16 ms.
    Loading: ClassLoaderManager ... 16 ms.
    Loading: ClusterManager ... 390 ms.
    Loading: LockingManager ... 125 ms.
    Loading: ConfigurationManager ... 0.000: [GC 0.000: [ParNew: 87039K->2386K(130560K), 0.0150914 secs] 87039K->2386K(1005056K), 0.0152223 secs]
    4969 ms.
    Loading: LicensingManager ... 47 ms.
    Loading: CacheManager ... 359 ms.
    Loading: ServiceManager ...
    Loading services.:
      Service DQE started. (0 ms).
      Service memory started. (47 ms).
      Service cross started. (47 ms).
      Service file started. (156 ms).
      Service timeout started. (109 ms).
      Service runtimeinfo started. (15 ms).
      Service trex.service started. (94 ms).
      Service cafeucc~api started. (141 ms).
      Service userstore started. (47 ms).
      Service jmx_notification started. (47 ms).
      Service p4 started. (297 ms).
      Service classpath_resolver started. (31 ms).
    9.789: [GC 9.789: [ParNew: 89426K->9626K(130560K), 0.0389830 secs] 89426K->9626K(1005056K), 0.0390998 secs]
      Service log_configurator started. (5797 ms).
      Service locking started. (16 ms).
      Service http started. (328 ms).
      Service naming started. (469 ms).
      Service failover started. (141 ms).
      Service appclient started. (188 ms).
      Service ts started. (235 ms).
      Service javamail started. (250 ms).
      Service licensing started. (0 ms).
      Service jmsconnector started. (312 ms).
      Service connector started. (391 ms).
      Service iiop started. (312 ms).
      Service webservices started. (766 ms).
    19.167: [GC 19.167: [ParNew: 96666K->19159K(130560K), 0.0812264 secs] 96666K->19159K(1005056K), 0.0813454 secs]
      Service deploy started. (15422 ms).
      Service MigrationService started. (47 ms).
      Service configuration started. (62 ms).
      Service bimmrdeployer started. (31 ms).
    24.849: [GC 24.849: [ParNew: 106199K->17756K(130560K), 0.0546511 secs] 106199K->17756K(1005056K), 0.0547691 secs]
      Service dbpool started. (2688 ms).
      Service cafeugpmailcf started. (62 ms).
    Nov 25, 2008 5:24:47 PM         com.sap.security.core.persistence [SAPEngine_System_Thread[impl:5]_70] Fatal: User Management Engine (com.sap.security.core.persistence.datasource.imp.R3Persistence) failed to connect to the ABAP backend system. Check that connection data are correct and the backend system is available. Error message: "Name or password is incorrect (repeat logon)". Connection data (obtained from properties of UME service in section "ume.r3.connection.master.": "{
      passwd=********
      lang=EN
      receiverid=master
      sysnr=01
      client=888
      poolmaxsize=10
      user=SAPJSF
      receiverid_guest=master
      ashost=R3DEVSER
    Nov 25, 2008 5:24:47 PM         com.sap.security.core.persistence [SAPEngine_System_Thread[impl:5]_70] Fatal: Initialization of UME persistence adapter "R3_DATASOURCE" failed.
      service com.sap.security.core.ume.service ================= ERROR =================
    Core service com.sap.security.core.ume.service failed. J2EE Engine cannot be started.
    com.sap.engine.frame.ServiceException: <Localization failed: ResourceBundle='com.sap.engine.frame.KernelResourceBundle', ID='UME initialization failed.', Arguments: []> : Can't find resource for bundle java.util.PropertyResourceBundle, key UME initialization failed.
         at com.sap.security.core.server.ume.service.UMEServiceFrame.start(UMEServiceFrame.java:372)
         at com.sap.engine.frame.ApplicationFrameAdaptor.start(ApplicationFrameAdaptor.java:31)
         at com.sap.engine.core.service630.container.ServiceRunner.startApplicationServiceFrame(ServiceRunner.java:214)
         at com.sap.engine.core.service630.container.ServiceRunner.run(ServiceRunner.java:144)
         at com.sap.engine.frame.core.thread.Task.run(Task.java:64)
         at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:79)
         at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:150)
    Caused by: com.sap.security.core.persistence.datasource.PersistenceException: Name or password is incorrect (repeat logon)
         at com.sap.security.core.persistence.datasource.imp.R3PersistenceBase.newPersistenceException(R3PersistenceBase.java:178)
         at com.sap.security.core.persistence.datasource.imp.R3PersistenceBase.init(R3PersistenceBase.java:446)
         at com.sap.security.core.persistence.imp.PrincipalDatabagFactoryInstance.<init>(PrincipalDatabagFactoryInstance.java:338)
         at com.sap.security.core.persistence.imp.PrincipalDatabagFactory.newInstance(PrincipalDatabagFactory.java:156)
         at com.sap.security.core.persistence.imp.PrincipalDatabagFactory.getInstance(PrincipalDatabagFactory.java:109)
         at com.sap.security.core.persistence.imp.PrincipalDatabagFactory.getInstance(PrincipalDatabagFactory.java:56)
         at com.sap.security.core.InternalUMFactory.initializeUME(InternalUMFactory.java:259)
         at com.sap.security.core.server.ume.service.UMEServiceFrame.start(UMEServiceFrame.java:279)
         ... 6 more
    com.sap.engine.frame.ServiceException: <Localization failed: ResourceBundle='com.sap.engine.frame.KernelResourceBundle', ID='UME initialization failed.', Arguments: []> : Can't find resource for bundle java.util.PropertyResourceBundle, key UME initialization failed.
         at com.sap.security.core.server.ume.service.UMEServiceFrame.start(UMEServiceFrame.java:372)
         at com.sap.engine.frame.ApplicationFrameAdaptor.start(ApplicationFrameAdaptor.java:31)
         at com.sap.engine.core.service630.container.ServiceRunner.startApplicationServiceFrame(ServiceRunner.java:214)
         at com.sap.engine.core.service630.container.ServiceRunner.run(ServiceRunner.java:144)
         at com.sap.engine.frame.core.thread.Task.run(Task.java:64)
         at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:79)
         at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:150)
    Caused by: com.sap.security.core.persistence.datasource.PersistenceException: Name or password is incorrect (repeat logon)
         at com.sap.security.core.persistence.datasource.imp.R3PersistenceBase.newPersistenceException(R3PersistenceBase.java:178)
         at com.sap.security.core.persistence.datasource.imp.R3PersistenceBase.init(R3PersistenceBase.java:446)
         at com.sap.security.core.persistence.imp.PrincipalDatabagFactoryInstance.<init>(PrincipalDatabagFactoryInstance.java:338)
         at com.sap.security.core.persistence.imp.PrincipalDatabagFactory.newInstance(PrincipalDatabagFactory.java:156)
         at com.sap.security.core.persistence.imp.PrincipalDatabagFactory.getInstance(PrincipalDatabagFactory.java:109)
         at com.sap.security.core.persistence.imp.PrincipalDatabagFactory.getInstance(PrincipalDatabagFactory.java:56)
         at com.sap.security.core.InternalUMFactory.initializeUME(InternalUMFactory.java:259)
         at com.sap.security.core.server.ume.service.UMEServiceFrame.start(UMEServiceFrame.java:279)
         ... 6 more
    [Framework -> criticalShutdown] Core service com.sap.security.core.ume.service failed. J2EE Engine cannot be started.
    Nov 25, 2008 5:24:47 PM             com.sap.engine.core.Framework [SAPEngine_System_Thread[impl:5]_70] Fatal: Critical shutdown was invoked. Reason is: Core service com.sap.security.core.ume.service failed. J2EE Engine cannot be started.
    stdout/stderr redirect
    node name   : server0
    pid         : 5088
    system name : EQ7
    system nr.  : 03
    started at  : Tue Nov 25 17:24:52 2008
    Reserved 1610612736 (0x60000000) bytes before loading DLLs.
    [Thr 4672] MtxInit: -2 0 0
    CompilerOracle: exclude com/sapportals/portal/pb/layout/taglib/ContainerTag addIviewResources
    CompilerOracle: exclude com/sap/engine/services/keystore/impl/security/CodeBasedSecurityConnector getApplicationDomain
    CompilerOracle: exclude com/sap/engine/services/rmi_p4/P4StubSkeletonGenerator generateStub
    CompilerOracle: exclude com/sapportals/portal/prt/util/StringUtils escapeToJS
    CompilerOracle: exclude com/sapportals/portal/prt/core/broker/PortalServiceItem startServices
    CompilerOracle: exclude com/sap/engine/services/webservices/server/deploy/WSConfigurationHandler downloadFile
    CompilerOracle: exclude com/sapportals/portal/prt/jndisupport/util/AbstractHierarchicalContext lookup
    CompilerOracle: exclude com/sapportals/portal/navigation/cache/CacheNavigationNode getAttributeValue
    CompilerOracle: exclude com/sapportals/portal/navigation/TopLevelNavigationiView PrintNode
    CompilerOracle: exclude com/sapportals/wcm/service/ice/wcm/ICEPropertiesCoder encode
    CompilerOracle: exclude com/sap/lcr/pers/delta/importing/ObjectLoader loadObjects
    CompilerOracle: exclude com/sap/engine/services/webservices/jaxrpc/encoding/InstanceBuilder readElement
    CompilerOracle: exclude com/sap/engine/services/webservices/jaxrpc/encoding/InstanceBuilder readSequence
    CompilerOracle: exclude com/sap/engine/services/webservices/jaxrpc/encoding/TypeMappingImpl initializeRelations
    CompilerOracle: exclude com/sap/engine/services/webservices/jaxrpc/encoding/GeneratedComplexType _loadInto
    SAP J2EE Engine Version 7.00   PatchLevel is starting...
    Error occurred while preloading classes of security providers from jre/lib/ext folder: java.util.zip.ZipException: The filename, directory name, or volume label syntax is incorrect
    Loading: LogManager ... 672 ms.
    Loading: PoolManager ... 0 ms.
    Loading: ApplicationThreadManager ... 93 ms.
    Loading: ThreadManager ... 16 ms.
    Loading: IpVerificationManager ... 16 ms.
    Loading: ClassLoaderManager ... 31 ms.
    Loading: ClusterManager ... 234 ms.
    Loading: LockingManager ... 110 ms.
    Loading: ConfigurationManager ... 0.000: [GC 0.000: [ParNew: 87040K->2403K(130560K), 0.0136260 secs] 87040K->2403K(1005056K), 0.0137788 secs]
    3203 ms.
    Loading: LicensingManager ... 31 ms.
    Loading: CacheManager ... 203 ms.
    Loading: ServiceManager ...
    Loading services.:
      Service DQE started. (0 ms).
      Service memory started. (47 ms).
      Service cross started. (32 ms).
      Service file started. (47 ms).
      Service timeout started. (63 ms).
      Service runtimeinfo started. (0 ms).
      Service trex.service started. (63 ms).
      Service cafeucc~api started. (203 ms).
      Service p4 started. (328 ms).
      Service jmx_notification started. (78 ms).
      Service userstore started. (78 ms).
      Service classpath_resolver started. (46 ms).
    6.865: [GC 6.865: [ParNew: 89443K->9702K(130560K), 0.0411006 secs] 89443K->9702K(1005056K), 0.0412578 secs]
      Service log_configurator started. (6141 ms).
      Service locking started. (0 ms).
      Service naming started. (484 ms).
      Service failover started. (172 ms).
      Service appclient started. (219 ms).
      Service http started. (813 ms).
      Service jmsconnector started. (422 ms).
      Service ts started. (422 ms).
      Service javamail started. (469 ms).
      Service connector started. (453 ms).
      Service licensing started. (110 ms).
      Service iiop started. (313 ms).
      Service webservices started. (1063 ms).
    16.407: [GC 16.407: [ParNew: 96742K->19088K(130560K), 0.0834244 secs] 96742K->19088K(1005056K), 0.0835901 secs]
      Service deploy started. (15859 ms).
      Service MigrationService started. (47 ms).
      Service configuration started. (47 ms).
      Service bimmrdeployer started. (16 ms).
    22.173: [GC 22.173: [ParNew: 106113K->17739K(130560K), 0.0551702 secs] 106113K->17739K(1005056K), 0.0553234 secs]
      Service dbpool started. (2625 ms).
      Service cafeugpmailcf started. (78 ms).
    Nov 25, 2008 5:25:22 PM         com.sap.security.core.persistence [SAPEngine_System_Thread[impl:5]_62] Fatal: User Management Engine (com.sap.security.core.persistence.datasource.imp.R3Persistence) failed to connect to the ABAP backend system. Check that connection data are correct and the backend system is available. Error message: "Name or password is incorrect (repeat logon)". Connection data (obtained from properties of UME service in section "ume.r3.connection.master.": "{
      passwd=********
      lang=EN
      receiverid=master
      sysnr=01
      client=888
      poolmaxsize=10
      user=SAPJSF
      receiverid_guest=master
      ashost=R3DEVSER
    Nov 25, 2008 5:25:22 PM         com.sap.security.core.persistence [SAPEngine_System_Thread[impl:5]_62] Fatal: Initialization of UME persistence adapter "R3_DATASOURCE" failed.
      service com.sap.security.core.ume.service ================= ERROR =================
    Core service com.sap.security.core.ume.service failed. J2EE Engine cannot be started.
    com.sap.engine.frame.ServiceException: <Localization failed: ResourceBundle='com.sap.engine.frame.KernelResourceBundle', ID='UME initialization failed.', Arguments: []> : Can't find resource for bundle java.util.PropertyResourceBundle, key UME initialization failed.
         at com.sap.security.core.server.ume.service.UMEServiceFrame.start(UMEServiceFrame.java:372)
         at com.sap.engine.frame.ApplicationFrameAdaptor.start(ApplicationFrameAdaptor.java:31)
         at com.sap.engine.core.service630.container.ServiceRunner.startApplicationServiceFrame(ServiceRunner.java:214)
         at com.sap.engine.core.service630.container.ServiceRunner.run(ServiceRunner.java:144)
         at com.sap.engine.frame.core.thread.Task.run(Task.java:64)
         at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:79)
         at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:150)
    Caused by: com.sap.security.core.persistence.datasource.PersistenceException: Name or password is incorrect (repeat logon)
         at com.sap.security.core.persistence.datasource.imp.R3PersistenceBase.newPersistenceException(R3PersistenceBase.java:178)
         at com.sap.security.core.persistence.datasource.imp.R3PersistenceBase.init(R3PersistenceBase.java:446)
         at com.sap.security.core.persistence.imp.PrincipalDatabagFactoryInstance.<init>(PrincipalDatabagFactoryInstance.java:338)
         at com.sap.security.core.persistence.imp.PrincipalDatabagFactory.newInstance(PrincipalDatabagFactory.java:156)
         at com.sap.security.core.persistence.imp.PrincipalDatabagFactory.getInstance(PrincipalDatabagFactory.java:109)
         at com.sap.security.core.persistence.imp.PrincipalDatabagFactory.getInstance(PrincipalDatabagFactory.java:56)
         at com.sap.security.core.InternalUMFactory.initializeUME(InternalUMFactory.java:259)
         at com.sap.security.core.server.ume.service.UMEServiceFrame.start(UMEServiceFrame.java:279)
         ... 6 more
    com.sap.engine.frame.ServiceException: <Localization failed: ResourceBundle='com.sap.engine.frame.KernelResourceBundle', ID='UME initialization failed.', Arguments: []> : Can't find resource for bundle java.util.PropertyResourceBundle, key UME initialization failed.
         at com.sap.security.core.server.ume.service.UMEServiceFrame.start(UMEServiceFrame.java:372)
         at com.sap.engine.frame.ApplicationFrameAdaptor.start(ApplicationFrameAdaptor.java:31)
         at com.sap.engine.core.service630.container.ServiceRunner.startApplicationServiceFrame(ServiceRunner.java:214)
         at com.sap.engine.core.service630.container.ServiceRunner.run(ServiceRunner.java:144)
         at com.sap.engine.frame.core.thread.Task.run(Task.java:64)
         at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:79)
         at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:150)
    Caused by: com.sap.security.core.persistence.datasource.PersistenceException: Name or password is incorrect (repeat logon)
         at com.sap.security.core.persistence.datasource.imp.R3PersistenceBase.newPersistenceException(R3PersistenceBase.java:178)
         at com.sap.security.core.persistence.datasource.imp.R3PersistenceBase.init(R3PersistenceBase.java:446)
         at com.sap.security.core.persistence.imp.PrincipalDatabagFactoryInstance.<init>(PrincipalDatabagFactoryInstance.java:338)
         at com.sap.security.core.persistence.imp.PrincipalDatabagFactory.newInstance(PrincipalDatabagFactory.java:156)
         at com.sap.security.core.persistence.imp.PrincipalDatabagFactory.getInstance(PrincipalDatabagFactory.java:109)
         at com.sap.security.core.persistence.imp.PrincipalDatabagFactory.getInstance(PrincipalDatabagFactory.java:56)
         at com.sap.security.core.InternalUMFactory.initializeUME(InternalUMFactory.java:259)
         at com.sap.security.core.server.ume.service.UMEServiceFrame.start(UMEServiceFrame.java:279)
         ... 6 more
    [Framework -> criticalShutdown] Core service com.sap.security.core.ume.service failed. J2EE Engine cannot be started.
    Nov 25, 2008 5:25:22 PM             com.sap.engine.core.Framework [SAPEngine_System_Thread[impl:5]_62] Fatal: Critical shutdown was invoked. Reason is: Core service com.sap.security.core.ume.service failed. J2EE Engine cannot be started.
    stdout/stderr redirect
    node name   : server0
    pid         : 5088
    system name : EQ7
    system nr.  : 03
    started at  : Tue Nov 25 17:25:27 2008
    Reserved 1610612736 (0x60000000) bytes before loading DLLs.
    [Thr 9304] MtxInit: -2 0 0
    CompilerOracle: exclude com/sapportals/portal/pb/layout/taglib/ContainerTag addIviewResources
    CompilerOracle: exclude com/sap/engine/services/keystore/impl/security/CodeBasedSecurityConnector getApplicationDomain
    CompilerOracle: exclude com/sap/engine/services/rmi_p4/P4StubSkeletonGenerator generateStub
    CompilerOracle: exclude com/sapportals/portal/prt/util/StringUtils escapeToJS
    CompilerOracle: exclude com/sapportals/portal/prt/core/broker/PortalServiceItem startServices
    CompilerOracle: exclude com/sap/engine/services/webservices/server/deploy/WSConfigurationHandler downloadFile
    CompilerOracle: exclude com/sapportals/portal/prt/jndisupport/util/AbstractHierarchicalContext lookup
    CompilerOracle: exclude com/sapportals/portal/navigation/cache/CacheNavigationNode getAttributeValue
    CompilerOracle: exclude com/sapportals/portal/navigation/TopLevelNavigationiView PrintNode
    CompilerOracle: exclude com/sapportals/wcm/service/ice/wcm/ICEPropertiesCoder encode
    CompilerOracle: exclude com/sap/lcr/pers/delta/importing/ObjectLoader loadObjects
    CompilerOracle: exclude com/sap/engine/services/webservices/jaxrpc/encoding/InstanceBuilder readElement
    CompilerOracle: exclude com/sap/engine/services/webservices/jaxrpc/encoding/InstanceBuilder readSequence
    CompilerOracle: exclude com/sap/engine/services/webservices/jaxrpc/encoding/TypeMappingImpl initializeRelations
    CompilerOracle: exclude com/sap/engine/services/webservices/jaxrpc/encoding/GeneratedComplexType _loadInto
    SAP J2EE Engine Version 7.00   PatchLevel is starting...
    Error occurred while preloading classes of security providers from jre/lib/ext folder: java.util.zip.ZipException: The filename, directory name, or volume label syntax is incorrect
    Loading: LogManager ... 656 ms.
    Loading: PoolManager ... 0 ms.
    Loading: ApplicationThreadManager ... 94 ms.
    Loading: ThreadManager ... 15 ms.
    Loading: IpVerificationManager ... 16 ms.
    Loading: ClassLoaderManager ... 31 ms.
    Loading: ClusterManager ... 219 ms.
    Loading: LockingManager ... 94 ms.
    Loading: ConfigurationManager ... 0.000: [GC 0.000: [ParNew: 87040K->2414K(130560K), 0.0145828 secs] 87040K->2414K(1005056K), 0.0147378 secs]
    3015 ms.
    Loading: LicensingManager ... 47 ms.
    Loading: CacheManager ... 172 ms.
    Loading: ServiceManager ...
    Loading services.:
      Service DQE started. (0 ms).
      Service memory started. (47 ms).
      Service cross started. (31 ms).
      Service file started. (63 ms).
      Service timeout started. (46 ms).
      Service runtimeinfo started. (16 ms).
      Service trex.service started. (78 ms).
      Service cafeucc~api started. (156 ms).
      Service p4 started. (282 ms).
      Service classpath_resolver started. (32 ms).
      Service userstore started. (15 ms).
      Service jmx_notification started. (47 ms).
    6.784: [GC 6.784: [ParNew: 89454K->9721K(130560K), 0.0417499 secs] 89454K->9721K(1005056K), 0.0419073 secs]
      Service log_configurator started. (5266 ms).
      Service locking started. (0 ms).
      Service http started. (406 ms).
      Service naming started. (469 ms).
      Service failover started. (94 ms).
      Service javamail started. (250 ms).
      Service ts started. (235 ms).
      Service appclient started. (250 ms).
      Service licensing started. (31 ms).
      Service jmsconnector started. (329 ms).
      Service connector started. (406 ms).
      Service iiop started. (312 ms).
      Service webservices started. (688 ms).
    16.028: [GC 16.028: [ParNew: 96761K->19104K(130560K), 0.0751680 secs] 96761K->19104K(1005056K), 0.0753377 secs]
      Service deploy started. (15438 ms).
      Service MigrationService started. (47 ms).
      Service bimmrdeployer started. (16 ms).
      Service configuration started. (62 ms).
    21.840: [GC 21.840: [ParNew: 106140K->17748K(130560K), 0.0443068 secs] 106140K->17748K(1005056K), 0.0444546 secs]
      Service dbpool started. (2656 ms).
      Service cafeugpmailcf started. (78 ms).
    Nov 25, 2008 5:25:57 PM         com.sap.security.core.persistence [SAPEngine_System_Thread[impl:5]_63] Fatal: User Management Engine (com.sap.security.core.persistence.datasource.imp.R3Persistence) failed to connect to the ABAP backend system. Check that connection data are correct and the backend system is available. Error message: "Name or password is incorrect (repeat logon)". Connection data (obtained from properties of UME service in section "ume.r3.connection.master.": "{
      passwd=********
      lang=EN
      receiverid=master
      sysnr=01
      client=888
      poolmaxsize=10
      user=SAPJSF
      receiverid_guest=master
      ashost=R3DEVSER
    Nov 25, 2008 5:25:57 PM         com.sap.security.core.persistence [SAPEngine_System_Thread[impl:5]_63] Fatal: Initialization of UME persistence adapter "R3_DATASOURCE" failed.
      service com.sap.security.core.ume.service ================= ERROR =================
    Core service com.sap.security.core.ume.service failed. J2EE Engine cannot be started.
    com.sap.engine.frame.ServiceException: <Localization failed: ResourceBundle='com.sap.engine.frame.KernelResourceBundle', ID='UME initialization failed.', Arguments: []> : Can't find resource for bundle java.util.PropertyResourceBundle, key UME initialization failed.
         at com.sap.security.core.server.ume.service.UMEServiceFrame.start(UMEServiceFrame.java:372)
         at com.sap.engine.frame.ApplicationFrameAdaptor.start(ApplicationFrameAdaptor.java:31)
         at com.sap.engine.core.service630.container.ServiceRunner.startApplicationServiceFrame(ServiceRunner.java:214)
         at com.sap.engine.core.service630.container.ServiceRunner.run(ServiceRunner.java:144)
         at com.sap.engine.frame.core.thread.Task.run(Task.java:64)
         at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:79)
         at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:150)
    Caused by: com.sap.security.core.persistence.datasource.PersistenceException: Name or password is incorrect (repeat logon)
         at com.sap.security.core.persistence.datasource.imp.R3PersistenceBase.newPersistenceException(R3PersistenceBase.java:178)
         at com.sap.security.core.persistence.datasource.imp.R3PersistenceBase.init(R3PersistenceBase.java:446)
         at com.sap.security.core.persistence.imp.PrincipalDatabagFactoryInstance.<init>(PrincipalDatabagFactoryInstance.java:338)
         at com.sap.security.core.persistence.imp.PrincipalDatabagFactory.newInstance(PrincipalDatabagFactory.java:156)
         at com.sap.security.core.persistence.imp.PrincipalDatabagFactory.getInstance(PrincipalDatabagFactory.java:109)
         at com.sap.security.core.persistence.imp.PrincipalDatabagFactory.getInstance(PrincipalDatabagFactory.java:56)
         at com.sap.security.core.InternalUMFactory.initializeUME(InternalUMFactory.java:259)
         at com.sap.security.core.server.ume.service.UMEServiceFrame.start(UMEServiceFrame.java:279)
         ... 6 more
    com.sap.engine.frame.ServiceException: <Localization failed: ResourceBundle='com.sap.engine.frame.KernelResourceBundle', ID='UME initialization failed.', Arguments: []> : Can't find resource for bundle java.util.PropertyResourceBundle, key UME initialization failed.
         at com.sap.security.core.server.ume.service.UMEServiceFrame.start(UMEServiceFrame.java:372)
         at com.sap.engine.frame.ApplicationFrameAdaptor.start(ApplicationFrameAdaptor.java:31)
         at com.sap.engine.core.service630.container.ServiceRunner.startApplicationServiceFrame(ServiceRunner.java:214)
         at com.sap.engine.core.service630.container.ServiceRunner.run(ServiceRunner.java:144)
         at com.sap.engine.frame.core.thread.Task.run(Task.java:64)
         at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:79)
         at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:150)
    Caused by: com.sap.security.core.persistence.datasource.PersistenceException: Name or password is incorrect (repeat logon)
         at com.sap.security.core.persistence.datasource.imp.R3PersistenceBase.newPersistenceException(R3PersistenceBase.java:178)
         at com.sap.security.core.persistence.datasource.imp.R3PersistenceBase.init(R3PersistenceBase.java:446)
         at com.sap.security.core.persistence.imp.PrincipalDatabagFactoryInstance.<init>(PrincipalDatabagFactoryInstance.java:338)
         at com.sap.security.core.persistence.imp.PrincipalDatabagFactory.newInstance(PrincipalDatabagFactory.java:156)
         at com.sap.security.core.persistence.imp.PrincipalDatabagFactory.getInstance(PrincipalDatabagFactory.java:109)
         at com.sap.security.core.persistence.imp.PrincipalDatabagFactory.getInstance(PrincipalDatabagFactory.java:56)
         at com.sap.security.core.InternalUMFactory.initializeUME(InternalUMFactory.java:259)
         at com.sap.security.core.server.ume.service.UMEServiceFrame.start(UMEServiceFrame.java:279)
         ... 6 more
    [Framework -> criticalShutdown] Core service com.sap.security.core.ume.service failed. J2EE Engine cannot be started.
    Nov 25, 2008 5:25:57 PM             com.sap.engine.core.Framework [SAPEngine_System_Thread[impl:5]_63] Fatal: Critical shutdown was invoked. Reason is: Core service com.sap.security.core.ume.service failed. J2EE Engine cannot be started.
    stdout/stderr redirect
    node name   : server0
    pid         : 5088
    system name : EQ7
    system nr.  : 03
    started at  : Tue Nov 25 17:25:58 2008
    Reserved 1610612736 (0x60000000) bytes before loading DLLs.
    [Thr 8240] MtxInit: -2 0 0
    CompilerOracle: exclude com/sapportals/portal/pb/layout/taglib/ContainerTag addIviewResources
    CompilerOracle: exclude com/sap/engine/services/keystore/impl/security/CodeBasedSecurityConnector getApplicationDomain
    CompilerOracle: exclude com/sap/engine/services/rmi_p4/P4StubSkeletonGenerator generateStub
    CompilerOracle: exclude com/sapportals/portal/prt/util/StringUtils escapeToJS
    CompilerOracle: exclude com/sapportals/portal/prt/core/broker/PortalServiceItem startServices
    CompilerOracle: exclude com/sap/engine/services/webservices/server/deploy/WSConfigurationHandler downloadFile
    CompilerOracle: exclude com/sapportals/portal/prt/jndisupport/util/AbstractHierarchicalContext lookup
    CompilerOracle: exclude com/sapportals/portal/navigation/cache/CacheNavigationNode getAttributeValue
    CompilerOracle: exclude com/sapportals/portal/navigation/TopLevelNavigationiView PrintNode
    CompilerOracle: exclude com/sapportals/wcm/service/ice/wcm/ICEPropertiesCoder encode
    CompilerOracle: exclude com/sap/lcr/pers/delta/importing/ObjectLoader loadObjects
    CompilerOracle: exclude com/sap/engine/services/webservices/jaxrpc/encoding/InstanceBuilder readElement
    CompilerOracle: exclude com/sap/engine/services/webservices/jaxrpc/encoding/InstanceBuilder readSequence
    CompilerOracle: exclude com/sap/engine/services/webservices/jaxrpc/encoding/TypeMappingImpl initializeRelations
    CompilerOracle: exclude com/sap/engine/services/webservices/jaxrpc/encoding/GeneratedComplexType _loadInto
    SAP J2EE Engine Version 7.00   PatchLevel is starting...
    Error occurred while preloading classes of security providers from jre/lib/ext folder: java.util.zip.ZipException: The filename, directory name, or volume label syntax is incorrect
    Loading: LogManager ... 656 ms.
    Loading: PoolManager ... 0 ms.
    Loading: ApplicationThreadManager ... 94 ms.
    Loading: ThreadManager ... 31 ms.
    Loading: IpVerificationManager ... 15 ms.
    Loading: ClassLoaderManager ... 16 ms.
    Loading: ClusterManager ... 266 ms.
    Loading: LockingManager ... 79 ms.
    Loading: ConfigurationManager ... 0.000: [GC 0.000: [ParNew: 87039K->2718K(130560K), 0.0175167 secs] 87039K->2718K(1005056K), 0.0176768 secs]
    4250 ms.
    Loading: LicensingManager ... 46 ms.
    Loading: CacheManager ... 250 ms.
    Loading: ServiceManager ...
    Loading services.:
      Service DQE started. (15 ms).
      service telnet ================= ERROR =================
      Service memory started. (31 ms).
      Service cross started. (32 ms).
      Service file started. (63 ms).
    7.854: [GC 7.855: [ParNew: 89758K->7739K(130560K), 0.0387127 secs] 89758K->7739K(1005056K), 0.0388651 secs]
      Service timeout started. (94 ms).
      Service runtimeinfo started. (15 ms).
      Service cafeucc~api started. (141 ms).
      Service trex.service started. (141 ms).
      Service userstore started. (79 ms).
      Service jmx_notification started. (47 ms).
      Service p4 started. (375 ms).
      Service classpath_resolver started. (47 ms).
      Service log_configurator started. (6343 ms).
      Service locking started. (0 ms).
      Service naming started. (641 ms).
      Service failover started. (172 ms).
      Service ts started. (281 ms).
      Service appclient started. (187 ms).
      Service javamail started. (312 ms).
      Service licensing started. (31 ms).
      Service jmsconnector started. (297 ms).
      Service http started. (1000 ms).
      Service connector started. (453 ms).
      Service iiop started. (281 ms).
      Service webservices started. (906 ms).
    16.628: [GC 16.628: [ParNew: 94779K->15719K(130560K), 0.0715624 secs] 94779K->15719K(1005056K), 0.0717470 secs]
    23.824: [GC 23.824: [ParNew: 102759K->17568K(130560K), 0.0594877 secs] 102759K->17568K(1005056K), 0.0596196 secs]
      Service deploy started. (21469 ms).
      Service configuration started. (47 ms).
      Service bimmrdeployer started. (15 ms).
      Service MigrationService started. (78 ms).
      Service dbpool started. (3641 ms).
    33.638: [GC 33.638: [ParNew: 104608K->20954K(130560K), 0.0721131 secs] 104608K->20954K(1005056K), 0.0722444 secs]
      Service cafeugpmailcf started. (156 ms).
    Nov 25, 2008 5:26:38 PM         com.sap.security.core.persistence [SAPEngine_System_Thread[impl:5]_71] Fatal: User Management Engine (com.sap.security.core.persistence.datasource.imp.R3Persistence) failed to connect to the ABAP backend system. Check that connection data are correct and the backend system is available. Error message: "Name or password is incorrect (repeat logon)". Connection data (obtained from properties of UME service in section "ume.r3.connection.master.": "{
      passwd=********
      lang=EN
      receiverid=master
      sysnr=01
      client=888
      poolmaxsize=10
      user=SAPJSF
      receiverid_guest=master
      ashost=R3DEVSER
    Nov 25, 2008 5:26:38 PM         com.sap.security.core.persistence [SAPEngine_System_Thread[impl:5]_71] Fatal: Initialization of UME persistence adapter "R3_DATASOURCE" failed.
      service com.sap.security.core.ume.service ================= ERROR =================
    Core service com.sap.security.core.ume.service failed. J2EE Engine cannot be started.
    com.sap.engine.frame.ServiceException: <Localization failed: ResourceBundle='com.sap.engine.frame.KernelResourceBundle', ID='UME initialization failed.', Arguments: []> : Can't find resource for bundle java.util.PropertyResourceBundle, key UME initialization failed.
         at com.sap.security.core.server.ume.service.UMEServiceFrame.start(UMEServiceFrame.java:372)
         at com.sap.engine.frame.ApplicationFrameAdaptor.start(ApplicationFrameAdaptor.java:31)
         at com.sap.engine.core.service630.container.ServiceRunner.startApplicationServiceFrame(ServiceRunner.java:214)
         at com.sap.engine.core.service630.container.ServiceRunner.run(ServiceRunner.java:144)
         at com.sap.engine.frame.core.thread.Task.run(Task.java:64)
         at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:79)
         at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:105)
    Caused by: com.sap.security.core.persistence.datasource.PersistenceException: Name or password is incorrect (repeat logon)
         at com.sap.security.core.persistence.datasource.imp.R3PersistenceBase.newPersistenceException(R3PersistenceBase.java:178)
         at com.sap.security.core.persistence.datasource.imp.R3PersistenceBase.init(R3PersistenceBase.java:446)
         at com.sap.security.core.persistence.imp.PrincipalDatabagFactoryInstance.<init>(PrincipalDatabagFactoryInstance.java:338)
         at com.sap.security.core.persistence.imp.PrincipalDatabagFactory.newInstance(PrincipalDatabagFactory.java:156)
         at com.sap.security.core.persistence.imp.PrincipalDatabagFactory.getInstance(PrincipalDatabagFactory.java:109)
         at com.sap.security.core.persistence.imp.PrincipalDatabagFactory.getInstance(PrincipalDatabagFactory.java:56)
         at com.sap.security.core.InternalUMFactory.initializeUME(InternalUMFactory.java:259)
         at com.sap.security.core.server.ume.service.UMEServiceFrame.start(UMEServiceFrame.java:279)
         ... 6 more
    com.sap.engine.frame.ServiceException: <Localization failed: ResourceBundle='com.sap.engine.frame.KernelResourceBundle', ID='UME initialization failed.', Arguments: []> : Can't find resource for bundle java.util.PropertyResourceBundle, key UME initialization failed.
         at com.sap.security.core.server.ume.service.UMEServiceFrame.start(UMEServiceFrame.java:372)
         at com.sap.engine.frame.ApplicationFrameAdaptor.start(ApplicationFrameAdaptor.java:31)
         at com.sap.engine.core.service630.container.ServiceRunner.startApplicationServiceFrame(ServiceRunner.java:214)
         at com.sap.engine.core.service630.container.ServiceRunner.run(ServiceRunner.java:144)
         at com.sap.engine.frame.core.thread.Task.run(Task.java:64)
         at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:79)
         at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:105)
    Caused by: com.sap.security.core.persistence.datasource.PersistenceException: Name or password is incorrect (repeat logon)
         at com.sap.security.core.persistence.datasource.imp.R3PersistenceBase.newPersistenceException(R3PersistenceBase.java:178)
         at com.sap.security.core.persistence.datasource.imp.R3PersistenceBase.init(R3PersistenceBase.java:446)
         at com.sap.security.core.persistence.imp.PrincipalDatabagFactoryInstance.<init>(PrincipalDatabagFactoryInstance.java:338)
         at com.sap.security.core.persistence.imp.PrincipalDatabagFactory.newInstance(PrincipalDatabagFactory.java:156)
         at com.sap.security.core.persistence.imp.PrincipalDatabagFactory.getInstance(PrincipalDatabagFactory.java:109)
         at com.sap.security.core.persistence.imp.PrincipalDatabagFactory.getInstance(PrincipalDatabagFactory.java:56)
         at com.sap.security.core.InternalUMFactory.initializeUME(InternalUMFactory.java:259)
         at com.sap.security.core.server.ume.service.UMEServiceFrame.start(UMEServiceFrame.java:279)
         ... 6 more
    [Framework -> criticalShutdown] Core service com.sap.security.core.ume.service failed. J2EE Engine cannot be started.
    Nov 25, 2008 5:26:38 PM             com.sap.engine.core.Framework [SAPEngine_System_Thread[impl:5]_71] Fatal: Critical shutdown was invoked. Reason is: Core service com.sap.security.core.ume.service failed. J2EE Engine cannot be started.
    Regards,
    Ramana

    Hi Friends,
    Issue got resolved.. Sorry for delay reply.
    The following parameters need to check in Config tool.
    ume.r3.connection.master.client -
    ume.r3.connection.master.user -
    ume.r3.connection.master.passwrd
    ume.r3.connection.master.ashost
    ume.r3.connection.master.sysnr
    ume.datasource
    Regards,
    Ramana

  • 6300 'Application error' with Sensor

    i've had lots of fun using Sensor but all of a sudden to my horror Sensor stopped working, im getting an
    'Application error' when i loads up and the
    'Details' are
    "com.nokia.mid.appl.sensor.S...(small text at top of screen)
    Security
    java/lang/SecurityException
    Access denied"
    i've tried reinstalling it with a backup from andy29b (thanks mate) but still the same error, i've tried restoring it with a backup of my phone + memory card using PC Suite but the backup log showed that it only restore the Sensor '.jad' file.
    Please help
    Thanks

    update:
    i figured if i highlight Sensor press 'Options' go to
    'Application access>Data access>Add and edit data' there is 4 option:
    "Ask every time
    Ask first time only (disabled-grey)
    Always allowed (disabled-grey)
    Not allowed (highlighted)"
    when i change this option to 'Ask every time' Sensor doesn't give me the 'Application error' any more but its not usable because it continuously asks to 'Allow application to edit and add new data in: Gallery' less then every second, i need to set this to 'Ask first time only' or 'Always allowed' but it wont let me
    does anyone have a solution
    and just incase my Sensor>Options>Details is:
    Name: Sensor
    Size: 320 kB
    Created: 11-10-2007 07:37
    Version: 1.23
    Vendor: Nokia
    Certificate: No

Maybe you are looking for