Upgrade 640 to 700: ERROR is BI : com.sap.ip.bi.sdk.dac.connector

Hello Experts,
I am doing the java system upgrade from NW04 to NW04s SR2. During the "Deploy Online" phase, the upgrade is failing due to below error
EAR file uploaded to server for 31ms.
07/11/10 05:34:18 -  ERROR: Not deployed. Deploy Service returned ERROR:
                     java.rmi.RemoteException: Cannot deploy application sap.com/com.sap.ip.bi.sdk.dac.connector.checko..
                     Reason: Application alias [TOdbo] for application [sap.com/com.sap.ip.bi.sdk.dac.connector.checko] already exists in the HTTP Provider Service. The application that holds this alias is [sap.com/com.sap.ip.bi.sdk.dac.connector.checkodbo].; nested exception is:
                          com.sap.engine.services.deploy.container.DeploymentException: <--Localization failed: ResourceBundle='com.sap.engine.services.deploy.DeployResourceBundle', ID='com.sap.engine.services.servlets_jsp.server.exceptions.WebDeploymentException: Application alias [TOdbo] for application [sap.com/com.sap.ip.bi.sdk.dac.connector.checko] already exists in the HTTP Provider Service. The application that holds this alias is [sap.com/com.sap.ip.bi.sdk.dac.connector.checkodbo].
Error: Aborted: D:\usr\sap\JUPGRADE\data\archives\BIUDI09_0.SCA
Please suggest asap.
Regards,
Thulasi

Dear David,
this is not SAP support, this is a user forum. If you want to issue a support ticket you should go to the SAP service marketplace and issue an OSS message. This can be done at http://service.sap.com/message .
You need an S-User to access this site.
Regards,
Benny

Similar Messages

  • Problem Installing WAS with com.sap.ip.bi.sdk.dac.connector.odbo

    Hi,
    we are installing the WAS640, and we get the following error:
    Deployment started Tue Mar 15 20:45:09 CET 2005
    ===========================================================================
    Starting Deployment of com.sap.ip.bi.sdk.dac.connector.odbo
    Aborted: development component 'com.sap.ip.bi.sdk.dac.connector.odbo'/'sap.com'/'SAP AG'/:
    Caught exception during module deployment from SAP J2EE Engine's deploy service:
    java.rmi.RemoteException:
    Cannot deploy application sap.com/com.sap.ip.bi.sdk.dac.connector.odbo..
    Reason: Cannot access methods of instance of class "com.sap.ip.bi.sdk.dac.connector.odbo.OdboManagedConnectionFactory".
    If anyone has any ideas.
    Thanks and regards,
    Tomas.
    p.s. the full dump...
    Deployment started Tue Mar 15 20:45:09 CET 2005
    ===========================================================================
    Starting Deployment of com.sap.ip.bi.sdk.dac.connector.odbo
    Aborted: development component 'com.sap.ip.bi.sdk.dac.connector.odbo'/'sap.com'/'SAP AG'/:
    Caught exception during module deployment from SAP J2EE Engine's deploy service:
    java.rmi.RemoteException: Cannot deploy application sap.com/com.sap.ip.bi.sdk.dac.connector.odbo.. Reason: Cannot access methods of instance of class "com.sap.ip.bi.sdk.dac.connector.odbo.OdboManagedConnectionFactory". Possible reasons: the class is not public and is in another package, the current method does not have access to the appropriate zero-argument constructor or there is no such method.; nested exception is:      com.sap.engine.services.deploy.container.DeploymentException: <--Localization failed: ResourceBundle='com.sap.engine.services.deploy.DeployResourceBundle', ID='com.sap.engine.services.connector.exceptions.BaseDeploymentException: Cannot access methods of instance of class "com.sap.ip.bi.sdk.dac.connector.odbo.OdboManagedConnectionFactory". Possible reasons: the class is not public and is in another package, the current method does not have access to the appropriate zero-argument constructor or there is no such method.
         at com.sap.engine.services.connector.jca.deploy.DeployAdmin.instantiateMCF(DeployAdmin.java:1211)
         at com.sap.engine.services.connector.jca.deploy.ContainerImpl.makeUpdate(ContainerImpl.java:859)
         at com.sap.engine.services.deploy.server.application.UpdateTransaction.makeComponents(UpdateTransaction.java:376)
         at com.sap.engine.services.deploy.server.application.DeployUtilTransaction.commonBegin(DeployUtilTransaction.java:379)
         at com.sap.engine.services.deploy.server.application.UpdateTransaction.begin(UpdateTransaction.java:148)
         at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesOnOneServer(ApplicationTransaction.java:290)
         at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhases(ApplicationTransaction.java:323)
         at com.sap.engine.services.deploy.server.DeployServiceImpl.makeGlobalTransaction(DeployServiceImpl.java:3033)
         at com.sap.engine.services.deploy.server.DeployServiceImpl.update(DeployServiceImpl.java:679)
         at com.sap.engine.services.deploy.server.DeployServiceImplp4_Skel.dispatch(DeployServiceImplp4_Skel.java:926)
         at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:294)
         at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:183)
         at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.request(P4SessionProcessor.java:119)
         at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:37)
         at com.sap.engine.core.cluster.impl6.session.UnorderedChannel$MessageRunner.run(UnorderedChannel.java:71)
         at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
         at java.security.AccessController.doPrivileged(Native Method)
         at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:94)
         at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:162)
    Caused by: java.lang.NoSuchMethodException: com.sap.ip.bi.sdk.dac.connector.odbo.OdboManagedConnectionFactory.setLogonAsUserID(java.lang.String)
         at java.lang.Class.getMethod(Class.java:986)
         at com.sap.engine.services.connector.jca.deploy.DeployAdmin.instantiateMCF(DeployAdmin.java:1187)
         ... 18 more
    ', Arguments: []--> : Can't find resource for bundle java.util.PropertyResourceBundle, key com.sap.engine.services.connector.exceptions.BaseDeploymentException: Cannot access methods of instance of class "com.sap.ip.bi.sdk.dac.connector.odbo.OdboManagedConnectionFactory". Possible reasons: the class is not public and is in another package, the current method does not have access to the appropriate zero-argument constructor or there is no such method.
         at com.sap.engine.services.connector.jca.deploy.DeployAdmin.instantiateMCF(DeployAdmin.java:1211)
         at com.sap.engine.services.connector.jca.deploy.ContainerImpl.makeUpdate(ContainerImpl.java:859)
         at com.sap.engine.services.deploy.server.application.UpdateTransaction.makeComponents(UpdateTransaction.java:376)
         at com.sap.engine.services.deploy.server.application.DeployUtilTransaction.commonBegin(DeployUtilTransaction.java:379)
         at com.sap.engine.services.deploy.server.application.UpdateTransaction.begin(UpdateTransaction.java:148)
         at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesOnOneServer(ApplicationTransaction.java:290)
         at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhases(ApplicationTransaction.java:323)
         at com.sap.engine.services.deploy.server.DeployServiceImpl.makeGlobalTransaction(DeployServiceImpl.java:3033)
         at com.sap.engine.services.deploy.server.DeployServiceImpl.update(DeployServiceImpl.java:679)
         at com.sap.engine.services.deploy.server.DeployServiceImplp4_Skel.dispatch(DeployServiceImplp4_Skel.java:926)
         at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:294)
         at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:183)
         at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.request(P4SessionProcessor.java:119)
         at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:37)
         at com.sap.engine.core.cluster.impl6.session.UnorderedChannel$MessageRunner.run(UnorderedChannel.java:71)
         at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
         at java.security.AccessController.doPrivileged(Native Method)
         at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:94)
         at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:162)
    Caused by: java.lang.NoSuchMethodException: com.sap.ip.bi.sdk.dac.connector.odbo.OdboManagedConnectionFactory.setLogonAsUserID(java.lang.String)
         at java.lang.Class.getMethod(Class.java:986)
         at com.sap.engine.services.connector.jca.deploy.DeployAdmin.instantiateMCF(DeployAdmin.java:1187)
         ... 18 more
    (message ID: com.sap.sdm.serverext.servertype.inqmy.extern.EngineSingleModuleOnlineDeployerImpl.performAction(DeploymentActionTypes).REMEXC)
    Deployment of com.sap.ip.bi.sdk.dac.connector.odbo finished with Error (Duration 6281 ms)
    Message was edited by: Tomas Altman
    Message was edited by: Tomas Altman

    Hi
    I had this same problem. Fixed it by reading the sp-stack manual.
    I bounced my instance and then stopped the connectors. Thereafter the deploy when through fine.
    Regards

  • Error in import com.sap.mbs.ca.ur.enum.MessageType

    Hi,
    I try to import MAM30 SP5 in NWDS (7.1 SP03). After doing that I get an error that class com.sap.mbs.ca.ur.enum.MessageType; is missing.
    In fact this class is part of the mbsui.jar file which is located in the lib folder of my application. MessageType class is in there.
    mbsui.jar is added to my build path.
    But the strange thing is that if i look at the jar file in NWDS, then i see that package com.sap.mbs.ca.ur.enum is missing, all the other packages for this jar file are there. What can be the reason for this?
    I also have noticed that this question was already posted on this forum, but there the problem was that mbsui.jar was not added to the lib folder. This is not the issue in my case.
    What could be the reason that one package of mbsui.jar is not seen by NWDS? I also copied the jar file, added this new jar file manually to the lib folder, also add this new jar file to my build path, everything except the com.sap.mbs.ca.ur.enum was succesfully included in the application.
    thanks for your help
    regards
    Peter

    I was reading through this post and wanted to add on some more inputs. The above error mentioned is due to the fact that Java 1.5 uses enum as a reserved keyword, where java 1.4 did not. So if we need to migrate to java 1.5 then we would get a compile error if we use the reserved keywords as a variable or a package name. This is the reason why with the latest version sap compatible with java 1.5 & above has moved the package names which were using enum.
    Hope this helps.

  • Error com.sap.aii.af.sdk.xi.util.URI$MalformedURIException: no scheme

    Hi,
    I am registering the following error in a SOAP Sender Communication Channel, it's very strange because of in the Development Environment everything worked fine.
    com.sap.aii.af.sdk.xi.util.URI$MalformedURIException: no scheme
    The Scenario is the following:
    Sender: SOAP
    Receiver: ABAP Proxy (Using the XI configuration)
    I configured all the scenario to use only the Adapter Engine instead the Integration Server and, as I explained in the previous paragraph it worked fine in Development environment.
    Does anybody know what could be going on?
    Thank a lot for your help.
    Kind Regards,
    Victoria

    Hello Victoria,
    Can you please check if the inbound address for SOAP messages should be as follow.Other wise you will exceptions.
    : http://host:port/XISOAPAdapter/MessageServlet?channel=party:service:channel
    Under
    party:service:channelenter the party name, the service name, and the
    name of the communication channel. If no party has been created, enter the
    following: channel=:service:channel
    Kind Regards
    Praveen Reddy

  • RFC Error : Commit fault: com.sap.aii.af.rfc.afcommunication

    Hi ,
    I am having a problem in a RFC to File scenario. My Sender RFC is working fine and is showing the status green in the CC Monitoring in AdapterEngine under Component Monitoring. But we are trying to trigger the data to the RFC we are getting the following error "Commit fault: com.sap.aii.af.rfc.afcommunication.R
    fcAFWException: alterna "
    The RFC connection when tested it is ok .. the connection is established.
    Please suggest.
    Regards,
    Hemanthika

    Hi,
    1. Refer to the following notes
    SAP Note 730870
    SAP Note 775765
    Also check
    RFC Error in SM58 Commit fault
    RFC Error in SM58 Commit fault com.sap.aii.af.rfc.afcommunication
    2. have a look to R/3 transaction SM58 to find your message
    Thanks
    swarup

  • Error during server runtime installation - com.sap.js.jpaas.sdk

    When adding the Runtime Enviroment for SAP HANA Cloud:
    From which location the SAP HANA Cloud Platform SDK can be found?
    On-screen help tells, that the location must contain com.sap.js.jpaas.sdk, but none of my downloads from "Getting Started" does contain a file with that name.
    The validation of Server "SAP HANA Cloud Platform" was error free when assigning C:\...\neo-java-web-sdk-2.3.3, but with Runtime Environment this SDK is not working.

    neo-java-web-sdk-2.x is to be used with Java Web Tomcat 7 (Beta) runtime. For SAP HANA Cloud runtime, either neo-java-web 1.x or neo-javaee6-wp 2.x should be used. This will be handled better with the next update of the Platform tools. Sorry for the confusion.

  • Com.sap.ip.bi.sdk.exception.BIResourceException: OLAP

    hi experts ,
    i am able to connect to SAP system but the olap operations are not supported
    my code :
    ManagedConnectionFactory mcf;
    IConnectionFactory cf;
    IConnectionSpec cs;
    mcf = new SapqManagedConnectionFactory();
    cf = (IConnectionFactory) mcf.createConnectionFactory();
    cs = cf.getConnectionSpec();
    cs.setPropertyValue(SapqConnectionConstants.USERNAME.toString(),"*******");
    // Password
    cs.setPropertyValue(SapqConnectionConstants.PASSWORD.toString(),"*******");
    // CLIENT
    cs.setPropertyValue(SapqConnectionConstants.CLIENT.toString(), "000");
    cs.setPropertyValue(SapqConnectionConstants.APPLICATIONSERVER.toString(),"131.x.x.x");
    cs.setPropertyValue(SapqConnectionConstants.LANGUAGE.toString(),"EN");
    cs.setPropertyValue(SapqConnectionConstants.SYSTEMNUMBER.toString(),"00");
    IBIConnection connection = (IBIConnection) cf.getConnectionEx(cs);
    System.out.println(connection.toString());
    getting the connection object working well till here
    IBIOlap olap = connection.getOlap();
    the above statement i am setting an error com.sap.ip.bi.sdk.exception.BIResourceException: OLAP connections are not supported
    Thanks,
    satish

    I've got the same problem/message. What is the solution?

  • Portal Runtime error when modifying: com.sap.portal.runtime.logon.par

    Hello,
    We need some help because we get 'Portal Runtime error: iView: N/A Component Name:N/A' error when trying to access portal logon screen.
    This is what we've done:
    We've modified com.sap.portal.runtime.logon.par file and we've uploaded it but it doesn't work. Because of the error, we've overwritten this file with the original one but now it's imposible to access portal.
    The situation it seems to be like before the modification of the .par file but we get the same error and can't access portal.
    Please, do you know what could be the problem?
    Thanks in advance

    Hi Belen,
    Here are the steps you would need to take
    1. import the original par file into the NWDS and name the project as  
        com.sap.portal.runtime.logon
    2. Make sure the project name is com.sap.portal.runtime.logon
    3. use winzip/winrar to extract the com.sap.portal.runtime.logon.par file in
        a local directory
    4.Under the lib you would find two jar files copy them and paste them in your project
       under dist>PORTAL-INF>lib directory
    5.move the files cert....till umResetPass....jsp into the  PORTAL-INF directory
    6. export the par to the server in question
    7. restart your server
    This should solve your problem..
    Thanks,
    Gokul

  • Error for package com.sap.aii.mapping.lookup

    Hi All
    I am writing a code for the DB lookup. When I import the package in the Message
    Mapping (Advance Function) I am getting an Error.
    C:/usr/sap/SXI/DVEBMGS00/j2ee/cluster/server0/./temp/classpath_resolver/Map6af6f7d1335111dc9b51000c2967ead8/source/com/sap/xi/tf/_MM_File2JMS_.java:3: package com.sap.aii.mapping.lookup does not exist
    import com.sap.aii.mappingtool.tf3.;import com.sap.aii.mappingtool.tf3.rt.;import java.util.;import java.io.; import java.lang.reflect.;import com.sap.aii.mapping.lookup.; ^
    C:/usr/sap/SXI/DVEBMGS00/j2ee/cluster/server0/./temp/classpath_resolver/Map6af6f7d1335111dc9b51000c2967ead8/source/com/sap/xi/tf/_MM_File2JMS_.java:57: cannot resolve symbol symbol : class Channel location: class com.sap.xi.tf._MM_File2JMS_ Channel channel = null;
    C:/usr/sap/SXI/DVEBMGS00/j2ee/cluster/server0/./temp/classpath_resolver/Map6af6f7d1335111dc9b51000c2967ead8/source/com/sap/xi/tf/_MM_File2JMS_.java:58: cannot resolve symbol symbol : class DataBaseAccessor location: class com.sap.xi.tf._MM_File2JMS_ DataBaseAccessor accessor = null; ^
    Thanks
    Farooq.

    Hey satish I am getting same Error:
    C:/usr/sap/SXI/DVEBMGS00/j2ee/cluster/server0/./temp/classpath_resolver/Map7801d381335311dc8660000c2967ead8/source/com/sap/xi/tf/_MM_File2JMS_.java:3: package com.sap.aii.mapping.lookup does not exist import com.sap.aii.mappingtool.tf3.;import com.sap.aii.mappingtool.tf3.rt.;import java.util.;import java.io.; import java.lang.reflect.;import com.sap.aii.mapping.lookup.;import java.io.*; ^ C:/usr/sap/SXI/DVEBMGS00/j2ee/cluster/server0/./temp/classpath_resolver/Map7801d381335311dc8660000c2967ead8/source/com/sap/xi/tf/_MM_File2JMS_.java:57: cannot resolve symbol symbol : class Channel location: class com.sap.xi.tf._MM_File2JMS_ Channel channel = null; ^ C:/usr/sap/SXI/DVEBMGS00/j2ee/cluster/server0/./temp/classpath_resolver/Map7801d381335311dc8660000c2967ead8/source/com/sap/xi/tf/_MM_File2JMS_.java:58: cannot resolve symbol symbol : class DataBaseAccessor location: class com.sap.xi.tf._MM_File2JMS_ DataBaseAccessor accessor = null; ^ 3 errors

  • Deployment error in referencing "com.sap.km.application"

    Hi,
    I am working on uploading documents on KM. I have added following sharing references into the project.
    ---com.sap.portal.htmlb
    ---com.sap.km.application
    But i am getting following error:
    ->Failed to start application sap.com/testattach: The referenced application com.sap.portal.htmlb cannot be started. Check the causing exception for details. Hint: Is the referenced application deployed correctly on the server?
    ->Failed to start application sap.com/testattach: The referenced application com.sap.km.application cannot be started. Check the causing exception for details. Hint: Is the referenced application deployed correctly on the server?
    Please guide me how to come out of this.

    I was reading through this post and wanted to add on some more inputs. The above error mentioned is due to the fact that Java 1.5 uses enum as a reserved keyword, where java 1.4 did not. So if we need to migrate to java 1.5 then we would get a compile error if we use the reserved keywords as a variable or a package name. This is the reason why with the latest version sap compatible with java 1.5 & above has moved the package names which were using enum.
    Hope this helps.

  • Modify MDM record error through WebDynpro: com.sap.mdm.internal.protocol.ma

    When I use MDM java api thruogh WebDynpro portal try to save a record to MDM, I got this error:
    com.sap.internal.protocol.manual.ServerException: The selected node has children.
    Any help will be appriciated.

    Jitesh:
    thanks for your answer. It is great help.
    Let me put this way, if that is the problems cause, this only happens for one category when I try to save. I can save records to other category through portal application. So it is not portal problem.
    Then we come to MDM, how do I find out what is wrong with this category? Why other categories work and this one does not work?
    How do I find out why I have reference to parent node instead of leaf node for this category?
    What I can do in MDM side to find problem?
    thanks,
    Eric

  • Com.sap.connectivity.cs.extended.connectionserver error in webi

    Hi
    I am getting the below error in webi.
    com.sap.connectivity.cs.extended.connectionserver error in webi while running the report.
    Please let us know ASAP.

    We have raised SAP note for this and we got the solution.
    Create new APS server and
    add the following required services to the APS
    "DSL Bridge Service"
    "Adaptive Connectivity Service"
    SAP Note for this
    0001775372   Error csEx WIS 00000 when trying to create a web intelligence document
    Regards
    Gaurav Mang.

  • 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

  • Com.sap.mw.jco.JCO$Exception: (103) RFC_ERROR_LOGON_FAILURE: Name or passwo

    Hi All,
    I'm configuring the Solution Manager Diagnostics.
    I have all my agent SMD and IS installed.... but when I run the Setup Wizard, I received the following error:
    Step Wilyhost Agent Details
    Created destination BD1_DVEBMGS00_server0
    Created destination SapStartSrv_bnsr3dci_BD1_00
    Created destination BD1|bnsr3dci_BD1_00
    Created action SAP GC|BD1_DVEBMGS00_server0 - SAP GC|BD1_DVEBMGS00_server0
    Created action BD1|bnsr3dci_BD1_00 - SapStartSrv_bnsr3dci_BD1_00
    Created action BD1 - BD1 AbapSystem
    Created action BD1|bnsr3dci_BD1_00 - BD1|bnsr3dci_BD1_00 AbapInstance
    Created 4 action(s).
    0 Wilyhost Agent(s) from host bnsr3dci are connected to the EM.
    Wilyhost Agent configuration finished without errors, but on Enterprise Manager (bnssmpci.bns.local:6001) no Wilyhost Agent was detected from host bnsr3dci. Please check the log file jvm_smdagent.out whether the Wilyhost Agent could connect to the Enterprise Manager. If the Enterprise Manager configuration has been changed recently please restart the SMD Agent on OS level.
    and checking the jvm_smdagent.out file on managed system
    Running SMD Agent ...
    [ms://bnssmpci:8101/P4] Agent ready.
    10/27/09 02:58:19 PM EDT [INFO] [IntroscopeAgent] Introscope Agent Release 8.0.2.0 (Build 470970)
    10/27/09 02:58:19 PM EDT [INFO] [IntroscopeAgent] Using Java VM version "SAP Java Server VM 1.5.0_17" from SAP AG
    10/27/09 02:58:19 PM EDT [INFO] [IntroscopeAgent] Trying to load agent profile based on system property "com.wily.introscope.agentProfile"
    10/27/09 02:58:19 PM EDT [INFO] [IntroscopeAgent] Trying to load file from /usr/sap/DAD/SMDA97/SMDAgent/applications.config/com.sap.smd.agent.application.wily
    host/IntroscopeSapAgent.profile
    10/27/09 02:58:19 PM EDT [INFO] [IntroscopeAgent] Loaded file from /usr/sap/DAD/SMDA97/SMDAgent/applications.config/com.sap.smd.agent.application.wilyhost/Int
    roscopeSapAgent.profile
    10/27/09 02:58:19 PM EDT [INFO] [IntroscopeAgent] Agent Metric Aging is turned off
    10/27/09 02:58:19 PM EDT [INFO] [IntroscopeAgent] Agent Metric Aging: property introscope.agent.metricAging.heartbeatInterval is set to 1800
    10/27/09 02:58:19 PM EDT [INFO] [IntroscopeAgent] Agent Metric Aging: property introscope.agent.metricAging.dataChunk is set to 500
    10/27/09 02:58:19 PM EDT [INFO] [IntroscopeAgent] Agent Metric Aging: property introscope.agent.metricAging.numberTimeslices is set to 3000
    10/27/09 02:58:19 PM EDT [INFO] [IntroscopeAgent] Looking for agent profile property "introscope.agent.extensions.directory" to locate the extensions director
    y.
    10/27/09 02:58:19 PM EDT [INFO] [IntroscopeAgent] The agent extensions directory /sap_mirrlog/sap/DAD/SMDA97/SMDAgent/applications.config/com.sap.smd.agent.ap
    plication.wilyhost/ext was successfully located
    10/27/09 02:58:19 PM EDT [INFO] [IntroscopeAgent] Introscope Agent startup complete.
    10/27/09 02:58:19 PM EDT [INFO] [IntroscopeAgent] The Agent will attempt to determine its name.
    10/27/09 02:58:19 PM EDT [INFO] [IntroscopeAgent] Using the Agent name "SAP HostAgent SMDA97" based on the value of the System Property "com.wily.introscope.a
    gent.agentName".
    10/27/09 02:58:19 PM EDT [INFO] [IntroscopeAgent] Initial agent name set to SAP HostAgent SMDA97
    10/27/09 02:58:19 PM EDT [INFO] [IntroscopeAgent.Isengard] Initiating connection attempts to the Introscope Enterprise Manager.
    10/27/09 02:58:19 PM EDT [INFO] [IntroscopeAgent.Isengard] The Agent reconnection delay is set to 15 second(s).
    10/27/09 02:58:19 PM EDT [INFO] [IntroscopeAgent] Started Error Reporting service
    Warning ! Protocol Implementation [com.sap.engine.services.webservices.jaxrpc.wsdl2java.features.builtin.MessageIdProtocol] could not be loaded (NoClassDefFoundError) !
    Error Message is :com/sap/guid/GUIDGeneratorFactory
    10/27/09 02:58:20 PM EDT [WARN] [IntroscopeAgent.ConnectionThread] Failed to connect to the Introscope Enterprise Manager at localhost:6001,com.wily.isengard.
    postofficehub.link.net.DefaultSocketFactory (1).
    Initialization done.
    10/27/09 02:58:30 PM EDT [WARN] [IntroscopeAgent.ConnectionThread] Failed to connect to the Introscope Enterprise Manager at localhost:6001,com.wily.isengard.
    postofficehub.link.net.DefaultSocketFactory (2).
    10/27/09 02:58:40 PM EDT [WARN] [IntroscopeAgent.ConnectionThread] Failed to connect to the Introscope Enterprise Manager at localhost:6001,com.wily.isengard.
    postofficehub.link.net.DefaultSocketFactory (3).
    10/27/09 02:58:50 PM EDT [WARN] [IntroscopeAgent.ConnectionThread] Failed to connect to the Introscope Enterprise Manager at localhost:6001,com.wily.isengard.
    postofficehub.link.net.DefaultSocketFactory (4).
    10/27/09 02:59:00 PM EDT [WARN] [IntroscopeAgent.ConnectionThread] Failed to connect to the Introscope Enterprise Manager at localhost:6001,com.wily.isengard.
    postofficehub.link.net.DefaultSocketFactory (5).
    10/27/09 02:59:11 PM EDT [WARN] [IntroscopeAgent.ConnectionThread] Failed to connect to the Introscope Enterprise Manager at localhost:6001,com.wily.isengard.
    postofficehub.link.net.DefaultSocketFactory (6).
    10/27/09 02:59:21 PM EDT [WARN] [IntroscopeAgent.ConnectionThread] Failed to connect to the Introscope Enterprise Manager at localhost:6001,com.wily.isengard.
    postofficehub.link.net.DefaultSocketFactory (7).
    10/27/09 02:59:31 PM EDT [WARN] [IntroscopeAgent.ConnectionThread] Failed to connect to the Introscope Enterprise Manager at localhost:6001,com.wily.isengard.
    postofficehub.link.net.DefaultSocketFactory (8).
    10/27/09 02:59:41 PM EDT [WARN] [IntroscopeAgent.ConnectionThread] Failed to connect to the Introscope Enterprise Manager at localhost:6001,com.wily.isengard.
    postofficehub.link.net.DefaultSocketFactory (9).
    10/27/09 02:59:51 PM EDT [WARN] [IntroscopeAgent.ConnectionThread] Failed to connect to the Introscope Enterprise Manager at localhost:6001,com.wily.isengard.
    postofficehub.link.net.DefaultSocketFactory (10).
    10/27/09 02:59:51 PM EDT [INFO] [IntroscopeAgent.ConnectionThread] The Agent will continue to attempt to connect to Introscope Enterprise Manager. Further fai
    lures will not be logged.
    [ms://bnssmpci:8101/P4] Agent ready.
    Warning ! Protocol Implementation [com.sap.engine.services.webservices.jaxrpc.wsdl2java.features.builtin.MessageIdProtocol] could not be loaded (NoClassDefFoundError) !
    Error Message is :com/sap/guid/GUIDGeneratorFactory
    Initialization done.
    Warning ! Protocol Implementation [com.sap.engine.services.webservices.jaxrpc.wsdl2java.features.builtin.MessageIdProtocol] could not be loaded (NoClassDefFoundError) !
    Error Message is :com/sap/guid/GUIDGeneratorFactory
    Warning ! Protocol Implementation [com.sap.engine.services.webservices.jaxrpc.wsdl2java.features.builtin.MessageIdProtocol] could not be loaded (NoClassDefFoundError) !
    Error Message is :com/sap/guid/GUIDGeneratorFactory
    Warning ! Protocol Implementation [com.sap.engine.services.webservices.jaxrpc.wsdl2java.features.builtin.MessageIdProtocol] could not be loaded (NoClassDefFoundError) !
    Error Message is :com/sap/guid/GUIDGeneratorFactory
    Warning ! Protocol Implementation [com.sap.engine.services.webservices.jaxrpc.wsdl2java.features.builtin.MessageIdProtocol] could not be loaded (NoClassDefFoundError) !
    Error Message is :com/sap/guid/GUIDGeneratorFactory
    Warning ! Protocol Implementation [com.sap.engine.services.webservices.jaxrpc.wsdl2java.features.builtin.MessageIdProtocol] could not be loaded (NoClassDefFoundError) !
    Error Message is :com/sap/guid/GUIDGeneratorFactory
    Warning ! Protocol Implementation [com.sap.engine.services.webservices.jaxrpc.wsdl2java.features.builtin.MessageIdProtocol] could not be loaded (NoClassDefFoundError) !
    Error Message is :com/sap/guid/GUIDGeneratorFactory
    Warning ! Protocol Implementation [com.sap.engine.services.webservices.jaxrpc.wsdl2java.features.builtin.MessageIdProtocol] could not be loaded (NoClassDefFoundError) !
    Error Message is :com/sap/guid/GUIDGeneratorFactory
    Warning ! Protocol Implementation [com.sap.engine.services.webservices.jaxrpc.wsdl2java.features.builtin.MessageIdProtocol] could not be loaded (NoClassDefFoundError) !
    Error Message is :com/sap/guid/GUIDGeneratorFactory
    Warning ! Protocol Implementation [com.sap.engine.services.webservices.jaxrpc.wsdl2java.features.builtin.MessageIdProtocol] could not be loaded (NoClassDefFoundError) !
    Error Message is :com/sap/guid/GUIDGeneratorFactory
    This is error common ?
    Any idea ?
    Weird for me is this line:
    "Failed to connect to the Introscope Enterprise Manager at localhost:6001"
    Because my INtroscope Enterprise Manager name is bnssmpci
    Thanks and Regars,
    Juan.

    SOLVED !!!
    Restart the J2EE Managed System and check the SAP Note - WilyHost agent fails to connect to ABAP stack (bad password

  • Com.sap.aii.adapter.file.ftp.FTPEx: 421

    Hi Guys,
    I am getting these two error messages:
    1) com.sap.aii.adapter.file.ftp.FTPEx: 421 Maximum session time exceeded - closing
    2) com.sap.aii.adapter.file.ftp.FTPEx: 421 Too many users - please try again later
    when XI Sender File Adapter tries to pick the files from the FTP server.
    I have not set any limit to the number of session for the user that I have mantianied in the adapter. (Niether I know it -:) how to set.)
    Any idea or help, how to resove this error.
    Thanks in adavance,
    Namadev

    Hi Namdev,
    Your this error is coming as your FTP server maximum allowed connection is reached. so as the solution I would suggest to change the Connection mode property of your communication channel as Per File Transfer as default property is Permanently which reserves connection forever.
    So other communication channels cannot communicate. Make this changes to all the communication channel you have configured.
    And your problem is solved.
    enjoy....
    Thanks & Regards,
    Gaurav Patwari

Maybe you are looking for

  • Converting PL/SQL report to Chart

    All how do i convert the following report to a chart. declare slimdate varchar(100); begin for c1 in (select DISTINCT(substr(logindate, 1, 13)) Users from tablename ) loop      select count(*) into slimdate from tablename where logindate like ''||c1.

  • Back to my Mac - Use with a NAS?

    The basics - Does Back to my mac support a NAS, specifically a Synology NAS? I own almost every possible Apple device that can be owned, except the Power PC (Slurps!!). Prior to this, it has been a pain to set up my Synology NAS for use on a variety

  • I am using iphone 4s in pakistan. siri doesn't respond to my command

    1.how to use siri in pakistan. siri doesn't respond to my commands at all and shows no answers. even i tried to use it when internet( wi-fi) is on. what to do? 2. to delete any apps. following operations is explained. but my phone dont show the cross

  • How make DateField alway is DD/MM/YYYY ?

    Hi all,      I have used DateField, I want result of date is : DD/MM/YYYY.      Example:           I enter 20/10/2010 ---> show : 20/10/2010  --> ok           I enter 2/10/2010 ---> show : 2/10/2010  --> I want is 02/10/2010 not 2/10/2010.          

  • Showing data in the format enterred (ASP JS Pages)

    Hi All, I'm building an ASP Javascipt website that stores the data in an MS SQL database, where there is a requirement for a large amount of text (like a news story) I'm using a text area field to enter the the data, and a nvarchar field to store the