Reconnecting J2EE engine to SAP MMC / NWDS

Hi,
I lost the connection to my local J2EE engine. I believe we accidently changed the password or we are locked out of the engine because of unsuccessful login attempts.
Is there anyway to make the connection back to the SAP MMC and/or to NWDS without having to reinstall the J2EE engine?
Any help you can give is appreciated.

you can use config tool for more info check this link:
Re: NetWeaver portal administrator user account (UME) locked
reward points if possible

Similar Messages

Starting local J2EE engine from SAP MMC

I am trying to start my local J2EE engine using SAP MMC. However, when I select the start option, the DB no longer starts automatically. I can manually start the DB, select start, and the engine will start. Previously, I could select start and everything would just come up.
Can anyone tell me where the disconnect is occuring?

Hi,
If you have an add-in installation then you can try to stop the java system by stopping the java dispacther by stopping the j2ee process.You can just try restarting the java system using SMICM.You can check whether the data base services are set to auto start or need a manual start.
Reward points if helpfull.
Regards,
Vamshi.

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

What J2EE engine for SAP NetWeaver 7.0 (2004s) Trial Version - Full Java Ed

Hi experts,
I am installing SAP NetWeaver 7.0 (2004s) Trial Version - Full Java Edition. For that
1.what J2EE engine sholud be installed?
2.where is it available?
3.give Installation procedure for this.
They have given it as trial version will it expire soon.
Regards,
karthik.

hi karthi,
This Section provides information on how to prepare the standard installation of the SAP System.
The below mentioned steps are to be done before going for a installation.
1.     Check the Resolution of the Screen - Screen resolution to be set to 1024 X 768.
2.     Check for Screen Saver Settings - Screensaver to be set to OFF
3.     Check for Installed OS and Service Pack.
4.     Check for all the Hardware related details Installation of drivers
5.      Check for Data Throughput for Network Adaptors.
Right Click the Local Area Connection -> Select Properties -> Select File & Printer Sharing for Microsoft Networks and click on Properties -> Click radio button for Maximize throughput for Network Connection
go to SAP market place web site u got more information about this
Regards,
P.Manivannan.

How to find the J2EE Engine in SAP BI server

Hi all,
Can anyone explain how to search J2EE Engine installed in SAP BI Server, Where to check to conform that J2EE is installed..
Thnaks in advance

Hi Harish,
Please have a look at the [help file|http://help.sap.com/saphelp_nw70/helpdata/en/43/e35b3315bb2d57e10000000a422035/content.htm] for info on BI Java.
Regards,
Raghu

How to deploy an EAR or WAR into our J2E(J2EE Engine of SAP)

I got a solo WAR but I don't know how to deploy it into our J2EE Engine(J2E). If you have any same or similar experience,can you give me some help?
Any advice is popular. Thanks!

Hello,
If you use 6.20 release of J2EE Engine then have a look at <j2ee root directory>/docs/deploymanual.pdf.
If you have J2EE Engine 6.40 and an already built war file then most probably the easiest way to assemble it and deploy it will be to use the deploy tool (http://help.sap.com/saphelp_nw04/helpdata/en/35/e3ee3da7138e5be10000000a114084/frameset.htm) Usually we use the NetWeaver Developer Studio to build and deploy J2EE Applications (http://help.sap.com/saphelp_nw04/helpdata/en/fe/a3996fa314f94f8a0c3475b08636d0/frameset.htm).
Best Regards
Vyara

J2EE Process table to visible in SAP MMC

Hi All,
Inside my SAP server MMC i am not getting J2EE process table and ICM also. how ever it was available till yesterday. today morning i restart SAP server and it is not found there. However Java process are running in JCMON, SDM is working with NWDS.
Also MMC is set in expert mode.
Please suggest
Regards
Gyan

I am unable to see J2ee Process in SAP MMC.
There is long running job (OCS_Import_queue) is going on from last 40 hours, i have terminated that job, update the statistics of database and restart SAP server, after that it's not showing the J2ee process and even also my dispatcher is not connecting with message server.
Kernel detail are as follows:
disp+work information
OS = Win2003
Datbase = Oracle 10
kernel release                701
kernel make variant           701_REL
patch number                  23
Kindly give me the solution, how to get resolve this issue, as i need to again start the saint import.
Regards
Adil

Stopping only J2EE engine from MMC

Dear Gurus,
I have a ABAP+Java stack 2004s instance. Can you please advice me how I can stop only the J2EE engine from the MMC.
Thanks!
Surya.

The instance '01' is not j2ee. That is actually the SCS01 instance which is the standalone message and enqueue server for the j2ee components. Do not stop the '01' instance while j2ee is running.
In SAPMMC of a 700 dual stack you can only stop/restart the individual elements (SDM, server#, dispatcher) of J2EE. There is no mechanism for a complete restart of j2ee (without stopping R/3). Please keep in mind that if you restart the individual elements in SAPMMC the bootstrap synchronization will not occur (synchronization with with DB). This means that if you make any changes to the J2EE core components the changes will not be realized in the system until a full restart is done.
Here are the ways to stop the j2ee stack independently of R/3:
- JCMON: Use JCMON tool (jcmon pf=<instance profile>) and navigate through the menu to the shutdown option.
- R/3 SMICM: Go to transaction SMICM in the R/3 stack and navigate to Administration-> J2EE Instance (Local)->
Send Soft Shutdown-> Without Restart
- SAPMMC: In sapmmc navigate to '<hostname> 0'-> J2EE Process Table-> Select each of the J2EE nodes by right clicking-> Disable process
Note: The sapmmc option does not stop the jcontrol process (parent process of the j2ee components) and therefore the bootstrap synchronization will not occur when you select "Enable process" to restart.
Regards,
Nathan
Edited by: Nathan Swenson on Jan 24, 2008 3:07 PM

MMC hangs on Windows 2008 and SAP MMC console not coming up

Hi All,
We are running SAP CRM 7. After upgrading Windows 2003 to Windows 2008 R2, SAP is coming up on our J2ee engine. We are able to login to the SAP J2ee application, but SAP MMC hangs. After the reboot, SAP MMC does come up but it hangs while starting the SAP Server Processes. We have to close the MMC from CTRL-ALT-DEL (end process). After that SAP MMC does not come up. Although, we can number number of MMC.EXE running in task manager,but
the SAP MMC window is not displayed.
We have gone through OSS note Note 1326097 - SAP MMC Snap-In crash for certain operations and installed the new version of MMC. But still the error exists. Also, we have installed the VCREDLIST patch and have installed all the DLLs mentioned in OSS SS Note 684106 - Microsoft runtime DLLs.
Also, the event viewer shows the following message
Log Name: Application
Source: Application Hang
Date: 9/9/2011 8:32:30 AM
Event ID: 1002
Task Category: (101)
Level: Error
Keywords: Classic
User: N/A
Computer: sap-xp-q01.com
Description:
The program mmc.exe version 6.1.7600.16385 stopped interacting with
Windows and was closed. To see if more information about the problem is
available, check the problem history in the Action Center control panel. Process ID: fcc
Start Time: 01cc6f03c402c248
Termination Time: 6
Application Path: C:\Windows\system32\mmc.exe
Report Id: e74f009f-daf8-11e0-afd2-000c29701b8a
Also, we have upgraded the SAP Kernel to the latest patch level and installed MMC latest patch.
Please suggest.
Thanks,
Antarpreet

Hello,
Try to re-create (re-register) the SAP Services (SAP instance services) in services.msc list. Then try to put SAP MMC up.
Or, after recreation of sap instance services, try to reconfigure the sap mmc as well -
http://help.sap.com/saphelp_nwpi71/helpdata/en/49/0eb43799b4740ee10000000a421937/content.htm
Thanks

CAF Services not deployed to J2EE engine

HI @all,
I desgined an application service in CAF and deployed it to my CE-systtem.
Developer Studio doesn't display any errors.
I'm using the user Administrator with the roles CAF_Admin and CAF_Developer
But when I use the "test service" functionality I get the following message, when the testing windows in IE is loaded:
German: "Service <<name>> nicht auf J2EE Engine bereitgestellt"
So the service is not on the J2EE engine.
Thus I can't map this service to a destination to use it in Visual Composer.
What's wrong?
Kiing regards and thanks in advice
Manfred Pielmeier

To my understanding the j2ee engine configured to ur NWDS should be the same as from where u r trying to run the "test service". So please do check that.
As far as what error tells is that such a service is not deployed, it means that u should have deployed in a different server. Its just a check that i wnat u to make.
Regards
Ashok

NWDS Webdynpro deploy: Cannot login to the SAP J2EE Engine using ......

Friends,
I am getting the following error while deploying a web dynpro application through NWDS.
Aborted: development component 'WebDynpro_ErrorBehavior'/'local'/'LOKAL'/'0.2007.05.29.17.02.04'/'1':Cannot login to the SAP J2EE Engine using user and password as provided in the Filesystem Secure Store. Enter valid login information in the Filesystem Secure Store using the SAP J2EE Engine Config Tool. For more information, see SAP note 701654.com.sap.sdm.serverext.servertype.inqmy.extern.DeployManagerAuthExceptionWrapper: Wrong security credentials detected while trying to obtain connection to the J2EE Engine. (message ID: com.sap.sdm.serverext.servertype.inqmy.extern.EngineApplOnlineDeployerImpl.checkLoginCredentials.DMAUTHEXC)
I get this error after I supply the SDM password which NWDS asks before deploying.
Can someone guide?
[email protected]
Thanks

In the additonal error log it says-
Unable to compare host[px1db] and host[x900704] Throwable: java.net.UnknownHostException Throwable message: x900704: x900704
where px1db is my portal server and x900704 is my localmachine name.
I dont know why it says so ...In NWDS i have configured only px1db.
any thoughts.
Vinay

SAP J2EE Engine configuration in NWDS 7.1

Hello everybody,
I would like to configure the SAP J2EE engine server (host and port) in NWDS 7.1.
In NWDS 7.0 I used to go in the Preference > SAP J2EE Engine and select "SAP J2EE engine is installed on a remote host" and enter the "Message server host" and "Message server port".
In NWDS 7.1, there is no "SAP J2EE Engine" in the preference and the only place where I found a field for J2EE engine was a local host only one.
How can I do in 7.1 what was able to do in 7.0?
Thanks in advance
François

Hi Fronis,
I feel you just installed NWDS CE 7.1. But there is a lenghty process to achive that. After installation of 7.1 in menu path goto help>software updates>link*(first option)>login to servicemarketplace>there are two options first select 1st after completion next select 2nd it will take long time(bcozz it will download nearly 1.7gb).
try this and let us know....
Regards,
Anil.

Sap J2EE Engine is not visible in NWDS

Hi ,
iam new to Sap iam Builing an Simple Application in Which SAP J2EE engine is not visible under
Window ->Preferences
can any one help me ASAP.

MY Sap J2EE Engine is Install in Remote Host and iam not getting the option Of SapJ2EE
Engine in Window->Prefrences.
iam building an Webdynpro Application In Netweaver.
1) When i Click Deploy NewArchive and Run.
2) Sap J2ee engine login Screen Come i logged in.
3) But after deployment is finish.
Iam getting an Error Saying that:
ERROR:
com.sap.ide.eclipse.deployer.api.APIException: ConnectionException,cause=[ERROR CODE DPL.DCAPI.1144] NamingException.Cannot get initial context.
Reason: Exception during getInitialContext operation. Cannot establish connection to the remote server.
 at com.sap.ide.eclipse.deployer.dc.DCClientImpl.<init>(DCClientImpl.java:70)
 at com.sap.ide.eclipse.deployer.dc.DCClientFactoryImpl.createClient(DCClientFactoryImpl.java:142)
 at com.sap.ide.eclipse.deployer.DeployerPlugin.getClient(DeployerPlugin.java:201)
 at com.sap.ide.eclipse.sdm.threading.DeployThreadManager.deploy(DeployThreadManager.java:359)
 at com.sap.ide.eclipse.sdm.SDMManager.deployArchives(SDMManager.java:149)
 at com.sap.ide.webdynpro.archivebuilder.ActionDeployArchive$DeployJob.run(ActionDeployArchive.java:214)
 at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
can you please help me with is error.

Sap j2ee engine configuration in NWDS

Hi,
I am using Netweaver studio 2.0.15 for developing web dynpro application and using Application server 7.1.
When I try to configure J2EE engine in Netweaver studio, it is giving a message
message saying "No system could be found under
sapmnt."
If i configure as remote host, server was configured but when i try to deploy the application i am getting message " Cannot determine sdm host. Please configure your engine/sdm correctly."
Please any one help me to resolve my problem.
Thanks in advance
Siva

Hi Siva Prasad
This is a reference for for your querry regarding SDM, You can lot of materials and descrptions by searching in this URL
http://help.sap.com/saphelp_nw04/helpdata/en/b8/cd96edb9c8794aa362e6e8b4236a1f/frameset.htm
Software Deployment Manager
The Software Deployment Manager (SDM) is a tool with which you can manage and deploy software packages (Software Deployment Archives (SDAs) and Software Component Archives (SCAs)) that you receive from SAP.
For More Details
http://help.sap.com/saphelp_nw04/helpdata/en/22/a7663bb3808c1fe10000000a114084/frameset.htm
Installing a J2EE Engine
http://help.sap.com/saphelp_nw04/helpdata/en/29/f37941601b040de10000000a1550b0/frameset.htm
Integrating with the SAP J2EE Engine
http://help.sap.com/saphelp_nw04/helpdata/en/42/9ddcc9bb211d72e10000000a1553f6/frameset.htm
Regards
Chandran

Which exe in SAP WAS 6.40 i need to execute to start J2EE engine

Hi
I am working on SAP WAS 6.40 SP9,
I need to start the J2EE not from the mmc (I know how to start the J2EE from MMC))but by invoking exe's.I was able to figure out that I need to invoke
C:\usr\sap\J2E\JC00\j2ee\os_libs\jcontrol.exe
with argument as
pf=C:\usr\sap\J2E\SYS\profile\J2E_JC00_[your_machine]
but when I execute the same on te command prompt the exe runs but when I use IE browser with URL "http://[your_machine]:50000/index.html" I dont get to see the index page
My work involves runing the SAP WAS 6.40 j2ee engine using ANT.I have to use ant tags to start,create deployment descriptors and deploy the ear.
I would be grateful If one can help me out
Thanks in advance
Sai

Hi Vladmir
Thanks for the advice
I saw the trace files and there was folwing exceptions :
#1.5#000FFE10EF3C00010000000000000CE00003F749651E606B#1116319531292#com.sap.engine.core.cluster.impl6.ms.MSRawConnection##com.sap.engine.core.cluster.impl6.ms.MSRawConnection.receiveRawMessage()#######SAP J2EE Engine|MS Socket Listener##0#0#Error##Plain###java.io.IOException: Error reading length field of message. EOF has been reached.#
#1.5#000FFE10EF3C00010000000100000CE00003F749651EB09B#1116319531308#com.sap.engine.core.cluster.impl6.ms.MSRawConnection##com.sap.engine.core.cluster.impl6.ms.MSRawConnection.receiveRawMessage()#######SAP J2EE Engine|MS Socket Listener##0#0#Error##Plain###java.io.IOException: Error reading length field of message. EOF has been reached.
     at com.sap.engine.core.cluster.impl6.ms.MSMessageHeader.read(MSMessageHeader.java:441)
     at com.sap.engine.core.cluster.impl6.ms.MSMessageObjectImpl.readHeader(MSMessageObjectImpl.java:141)
     at com.sap.engine.core.cluster.impl6.ms.MSRawConnection.receiveRawMessage(MSRawConnection.java:1689)
     at com.sap.engine.core.cluster.impl6.ms.MSListener.run(MSListener.java:87)
     at com.sap.engine.frame.core.thread.Task.run(Task.java:60)
     at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:73)
     at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:145)
#1.5#000FFE10EF3C00010000000300000CE00003F749651EB86A#1116319531323#com.sap.engine.core.cluster.impl6.ms.MSListener##com.sap.engine.core.cluster.impl6.ms.MSListener.run()#######SAP J2EE Engine|MS Socket Listener##0#0#Error#1#/System/Server#Java###.#1#MSLib: Exiting the listener loop. Cluster communication is not working anymore. This is due to an interrupted reconnect session. Node will reboot.#
#1.5#000FFE10EF3C00000000000700000CE00003F749651F2D03#1116319531355#com.sap.engine.core.cluster.impl6.ClusterManagerImpl##com.sap.engine.core.cluster.impl6.ClusterManagerImpl.init(java.util.Properties)#######Thread[Thread-1,5,main]##0#0#Fatal#1#/System/Network#Plain###Cannot attach to the Message Server. cluster Id is not unique.#
#1.5#000FFE10EF3C00000000000800000CE00003F749651F2EE8#1116319531355#com.sap.engine.core.cluster.impl6.ClusterManagerImpl##com.sap.engine.core.cluster.impl6.ClusterManagerImpl.init(java.util.Properties)#######Thread[Thread-1,5,main]##0#0#Fatal##Plain###com.sap.engine.frame.cluster.ClusterException: cluster Id is not unique.#
#1.5#000FFE10EF3C00000000000900000CE00003F749651F3066#1116319531355#com.sap.engine.core.cluster.impl6.ClusterManagerImpl##com.sap.engine.core.cluster.impl6.ClusterManagerImpl.init(java.util.Properties)#######Thread[Thread-1,5,main]##0#0#Fatal##Plain###com.sap.engine.frame.cluster.ClusterException: cluster Id is not unique.
     at com.sap.engine.core.cluster.impl6.ms.MSRawConnection.attachToMessageServer(MSRawConnection.java:815)
     at com.sap.engine.core.cluster.impl6.ms.MSConnectionImpl.attachToCluster(MSConnectionImpl.java:73)
     at com.sap.engine.core.cluster.impl6.ClusterManagerImpl.init(ClusterManagerImpl.java:985)
     at com.sap.engine.core.Framework.loadSingleManager(Framework.java:396)
     at com.sap.engine.core.Framework.loadManagers(Framework.java:163)
     at com.sap.engine.core.Framework.start(Framework.java:97)
     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
     at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
     at java.lang.reflect.Method.invoke(Method.java:324)
     at com.sap.engine.boot.FrameThread.run(FrameThread.java:58)
     at java.lang.Thread.run(Thread.java:534)
I saw the http://help.sap.com/ site and there it has been mentioned that :
The following processes must be running for the simplest installation (one dispatcher, one server):
Message Server ( msg_server or msg_server.exe)
Enqueue Server ( enserver or enserver.exe)
Dispatcher and server process (two jlaunch.exe)
Software Deployment Manager (SDM, jlaunch.exe)
Also when I see the developer trace file for jcontrol.exe It actually invokes Jlaunch.exe internally
based on the above stacktrace will you be able to suggest me what might have went wrong
Actually I am trying to find out which all exe file files should be executed in what order so as to start the SAp J2EE engine so that I can deploy some applications on it
Thanks in advance
sai

Reconnecting J2EE engine to SAP MMC / NWDS

Similar Messages

Maybe you are looking for