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

Similar Messages

  • 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.

  • 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

  • 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.

  • 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

  • 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

  • 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

  • Exception when using a renamed com.sap.portal.navigation.toolarea.par file

    Hi,
    I would like to modify the toolarea of our SAP Enterprise Portal. Basically, I just want to move the tools to the right hand side.
    <b>Problem Description</b>
    According to several threads I found on sdn
    - How to modify the header
    - copy and rename par-file?
    it should be fairly simple to modify the tool area.
    - download com.sap.portal.navigation.toolarea.par from portal server
    - import the downloaded par file into your NetWeaver Developer Studio
    - Change the ToolAreaiView.jsp in project folder dist/PORTAL-INF/jsp
    - Save changes
    - Deploy project to the portal server (>File>Export>Par File><Name of your project>>Next>...)
    - Remove the standard Tool Area iView from your Framework page
    - Create a new iView from your uploaded par file (chose default component)
    - Add new created iView to your Framework page
    Done, you should see your customized tool area. Unfortunately I encounter a Portal Runtime Exception (Page could not create the iView). I did exactly as described above.
    - I downloaded the com.sap.portal.navigation.toolarea.par.bak file from >System Administration>Support>Portal Runtime>Browse Deployment>ROOT>WEB-INF/deployment/temp.
    - Extracted the com.sap.portal.navigation.toolarea.par after changing the downloaded files file extension to zip
    - Imported the extracted par file into Netweaver Developer Studio under a new project name
    - Found the ToolAreaiView.jsp in project folder dist/PORTAL-INF/jsp
    - Did NO changes
    - Exported the project into a par file and deployed the par file to the portal successfully.
    - Removed the old Tool Area iView from the Framework page
    - Created a new Tool Area iView from my uploaded par file (default component)
    - Added the new created iView to the Framework page.
    - I logged on again and instead of the Tool Area I see an error message
    <i>Portal Runtime Error
    An exception occurred while processing a request for :
    iView : pcd:portal_content/sdm_Germany/de.sdm.kellermann.folders.home/de.sdm.kellermann.folders.coreobjects/default/frameworkPages/de.sdm.kellermann.coreobjects.frameworkpage/de.sdm.kellermann.iviews.toolarea
    Component Name : null
    Page could not create the iView.
    See the details for the exception ID in the log file</i>
    <b>Background information</b>
    J2EE Engine: 6.40 PatchLevel 89291.313
    Portal: 6.0.11.3.0
    Browser: Microsoft Internet Explorer 6 SP2
    NWDS: 2.0.11
    Any ideas what I did wrong? I appreaciate any kind of help.
    Best regards,
    Martin

    Hi Yoav,
    thank you for your swift response. You were right. I do not know why but after I imported the downloaded par file into NetWeaver Developer Studio, the new created project did not contain the jar files, which come with the par file. I added the jar files manually to the project, put them into the project's build path and instructed the NWDS to put them into the par file which I deployed to the portal server.
    Afterwards I completed the routine described in my first post and everything worked out. Thanks a lot for that hint.
    By the way do you know how to instruct NWDS to include the jar files automatically during an import?
    Best regards,
    Martin

  • 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

  • Com.sap.aii.adapter.jdbc.svc and com.sap.aii.adapter.jms.svc don't start

    Hello,
    In order to configure JMS Receiver Adapter to access Websphere Application Server 7.0, I have recently deployed file com.sap.aii.adapter.lib.sca with the following libraries:
    com.sap.aii.adapter.lib_api.jar
    com.ibm.ws.ejb.thinclient_7.0.0.jar
    com.ibm.ws.orb_7.0.0.jar
    com.ibm.ws.sib.client.thin.jms_7.0.0.jar
    com.ibm.ws.runtime.jar   
    javax.j2ee.jms.jar
    The communication channel can reach the queue but when I send a message it fails because services sap.com/com.sap.aii.adapter.jdbc.svc and com.sap.aii.adapter.jms.svc are not started.
    Checking dev_server0 file I found the following error.
    ==============================================================================================
    Service com.sap.aii.adapter.jdbc.svc start ================= ERROR =================
    com.sap.engine.frame.ServiceException: Could not obtain an initial context due to a communication failure. Since no provider
    URL was specified, the default provider URL of "corbaloc:iiop:1.0(at)sapdpi-lpar:2809/NameService" was used.  Make sure that any
    bootstrap address information in the URL is correct and that the target name server is running.  Possible causes other than
    an incorrect bootstrap address or unavailable name server include the network environment and workstation network configurati
    on.
    at com.sap.aii.adapter.jdbc.SapAdapterServiceFrameImpl.start(SapAdapterServiceFrameImpl.java:151)
    at com.sap.engine.core.service630.container.ServiceRunner.startFrame(ServiceRunner.java:155)
    at com.sap.engine.core.service630.container.ServiceRunner.startService(ServiceRunner.java:113)
    at com.sap.engine.core.service630.container.ServiceRunner.run(ServiceRunner.java:60)
    at com.sap.engine.frame.core.thread.Task.run(Task.java:73)
    at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:162)
    at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:260)
    Caused by: javax.naming.ServiceUnavailableException: Could not obtain an initial context due to a communication failure. Sinc
    e no provider URL was specified, the default provider URL of "corbaloc:iiop:1.0(at)sapdpi-lpar:2809/NameService" was used.  Make
    sure that any bootstrap address information in the URL is correct and that the target name server is running.  Possible caus
    es other than an incorrect bootstrap address or unavailable name server include the network environment and workstation netwo
    rk configuration. [Root exception is org.omg.CORBA.TRANSIENT: java.net.ConnectException: Connection refused:host=sapdpi-lpar,
    port=2809  vmcid: 0x4942f000  minor code: 3586  completed: No]
    at com.ibm.ws.naming.util.WsnInitCtxFactory.mapInitialReferenceFailure(WsnInitCtxFactory.java:2228)
    at com.ibm.ws.naming.util.WsnInitCtxFactory.getWsnNameService(WsnInitCtxFactory.java:1414)
    at com.ibm.ws.naming.util.WsnInitCtxFactory.getRootContextFromServer(WsnInitCtxFactory.java:944)
    at com.ibm.ws.naming.util.WsnInitCtxFactory.getRootJndiContext(WsnInitCtxFactory.java:865)
    at com.ibm.ws.naming.util.WsnInitCtxFactory.getInitialContextInternal(WsnInitCtxFactory.java:545)
    at com.ibm.ws.naming.util.WsnInitCtx.getContext(WsnInitCtx.java:123)
    at com.ibm.ws.naming.util.WsnInitCtx.getContextIfNull(WsnInitCtx.java:798)
    at com.ibm.ws.naming.util.WsnInitCtx.rebind(WsnInitCtx.java:242)
    at com.ibm.ws.naming.util.WsnInitCtx.rebind(WsnInitCtx.java:255)
    at javax.naming.InitialContext.rebind(InitialContext.java:367)
    at javax.naming.InitialContext.rebind(InitialContext.java:367)
    at com.sap.aii.adapter.jdbc.SapAdapterServiceFrameImpl.start(SapAdapterServiceFrameImpl.java:100)
    ... 6 more
    Caused by: org.omg.CORBA.TRANSIENT: java.net.ConnectException: Connection refused:host=sapdpi-lpar,port=2809  vmcid: 0x4942f0
    00  minor code: 3586  completed: No
    at com.ibm.CORBA.transport.TransportConnectionBase.connect(TransportConnectionBase.java:425)
    at com.ibm.ws.orbimpl.transport.WSTransport.getConnection(WSTransport.java:436)
    at com.ibm.CORBA.transport.TransportBase.getConnection(TransportBase.java:187)
    at com.ibm.rmi.iiop.TransportManager.get(TransportManager.java:89)
    at com.ibm.rmi.iiop.GIOPImpl.getConnection(GIOPImpl.java:120)
    at com.ibm.rmi.iiop.GIOPImpl.locate(GIOPImpl.java:209)
    at com.ibm.rmi.corba.Corbaloc.locateUsingINS(Corbaloc.java:307)
    at com.ibm.rmi.corba.Corbaloc.resolve(Corbaloc.java:378)
    at com.ibm.rmi.corba.ORB.objectURLToObject(ORB.java:3721)
    at com.ibm.CORBA.iiop.ORB.objectURLToObject(ORB.java:3256)
    at com.ibm.rmi.corba.ORB.string_to_object(ORB.java:3619)
    at com.ibm.ws.naming.util.WsnInitCtxFactory.stringToObject(WsnInitCtxFactory.java:1524)
    at com.ibm.ws.naming.util.WsnInitCtxFactory.getWsnNameService(WsnInitCtxFactory.java:1389)
    ... 16 more
    Caused by: java.net.ConnectException: Connection refused
    at java.net.PlainSocketImpl.socketConnect(Native Method)
    at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:333)
    at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:195)
    at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:182)
    at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:366)
    at java.net.Socket.connect(Socket.java:522)
    at java.net.Socket.connect(Socket.java:470)
    at java.net.Socket.<init>(Socket.java:367)
    at java.net.Socket.<init>(Socket.java:180)
    at com.ibm.ws.orbimpl.transport.WSTCPTransportConnection.createSocket(WSTCPTransportConnection.java:270)
    at com.ibm.CORBA.transport.TransportConnectionBase.connect(TransportConnectionBase.java:354)
    ... 28 more
    Service com.sap.aii.adapter.jms.svc start ================= ERROR =================
    com.sap.engine.frame.ServiceRuntimeException: Could not obtain an initial context due to a communication failure. Since no pr
    ovider URL was specified, the default provider URL of "corbaloc:iiop:1.0(at)sapdpi-lpar:2809/NameService" was used.  Make sure t
    hat any bootstrap address information in the URL is correct and that the target name server is running.  Possible causes othe
    r than an incorrect bootstrap address or unavailable name server include the network environment and workstation network conf
    iguration.
    at com.sap.aii.adapter.jms.core.service.AdapterServiceFrameImpl.bindAdapter(AdapterServiceFrameImpl.java:171)
    at com.sap.aii.adapter.jms.core.service.AdapterServiceFrameImpl.start(AdapterServiceFrameImpl.java:125)
    at com.sap.engine.core.service630.container.ServiceRunner.startFrame(ServiceRunner.java:155)
    at com.sap.engine.core.service630.container.ServiceRunner.startService(ServiceRunner.java:113)
    at com.sap.engine.core.service630.container.ServiceRunner.run(ServiceRunner.java:60)
    at com.sap.engine.frame.core.thread.Task.run(Task.java:73)
    at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:162)
    at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:260)
    Caused by: javax.naming.ServiceUnavailableException: Could not obtain an initial context due to a communication failure. Sinc
    e no provider URL was specified, the default provider URL of "corbaloc:iiop:1.0(at)sapdpi-lpar:2809/NameService" was used.  Make
    sure that any bootstrap address information in the URL is correct and that the target name server is running.  Possible caus
    es other than an incorrect bootstrap address or unavailable name server include the network environment and workstation netwo
    rk configuration. [Root exception is org.omg.CORBA.TRANSIENT: Connection state: State: ABORT (5)  vmcid: 0x4942f000  minor co
    de: 775  completed: No]
    at com.ibm.ws.naming.util.WsnInitCtxFactory.mapInitialReferenceFailure(WsnInitCtxFactory.java:2228)
    at com.ibm.ws.naming.util.WsnInitCtxFactory.getWsnNameService(WsnInitCtxFactory.java:1414)
    at com.ibm.ws.naming.util.WsnInitCtxFactory.getRootContextFromServer(WsnInitCtxFactory.java:944)
    at com.ibm.ws.naming.util.WsnInitCtxFactory.getRootJndiContext(WsnInitCtxFactory.java:865)
    at com.ibm.ws.naming.util.WsnInitCtxFactory.getInitialContextInternal(WsnInitCtxFactory.java:545)
    at com.ibm.ws.naming.util.WsnInitCtx.getContext(WsnInitCtx.java:123)
    at com.ibm.ws.naming.util.WsnInitCtx.getContextIfNull(WsnInitCtx.java:798)
    at com.ibm.ws.naming.util.WsnInitCtx.rebind(WsnInitCtx.java:242)
    at com.ibm.ws.naming.util.WsnInitCtx.rebind(WsnInitCtx.java:255)
    at javax.naming.InitialContext.rebind(InitialContext.java:367)
    at javax.naming.InitialContext.rebind(InitialContext.java:367)
    at com.sap.aii.adapter.jms.core.service.AdapterServiceFrameImpl.bindAdapter(AdapterServiceFrameImpl.java:163)
    ... 7 more
    Caused by: org.omg.CORBA.TRANSIENT: Connection state: State: ABORT (5)  vmcid: 0x4942f000  minor code: 775  completed: No
    at com.ibm.rmi.iiop.Connection.checkEstablished(Connection.java:3091)
    at com.ibm.rmi.iiop.Connection.send(Connection.java:2145)
    at com.ibm.rmi.iiop.Connection._locate(Connection.java:463)
    at com.ibm.rmi.iiop.Connection.locate(Connection.java:439)
    at com.ibm.rmi.iiop.GIOPImpl.locate(GIOPImpl.java:219)
    at com.ibm.rmi.corba.Corbaloc.locateUsingINS(Corbaloc.java:307)
    at com.ibm.rmi.corba.Corbaloc.resolve(Corbaloc.java:378)
    at com.ibm.rmi.corba.ORB.objectURLToObject(ORB.java:3721)
    at com.ibm.CORBA.iiop.ORB.objectURLToObject(ORB.java:3256)
    at com.ibm.rmi.corba.ORB.string_to_object(ORB.java:3619)
    at com.ibm.ws.naming.util.WsnInitCtxFactory.stringToObject(WsnInitCtxFactory.java:1524)
    at com.ibm.ws.naming.util.WsnInitCtxFactory.getWsnNameService(WsnInitCtxFactory.java:1389)
    ... 17 more
    ==============================================================================================
    Could anyone tell me why is trying to connect to "corbaloc:iiop:1.0(at)sapdpi-lpar:2809/NameService"? Do I have to configure a default provider URL for SAP PI server? If so, where I configure it? Any help will be appreciated.
    Thank you in advance.
    Roger Allué i Vall

    Hi Roger,
    we also experience the same issue and would be very keen to understand how you resolved this problem.
    Many thanks.
    Dieter

  • Java proxy problem:com.sap.aii.proxy.xiruntime cannot be resolved to a type

    hi:
        i am new to Java proxy and new to SAP netweaver developer studio.
        thei PI version is 7.1
        I have generate a java proxy , then create a project in netweaver developer studio and import this java proxy according document "How Tou2026Work with XI 3.0 Java Proxies".
        but i can not find :aii_proxy_xirt.jar  aii_msg_runtime.jar on the PI server, only guidgenerator.jaraii_utilxi_misc.jar could be found. then i could not config the build path.
        in the  SAP netweaver developer studio, the error shows like :com.sap.aii.proxy.xiruntime cannot be resolved to a type
       then how to resolve this problem
       thank you very much

    Hi Cheng,
    I am trying to create a java proxy to send message from WebAS to PI using java proxy.
    I am using NWDS 7.1. Can you please help with step on how to create a java proxy in NWDS 7.1?
    Thanks and best regards,
    Arun prabhu S

  • ERROR:com.sap.tc.webdynpro.services.exceptions.TypeNotFoundException

    Dear All,
    We have taken a par file from another project and deployed in the J2EE engine using SDM.It was succesfully deployed with out any warnings.I have created an iview also.When we are trying to access that i view i am getting an error as follows:
    500   Internal Server Error
    Web Dynpro Container/SAP J2EE Engine/6.40
    Failed to process request. Please contact your system administrator.
    [Hide]
    Error Summary
    While processing the current request, an exception occured which could not be handled by the application or the framework.
    If the information contained on this page doesn't help you to find and correct the cause of the problem, please contact your system administrator. To facilitate analysis of the problem, keep a copy of this error page. Hint: Most browsers allow to select all content, copy it and then paste it into an empty document (e.g. email or simple text file).
    Root Cause
    The initial exception that caused the request to fail, was:
       com.sap.dictionary.runtime.DdException: Type com.bel.holidaycal.model.types.Zhrt029 does not exist
        at com.sap.dictionary.types.mdi.util.ProviderUtil.createAbapTypeXmlMap(ProviderUtil.java:400)
        at com.sap.dictionary.runtime.mdi.DataProvider.createSimpleTypeFromAbapType(DataProvider.java:586)
        at com.sap.dictionary.runtime.mdi.DataProvider.getDataType(DataProvider.java:286)
        at com.sap.dictionary.runtime.DdDictionary.getDataType(DdDictionary.java:95)
        at com.sap.dictionary.runtime.DdBroker.getDataType(DdBroker.java:164)
        ... 51 more
    See full exception chain for details.
    System Environment
    Client
    Web Dynpro Client Type     HTML Client
    User agent     Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; SV1)
    Version     null
    DOM version     null
    Client Type     msie6
    Client Type Profile     ie6
    ActiveX     enabled
    Cookies     enabled
    Frames     enabled
    Java Applets     enabled
    JavaScript     enabled
    Tables     enabled
    VB Script     enabled
    Server
    Web Dynpro Runtime     Vendor: SAP, build ID: 7.0009.20060804145649.0000 (release=645_VAL_REL, buildtime=2006-08-26:14:41:58[UTC], changelist=413534, host=pwdfm101), build date: Mon Mar 03 21:11:10 GMT+05:30 2008
    J2EE Engine     7.00 patchlevel
    Java VM     Java HotSpot(TM) 64-Bit Server VM, version:1.4.2_13-b06, vendor: Sun Microsystems Inc.
    Operating system     Windows 2003, version: 5.2, architecture: ia64
    Session & Other
    Session Locale     en
    Time of Failure     Thu Apr 10 14:31:31 GMT+05:30 2008 (Java Time: 1207818091497)
    Web Dynpro Code Generation Infos
    local/WDHolidayCalendar
    SapDictionaryGenerationCore     7.0009.20060802115015.0000 (release=645_VAL_REL, buildtime=2006-08-26:14:24:21[UTC], changelist=413123, host=PWDFM101.wdf.sap.corp)
    SapDictionaryGenerationTemplates     (unknown)
    SapGenerationFrameworkCore     7.0009.20060719095755.0000 (release=645_VAL_REL, buildtime=2006-08-26:14:12:57[UTC], changelist=411255, host=PWDFM101.wdf.sap.corp)
    SapIdeWebDynproCheckLayer     7.0009.20060802115035.0000 (release=645_VAL_REL, buildtime=2006-08-26:14:30:00[UTC], changelist=413124, host=PWDFM101.wdf.sap.corp)
    SapMetamodelCommon     7.0009.20060210160857.0000 (release=645_VAL_REL, buildtime=2006-08-26:14:13:46[UTC], changelist=388995, host=PWDFM101.wdf.sap.corp)
    SapMetamodelCore     7.0009.20060210160857.0000 (release=645_VAL_REL, buildtime=2006-08-26:14:13:38[UTC], changelist=388995, host=PWDFM101.wdf.sap.corp)
    SapMetamodelDictionary     7.0009.20060719095619.0000 (release=645_VAL_REL, buildtime=2006-08-26:14:21:59[UTC], changelist=411251, host=PWDFM101.wdf.sap.corp)
    SapMetamodelWebDynpro     7.0009.20060428190938.0000 (release=645_VAL_REL, buildtime=2006-08-26:14:26:52[UTC], changelist=400815, host=PWDFM101.wdf.sap.corp)
    SapWebDynproGenerationCTemplates     7.0009.20060804145649.0000 (release=645_VAL_REL, buildtime=2006-08-26:14:45:29[UTC], changelist=413534, host=pwdfm101)
    SapWebDynproGenerationCore     7.0009.20060802115035.0000 (release=645_VAL_REL, buildtime=2006-08-26:14:30:11[UTC], changelist=413124, host=PWDFM101.wdf.sap.corp)
    SapWebDynproGenerationTemplates     7.0009.20060804145649.0000 (release=645_VAL_REL, buildtime=2006-08-26:14:45:29[UTC], changelist=413534, host=pwdfm101)
    sap.com/tcwddispwda
    No information available     null
    sap.com/tcwdcorecomp
    No information available     null
    Detailed Error Information
    Detailed Exception Chain
    com.sap.tc.webdynpro.services.exceptions.TypeNotFoundException: type extern:com.bel.holidaycal.model.types.WDModelHolical:com.bel.holidaycal.model.types.Zhrt029 could not be loaded: com.sap.dictionary.runtime.DdException: Type com.bel.holidaycal.model.types.Zhrt029 does not exist
         at com.sap.tc.webdynpro.services.datatypes.core.DataTypeBroker.getStructure(DataTypeBroker.java:305)
         at com.sap.tc.webdynpro.progmodel.context.DataNodeInfo.doInit(DataNodeInfo.java:234)
         at com.sap.tc.webdynpro.progmodel.context.NodeInfo.init(NodeInfo.java:671)
         at com.sap.tc.webdynpro.progmodel.context.NodeInfo.init(NodeInfo.java:674)
         at com.sap.tc.webdynpro.progmodel.context.NodeInfo.init(NodeInfo.java:674)
         at com.sap.tc.webdynpro.progmodel.context.NodeInfo.init(NodeInfo.java:674)
         at com.sap.tc.webdynpro.progmodel.context.Context.init(Context.java:40)
         at com.sap.tc.webdynpro.progmodel.controller.Controller.init(Controller.java:199)
         at com.sap.tc.webdynpro.progmodel.controller.Component.getCustomControllerInternal(Component.java:448)
         at com.sap.tc.webdynpro.progmodel.controller.Component.getMappableContext(Component.java:386)
         at com.sap.tc.webdynpro.progmodel.controller.Component.getMappableContext(Component.java:415)
         at com.sap.tc.webdynpro.progmodel.context.MappingInfo.getDataNode(MappingInfo.java:79)
         at com.sap.tc.webdynpro.progmodel.context.MappingInfo.initMapping(MappingInfo.java:121)
         at com.sap.tc.webdynpro.progmodel.context.MappingInfo.init(MappingInfo.java:117)
         at com.sap.tc.webdynpro.progmodel.context.MappedNodeInfo.doInit(MappedNodeInfo.java:212)
         at com.sap.tc.webdynpro.progmodel.context.NodeInfo.init(NodeInfo.java:671)
         at com.sap.tc.webdynpro.progmodel.context.NodeInfo.init(NodeInfo.java:674)
         at com.sap.tc.webdynpro.progmodel.context.Context.init(Context.java:40)
         at com.sap.tc.webdynpro.progmodel.controller.Controller.init(Controller.java:199)
         at com.sap.tc.webdynpro.progmodel.view.ViewManager.getView(ViewManager.java:709)
         at com.sap.tc.webdynpro.progmodel.view.ViewManager.bindRoot(ViewManager.java:579)
         at com.sap.tc.webdynpro.progmodel.view.ViewManager.init(ViewManager.java:155)
         at com.sap.tc.webdynpro.clientserver.window.WebDynproWindow.doOpen(WebDynproWindow.java:295)
         at com.sap.tc.webdynpro.clientserver.window.ApplicationWindow.show(ApplicationWindow.java:183)
         at com.sap.tc.webdynpro.clientserver.window.ApplicationWindow.open(ApplicationWindow.java:178)
         at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.init(ClientApplication.java:364)
         at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.initApplication(ApplicationSession.java:700)
         at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:269)
         at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessingStandalone(ClientSession.java:711)
         at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:665)
         at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:232)
         at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:152)
         at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doContent(DispatcherServlet.java:62)
         at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doGet(DispatcherServlet.java:46)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:740)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
         at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:390)
         at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:264)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:347)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:325)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:887)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:241)
         at com.sap.engine.services.httpserver.server.Client.handle(Client.java:92)
         at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:148)
         at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
         at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
         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:100)
         at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
    Caused by: com.sap.dictionary.runtime.DdException: Type com.bel.holidaycal.model.types.Zhrt029 does not exist
         at com.sap.dictionary.types.mdi.util.ProviderUtil.createAbapTypeXmlMap(ProviderUtil.java:400)
         at com.sap.dictionary.runtime.mdi.DataProvider.createSimpleTypeFromAbapType(DataProvider.java:586)
         at com.sap.dictionary.runtime.mdi.DataProvider.getDataType(DataProvider.java:286)
         at com.sap.dictionary.runtime.DdDictionary.getDataType(DdDictionary.java:95)
         at com.sap.dictionary.runtime.DdBroker.getDataType(DdBroker.java:164)
         at com.sap.dictionary.runtime.DdBroker.getStructure(DdBroker.java:180)
         at com.sap.tc.webdynpro.services.datatypes.core.DataTypeBroker.getStructure(DataTypeBroker.java:303)
         ... 49 more
    I have created the JCO connections also ,i am able to test them also.I have imported the same into NWDS and deployed the application , its deploying but the out put is the same error.
    I have cross checked the models and found that the Model is there in the model types.
    Can any one help me regarding this.
    Waiting for the response ASAP.
    Thanks
    Ravi.S

    Hi,
      I think you mean ear file and not par file. Check these threads. The exception is mentioned to be because of JCo problems only.
    Type com.sap.xss.ser.xssmenu.model.types.P_Pernr does not exist
    WDTypeNotFoundException: type model.types.Zbtr_Wbselement could not be load
    WebDynpro using BAPI has an error
    Regards,
    Harini S

  • Error at com.sap.tc.webdynpro.modelimpl.dynamicrfc.DynamicRFCModelClassExec

    hi
    i am getting following , when i am try to execute second bapi. the first babi working fine. i want execute 2 bapi.
    at com.sap.tc.webdynpro.modelimpl.dynamicrfc.DynamicRFCModelClassExecutable.execute(DynamicRFCModelClassExecutable.java.
    all jco are fine. an help plazz
    thanks
    ra

    Is there any possibility of this error when Creating New Models with Single Server and but NOT Working with Load balancing Option.
    The same code worked when connecting to Single Server locally but doesn't work when New models were created  by selection of loadbalancing Option on Remote Server..during development on source from DTR Server(SLD)
    Edited by: Raghu v on Jan 26, 2008 1:22 PM

Maybe you are looking for