- SAP Community
- Products and Technology
- Technology
- Technology Q&A
- Java wonu00B4t start
- Subscribe to RSS Feed
- Mark Question as New
- Mark Question as Read
- Bookmark
- Subscribe
- Printer Friendly Page
- Report Inappropriate Content
Java wonu00B4t start
- Subscribe to RSS Feed
- Mark Question as New
- Mark Question as Read
- Bookmark
- Subscribe
- Printer Friendly Page
- Report Inappropriate Content
on 07-22-2009 9:58 AM
Dear all,
the Java on a Solution Manager won´t start. The dispatcher on the mmc is yellow and there is a Warning-Message:
WARNING=> DpEnvCheck: no answer from msg server since 38 secs, but dp_ms_keepalive_timeout(300 secs) not reached.
what does it means?
- SAP Managed Tags:
- SAP Solution Manager
Accepted Solutions (0)
Answers (30)
Answers (30)
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Report Inappropriate Content
I found the Problem.
After I reset the
ume.r3.connection.master.r3name= SID
to
ume.r3.connection.master.r3name=
the Java starts
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Report Inappropriate Content
the sap* user wasn´t deactivated. he´s already active
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Report Inappropriate Content
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Report Inappropriate Content
com.sap.security.core.persistence [SAPEngine_Sys
tem_Thread[impl:5]_71] Fatal: Initialization of ABAP data source (com.sap.securi
ty.core.persistence.datasource.imp.R3Persistence) failed: "'mshost' missing". Th
is message is critical if it appears during the startup of the AS Java.
Jul 23, 2009 12:28:57... ...re.server.ume.service.UMEServiceFrame [SAPEngine_Sys
tem_Thread[impl:5]_71] Fatal:
service com.sap.security.core.ume.service ================= ERROR ============
=====
Core service com.sap.security.core.ume.service failed. J2EE Engine cannot be sta
rted.
com.sap.engine.frame.ServiceException: Start of UME service failed. Check help t
opic "Start of UME Service Failed". Technical details: 'mshost' missing
at com.sap.security.core.server.ume.service.UMEServiceFrame.start(UMESer
viceFrame.java:398)
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Report Inappropriate Content
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Report Inappropriate Content
yes, the java_guest was locked, but after unlocking and restart the java engine won´t start.
the message on the screen is:
503 Service Unavailable
7.00
SAP WebAS Engine is starting...
If this state does not change within a few minutes,
please contact your system administrator.
Check the recommendations in SAP Notes: 943498, 764417
Message: Dispatcher running but no server connected!
Details:
No details available
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Report Inappropriate Content
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Report Inappropriate Content
master.ashost = localhost
master.client = 001
master.gwhost =
master.gwserv =
master.r3name = AG5
master.system =
master.sysnr = $$
master.user = SAPJSF
master.passwd = (password of SAPJSF)
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Report Inappropriate Content
Hm,
one other point in the UME config:
ume.login.guesi_user.uniqueids = J2EE_Guest
is this user looked in the ABAP?
if there is no problem with the Gues user, then activate the sap* User.
ume.superadmin.activated = TRUE
ume.superadmin.password = Enter a password for the sap* user
then restart the j2ee_engine
and you can logon with the sap* user and your password
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Report Inappropriate Content
the entries are inside
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Report Inappropriate Content
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Report Inappropriate Content
and what i must do with the services?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Report Inappropriate Content
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Report Inappropriate Content
it is a unix system
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Report Inappropriate Content
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Report Inappropriate Content
i only can find msghost and not mshost.
where can i find it?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Report Inappropriate Content
do you use load balancing?
you have defined:
master.ashost
master.client
master.group
master.msghost
master.r3name
master.system
master.sysnr
master.user
master.passwd?
if you don't use load balancing you need
master.ashost
master.client
master.gwhost
master.gwserv
master.r3name
master.system
master.sysnr
master.user
master.passwd
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Report Inappropriate Content
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Report Inappropriate Content
do you need more? because the file is long!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Report Inappropriate Content
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Report Inappropriate Content
at com.sap.engine.core.service630.container.ServiceRunner.startApplicati
onServiceFrame(ServiceRunner.java:214)
at com.sap.engine.core.service630.container.ServiceRunner.run(ServiceRun
ner.java:144)
at com.sap.engine.frame.core.thread.Task.run(Task.java:64)
at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.ja
va:81)
at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:1
52)
Caused by: com.sap.security.core.persistence.datasource.PersistenceException: 'm
shost' missing
at com.sap.security.core.persistence.datasource.imp.R3PersistenceBase.ne
wPersistenceException(R3PersistenceBase.java:236)
at com.sap.security.core.persistence.datasource.imp.R3PersistenceBase.in
it(R3PersistenceBase.java:491)
at com.sap.security.core.persistence.imp.PrincipalDatabagFactoryInstance
.<init>(PrincipalDatabagFactoryInstance.java:446)
at com.sap.security.core.persistence.imp.PrincipalDatabagFactory.newInst
ance(PrincipalDatabagFactory.java:164)
at com.sap.security.core.persistence.imp.PrincipalDatabagFactory.getInst
ance(PrincipalDatabagFactory.java:117)
at com.sap.security.core.persistence.imp.PrincipalDatabagFactory.getInst
ance(PrincipalDatabagFactory.java:63)
at com.sap.security.core.InternalUMFactory.initializeUME(InternalUMFacto
ry.java:221)
at com.sap.security.core.server.ume.service.UMEServiceFrame.start(UMESer
viceFrame.java:287)
... 6 more
[Framework -> criticalShutdown] Core service com.sap.security.core.ume.service f
ailed. J2EE Engine cannot be started.
Jul 22, 2009 6:47:18 AM com.sap.engine.core.Framework [SAPEngine_Sys
tem_Thread[impl:5]_62] Fatal: Critical shutdown was invoked. Reason is: Core ser
vice com.sap.security.core.ume.service failed. J2EE Engine cannot be started.
-
stdout/stderr redirect
-
node name : server0
pid : 22359
system name : AG5
system nr. : 00
started at : Wed Jul 22 06:47:21 2009
[Thr 1] Wed Jul 22 06:47:23 2009
[Thr 1] MtxInit: -2 0 0
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Report Inappropriate Content
Service failover started. (11 ms).
Service ts started. (61 ms).
Service licensing started. (6 ms).
Service deploy started. (4881 ms).
Service javamail started. (126 ms).
Service appclient started. (86 ms).
Service MigrationService started. (91 ms).
Service jmsconnector started. (262 ms).
Service bimmrdeployer started. (8 ms).
Service connector started. (334 ms).
Service iiop started. (317 ms).
19.623: [GC 19.623: [DefNew: 105381K->22023K(131328K), 0.0894275 secs] 105381K->
22023K(1004800K), 0.0895579 secs]
Service configuration started. (122 ms).
Service webservices started. (791 ms).
Service dbpool started. (1648 ms).
Service UT started. (12 ms).
Jul 22, 2009 6:47:18 AM com.sap.security.core.persistence [SAPEngine_Sys
tem_Thread[impl:5]_62] Fatal: Initialization of ABAP data source (com.sap.securi
ty.core.persistence.datasource.imp.R3Persistence) failed: "'mshost' missing". Th
is message is critical if it appears during the startup of the AS Java.
Jul 22, 2009 6:47:18 AM ...re.server.ume.service.UMEServiceFrame [SAPEngine_Sys
tem_Thread[impl:5]_62] Fatal:
at com.sap.security.core.persistence.datasource.imp.R3PersistenceBase.in
it(R3PersistenceBase.java:491)
at com.sap.security.core.persistence.imp.PrincipalDatabagFactoryInstance
.<init>(PrincipalDatabagFactoryInstance.java:446)
at com.sap.security.core.persistence.imp.PrincipalDatabagFactory.newInst
ance(PrincipalDatabagFactory.java:164)
at com.sap.security.core.persistence.imp.PrincipalDatabagFactory.getInst
ance(PrincipalDatabagFactory.java:117)
at com.sap.security.core.persistence.imp.PrincipalDatabagFactory.getInst
ance(PrincipalDatabagFactory.java:63)
at com.sap.security.core.InternalUMFactory.initializeUME(InternalUMFacto
ry.java:221)
at com.sap.security.core.server.ume.service.UMEServiceFrame.start(UMESer
viceFrame.java:287)
... 6 more
com.sap.engine.frame.ServiceException: Start of UME service failed. Check help t
opic "Start of UME Service Failed". Technical details: 'mshost' missing
at com.sap.security.core.server.ume.service.UMEServiceFrame.start(UMESer
viceFrame.java:398)
at com.sap.engine.frame.ApplicationFrameAdaptor.start(ApplicationFrameAd
aptor.java:31)
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Report Inappropriate Content
system name : AG5
system nr. : 00
started at : Wed Jul 22 06:46:51 2009
[Thr 1] MtxInit: -2 0 0
SAP J2EE Engine Version 7.00 PatchLevel 111772.44 is starting...
Loading: LogManager ... 1107 ms.
Loading: PoolManager ... 2 ms.
Loading: ApplicationThreadManager ... 134 ms.
Loading: ThreadManager ... 25 ms.
Loading: IpVerificationManager ... 52 ms.
Loading: ClassLoaderManager ... 21 ms.
Loading: ClusterManager ... 279 ms.
Loading: LockingManager ... 94 ms.
Loading: ConfigurationManager ... 6548 ms.
Loading: LicensingManager ... 28 ms.
Loading: CacheManager ... 160 ms.
Loading: ServiceManager ...
12.600: [GC 12.600: [DefNew: 87552K->5954K(131328K), 0.0519987 secs] 87552K->595
4K(1004800K), 0.0521194 secs]
Loading services.:
Service memory started. (26 ms).
Service timeout started. (40 ms).
Service runtimeinfo started. (33 ms).
Service cross started. (41 ms).
Service file started. (84 ms).
Service trex.service started. (81 ms).
Service p4 started. (334 ms).
Service classpath_resolver started. (121 ms).
Service userstore started. (26 ms).
Service jmx_notification started. (515 ms).
15.810: [GC 15.811: [DefNew: 93506K->12886K(131328K), 0.0664710 secs] 93506K->12
886K(1004800K), 0.0666228 secs]
16.918: [GC 16.918: [DefNew: 100438K->14253K(131328K), 0.0521681 secs] 100438K->
14253K(1004800K), 0.0522874 secs]
17.824: [GC 17.825: [DefNew: 101805K->16111K(131328K), 0.0566523 secs] 101805K->
16111K(1004800K), 0.0567818 secs]
18.388: [GC 18.388: [DefNew: 103663K->17829K(131328K), 0.0599431 secs] 103663K->
17829K(1004800K), 0.0600713 secs]
Service log_configurator started. (4983 ms).
Service locking started. (2 ms).
Service http started. (236 ms).
Service naming started. (369 ms).
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Report Inappropriate Content
com.sap.engine.frame.ServiceException: Start of UME service failed. Check help t
opic "Start of UME Service Failed". Technical details: 'mshost' missing
at com.sap.security.core.server.ume.service.UMEServiceFrame.start(UMESer
viceFrame.java:398)
at com.sap.engine.frame.ApplicationFrameAdaptor.start(ApplicationFrameAd
aptor.java:31)
at com.sap.engine.core.service630.container.ServiceRunner.startApplicati
onServiceFrame(ServiceRunner.java:214)
at com.sap.engine.core.service630.container.ServiceRunner.run(ServiceRun
ner.java:144)
at com.sap.engine.frame.core.thread.Task.run(Task.java:64)
at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.ja
va:81)
at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:1
07)
Caused by: com.sap.security.core.persistence.datasource.PersistenceException: 'm
shost' missing
at com.sap.security.core.persistence.datasource.imp.R3PersistenceBase.ne
wPersistenceException(R3PersistenceBase.java:236)
at com.sap.security.core.persistence.datasource.imp.R3PersistenceBase.in
it(R3PersistenceBase.java:491)
at com.sap.security.core.persistence.imp.PrincipalDatabagFactoryInstance
.<init>(PrincipalDatabagFactoryInstance.java:446)
at com.sap.security.core.persistence.imp.PrincipalDatabagFactory.newInst
ance(PrincipalDatabagFactory.java:164)
at com.sap.security.core.persistence.imp.PrincipalDatabagFactory.getInst
ance(PrincipalDatabagFactory.java:117)
at com.sap.security.core.persistence.imp.PrincipalDatabagFactory.getInst
ance(PrincipalDatabagFactory.java:63)
at com.sap.security.core.InternalUMFactory.initializeUME(InternalUMFacto
ry.java:221)
at com.sap.security.core.server.ume.service.UMEServiceFrame.start(UMESer
viceFrame.java:287)
... 6 more
[Framework -> criticalShutdown] Core service com.sap.security.core.ume.service f
ailed. J2EE Engine cannot be started.
Jul 22, 2009 6:46:39 AM com.sap.engine.core.Framework [SAPEngine_Sys
tem_Thread[impl:5]_62] Fatal: Critical shutdown was invoked. Reason is: Core ser
vice com.sap.security.core.ume.service failed. J2EE Engine cannot be started.
-
stdout/stderr redirect
-
node name : server0
pid : 22359
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Report Inappropriate Content
Service UT started. (10 ms).
Jul 22, 2009 6:46:39 AM com.sap.security.core.persistence [SAPEngine_Sys
tem_Thread[impl:5]_62] Fatal: Initialization of ABAP data source (com.sap.securi
ty.core.persistence.datasource.imp.R3Persistence) failed: "'mshost' missing". Th
is message is critical if it appears during the startup of the AS Java.
Jul 22, 2009 6:46:39 AM ...re.server.ume.service.UMEServiceFrame [SAPEngine_Sys
tem_Thread[impl:5]_62] Fatal:
service com.sap.security.core.ume.service ================= ERROR ============
=====
Core service com.sap.security.core.ume.service failed. J2EE Engine cannot be sta
rted.
com.sap.engine.frame.ServiceException: Start of UME service failed. Check help t
opic "Start of UME Service Failed". Technical details: 'mshost' missing
at com.sap.security.core.server.ume.service.UMEServiceFrame.start(UMESer
viceFrame.java:398)
at com.sap.engine.frame.ApplicationFrameAdaptor.start(ApplicationFrameAd
aptor.java:31)
at com.sap.engine.core.service630.container.ServiceRunner.startApplicati
onServiceFrame(ServiceRunner.java:214)
at com.sap.engine.core.service630.container.ServiceRunner.run(ServiceRun
ner.java:144)
at com.sap.engine.frame.core.thread.Task.run(Task.java:64)
at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.ja
va:81)
at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:1
07)
Caused by: com.sap.security.core.persistence.datasource.PersistenceException: 'm
shost' missing
at com.sap.security.core.persistence.datasource.imp.R3PersistenceBase.ne
wPersistenceException(R3PersistenceBase.java:236)
at com.sap.security.core.persistence.datasource.imp.R3PersistenceBase.in
it(R3PersistenceBase.java:491)
at com.sap.security.core.persistence.imp.PrincipalDatabagFactoryInstance
.<init>(PrincipalDatabagFactoryInstance.java:446)
at com.sap.security.core.persistence.imp.PrincipalDatabagFactory.newInst
ance(PrincipalDatabagFactory.java:164)
at com.sap.security.core.persistence.imp.PrincipalDatabagFactory.getInst
ance(PrincipalDatabagFactory.java:117)
at com.sap.security.core.persistence.imp.PrincipalDatabagFactory.getInst
ance(PrincipalDatabagFactory.java:63)
at com.sap.security.core.InternalUMFactory.initializeUME(InternalUMFacto
ry.java:221)
at com.sap.security.core.server.ume.service.UMEServiceFrame.start(UMESer
viceFrame.java:287)
... 6 more
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Report Inappropriate Content
Service UT started. (10 ms).
Jul 22, 2009 6:46:39 AM com.sap.security.core.persistence [SAPEngine_Sys
tem_Thread[impl:5]_62] Fatal: Initialization of ABAP data source (com.sap.securi
ty.core.persistence.datasource.imp.R3Persistence) failed: "'mshost' missing". Th
is message is critical if it appears during the startup of the AS Java.
Jul 22, 2009 6:46:39 AM ...re.server.ume.service.UMEServiceFrame [SAPEngine_Sys
tem_Thread[impl:5]_62] Fatal:
service com.sap.security.core.ume.service ================= ERROR ============
=====
Core service com.sap.security.core.ume.service failed. J2EE Engine cannot be sta
rted.
com.sap.engine.frame.ServiceException: Start of UME service failed. Check help t
opic "Start of UME Service Failed". Technical details: 'mshost' missing
at com.sap.security.core.server.ume.service.UMEServiceFrame.start(UMESer
viceFrame.java:398)
at com.sap.engine.frame.ApplicationFrameAdaptor.start(ApplicationFrameAd
aptor.java:31)
at com.sap.engine.core.service630.container.ServiceRunner.startApplicati
onServiceFrame(ServiceRunner.java:214)
at com.sap.engine.core.service630.container.ServiceRunner.run(ServiceRun
ner.java:144)
at com.sap.engine.frame.core.thread.Task.run(Task.java:64)
at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.ja
va:81)
at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:1
07)
Caused by: com.sap.security.core.persistence.datasource.PersistenceException: 'm
shost' missing
at com.sap.security.core.persistence.datasource.imp.R3PersistenceBase.ne
wPersistenceException(R3PersistenceBase.java:236)
at com.sap.security.core.persistence.datasource.imp.R3PersistenceBase.in
it(R3PersistenceBase.java:491)
at com.sap.security.core.persistence.imp.PrincipalDatabagFactoryInstance
.<init>(PrincipalDatabagFactoryInstance.java:446)
at com.sap.security.core.persistence.imp.PrincipalDatabagFactory.newInst
ance(PrincipalDatabagFactory.java:164)
at com.sap.security.core.persistence.imp.PrincipalDatabagFactory.getInst
ance(PrincipalDatabagFactory.java:117)
at com.sap.security.core.persistence.imp.PrincipalDatabagFactory.getInst
ance(PrincipalDatabagFactory.java:63)
at com.sap.security.core.InternalUMFactory.initializeUME(InternalUMFacto
ry.java:221)
at com.sap.security.core.server.ume.service.UMEServiceFrame.start(UMESer
viceFrame.java:287)
... 6 more
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Report Inappropriate Content
stdout/stderr redirect
-
node name : server0
pid : 22359
system name : AG5
system nr. : 00
started at : Wed Jul 22 06:42:56 2009
[Thr 1] Wed Jul 22 06:42:57 2009
[Thr 1] MtxInit: -2 0 0
SAP J2EE Engine Version 7.00 PatchLevel 111772.44 is starting...
Loading: LogManager ... 2449 ms.
Loading: PoolManager ... 4 ms.
Loading: ApplicationThreadManager ... 115 ms.
Loading: ThreadManager ... 21 ms.
Loading: IpVerificationManager ... 21 ms.
Loading: ClassLoaderManager ... 29 ms.
Loading: ClusterManager ... 2987 ms.
Loading: LockingManager ... 9828 ms.
Loading: ConfigurationManager ... 9266 ms.
Loading: LicensingManager ... 31 ms.
Loading: CacheManager ... 265 ms.
Loading: ServiceManager ...
152.907: [GC 152.908: [DefNew: 87552K->5869K(131328K), 0.0540199 secs] 87552K->5
869K(1004800K), 0.0541489 secs]
Loading services.:
Service timeout started. (44 ms).
Service runtimeinfo started. (111 ms).
Service memory started. (50 ms).
Service cross started. (223 ms).
Service file started. (221 ms).
Service trex.service started. (139 ms).
Service p4 started. (467 ms).
Service classpath_resolver started. (87 ms).
158.445: [GC 158.445: [DefNew: 93421K->10771K(131328K), 1.6218330 secs] 93421K->
10771K(1004800K), 1.6219961 secs]
Service userstore started. (9 ms).
Service jmx_notification started. (2013 ms).
176.086: [GC 176.086: [DefNew: 98316K->12813K(131328K), 0.0577301 secs] 98316K->
12813K(1004800K), 0.0578717 secs]
182.673: [GC 182.674: [DefNew: 100365K->16948K(131328K), 1.3435954 secs] 100365K
->16948K(1004800K), 1.3437349 secs]
Service log_configurator started. (30170 ms).
Service locking started. (4 ms).
189.868: [GC 189.868: [DefNew: 104500K->18500K(131328K), 1.9377509 secs] 104500K
->18500K(1004800K), 1.9378935 secs]
Service naming started. (7660 ms).
Service ts started. (102 ms).
Service licensing started. (11 ms).
Service failover started. (274 ms).
Service javamail started. (521 ms).
Service http started. (3228 ms).
Service appclient started. (515 ms).
Service jmsconnector started. (505 ms).
Service connector started. (466 ms).
Service iiop started. (793 ms).
Service webservices started. (1221 ms).
197.475: [GC 197.476: [DefNew: 106052K->21372K(131328K), 1.5219481 secs] 106052K
->21372K(1004800K), 1.5220941 secs]
Service deploy started. (37584 ms).
Service configuration started. (17 ms).
Service MigrationService started. (544 ms).
Service bimmrdeployer started. (7 ms).
Service dbpool started. (6367 ms).
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Report Inappropriate Content
After the changes in configtool it comes now this screen on NWA:
503 Service Unavailable
SAP J2EE Engine/7.00
Cannot process a request for dynamic resources.
Details:
Web Container service is currently unavailable.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Report Inappropriate Content
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Report Inappropriate Content
what should i made in the configtool?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Report Inappropriate Content
User SAPJSF exists and have rights and is not locked
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Report Inappropriate Content
within the configtool please check:
Global server configuration - services - com.sap.security.core.ume.service
and then the Keys:
ume.persistence.data_source_configuration = dataSourceConfiguration_abap.xml
ume.r3.connection.master.ashost = your hostname
ume.r3.connection.master.client = your abap client
ume.r3.connection.master.group = if load balanced
ume.r3.connection.master.gwhost
ume.r3.connection.master.gwserv
ume.r3.connection.master.lang
ume.r3.connection.master.msghost=if load balanced
ume.r3.connection.master.r3name= SID
ume.r3.connection.master.sysnr = sysnr
ume.r3.connection.master.user= SAPJSF
ume.r3.connection.master.passwd=password of sapjsf
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Report Inappropriate Content
Hi
Login to SAP and Check SAPJSF user exists and he is not locked
Regards
Udasy
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Report Inappropriate Content
No, the Problem is, when I want to open the UME or NWA this is in the screen:
503 Service Unavailable
7.00
SAP WebAS Engine is starting...
If this state does not change within a few minutes,
please contact your system administrator.
Check the recommendations in SAP Notes: 943498, 764417
Message: Dispatcher running but no server connected!
Details:
No details available
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Report Inappropriate Content
no, you have to use the offline config tool.
http://help.sap.com/saphelp_nw70/helpdata/de/eb/00954081efb90ee10000000a155106/content.htm
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Report Inappropriate Content
[Framework -> criticalShutdown] Core service com.sap.security.core.ume.service failed. J2EE Engine cannot be started.
Jul 21, 2009 8:31:08 PM com.sap.engine.core.Framework [SAPEngine_System_Thread[impl:5]_77] 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 : 6054
system name : AG5
system nr. : 00
started at : Tue Jul 21 20:31:15 2009
[Thr 1] Tue Jul 21 20:31:16 2009
[Thr 1] MtxInit: -2 0 0
SAP J2EE Engine Version 7.00 PatchLevel 111772.44 is starting...
Loading: LogManager ... 2254 ms.
Loading: PoolManager ... 4 ms.
Loading: ApplicationThreadManager ... 72 ms.
Loading: ThreadManager ... 66 ms.
Loading: IpVerificationManager ... 9 ms.
Loading: ClassLoaderManager ... 15 ms.
Loading: ClusterManager ... 260 ms.
Loading: LockingManager ... 74 ms.
Loading: ConfigurationManager ... 3592 ms.
Loading: LicensingManager ... 27 ms.
Loading: CacheManager ... 165 ms.
Loading: ServiceManager ...
10.484: [GC 10.484: [DefNew: 87552K->6173K(131328K), 0.0517841 secs] 87552K->6173K(1004800K), 0.0519082 secs]
Loading services.:
Service memory started. (82 ms).
Service timeout started. (97 ms).
Service trex.service started. (98 ms).
Service cross started. (114 ms).
Service file started. (116 ms).
Service runtimeinfo started. (113 ms).
Service userstore started. (20 ms).
Service p4 started. (306 ms).
Service classpath_resolver started. (23 ms).
Service jmx_notification started. (504 ms).
13.784: [GC 13.784: [DefNew: 93702K->13395K(131328K), 0.0714825 secs] 93702K->13395K(1004800K), 0.0716364 secs]
15.304: [GC 15.304: [DefNew: 100947K->14972K(131328K), 0.0535901 secs] 100947K->14972K(1004800K), 0.0537184 secs]
16.318: [GC 16.318: [DefNew: 102524K->14104K(131328K), 0.0496373 secs] 102524K->14104K(1004800K), 0.0497890 secs]
17.084: [GC 17.084: [DefNew: 101656K->18391K(131328K), 0.0630568 secs] 101656K->18391K(1004800K), 0.0631841 secs]
Service log_configurator started. (5938 ms).
Service locking started. (16 ms).
Service deploy started. (5629 ms).
Service MigrationService started. (80 ms).
Service bimmrdeployer started. (48 ms).
Service http started. (298 ms).
Service naming started. (460 ms).
Service appclient started. (87 ms).
Service javamail started. (96 ms).
Service ts started. (114 ms).
Service licensing started. (11 ms).
Service failover started. (14 ms).
Service jmsconnector started. (212 ms).
Service iiop started. (198 ms).
Service connector started. (349 ms).
18.582: [GC 18.582: [DefNew: 105943K->21769K(131328K), 0.0886351 secs] 105943K->21769K(1004800K), 0.0887732 secs]
Service configuration started. (20 ms).
Service webservices started. (795 ms).
Service dbpool started. (1559 ms).
Service UT started. (13 ms).
Jul 21, 2009 8:31:40 PM com.sap.security.core.persistence [SAPEngine_System_Thread[impl:5]_65] Fatal: Initialization of ABAP data source (com.sap.sec
urity.core.persistence.datasource.imp.R3Persistence) failed: "Name or password is incorrect (repeat logon)". This message is critical if it appears during th
e startup of the AS Java.
Jul 21, 2009 8:31:40 PM ...re.server.ume.service.UMEServiceFrame [SAPEngine_System_Thread[impl:5]_65] Fatal:
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: Start of UME service failed. Check help topic "Start of UME Service Failed". Technical details: Name or password is in
correct (repeat logon)
at com.sap.security.core.server.ume.service.UMEServiceFrame.start(UMEServiceFrame.java:398)
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:81)
at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:152)
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:236)
at com.sap.security.core.persistence.datasource.imp.R3PersistenceBase.init(R3PersistenceBase.java:491)
at com.sap.security.core.persistence.imp.PrincipalDatabagFactoryInstance.<init>(PrincipalDatabagFactoryInstance.java:446)
at com.sap.security.core.persistence.imp.PrincipalDatabagFactory.newInstance(PrincipalDatabagFactory.java:164)
at com.sap.security.core.persistence.imp.PrincipalDatabagFactory.getInstance(PrincipalDatabagFactory.java:117)
at com.sap.security.core.persistence.imp.PrincipalDatabagFactory.getInstance(PrincipalDatabagFactory.java:63)
at com.sap.security.core.InternalUMFactory.initializeUME(InternalUMFactory.java:221)
at com.sap.security.core.server.ume.service.UMEServiceFrame.start(UMEServiceFrame.java:287)
... 6 more
com.sap.engine.frame.ServiceException: Start of UME service failed. Check help topic "Start of UME Service Failed". Technical details: Name or password is in
correct (repeat logon)
at com.sap.security.core.server.ume.service.UMEServiceFrame.start(UMEServiceFrame.java:398)
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:81)
at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:152)
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:236)
at com.sap.security.core.persistence.datasource.imp.R3PersistenceBase.init(R3PersistenceBase.java:491)
at com.sap.security.core.persistence.imp.PrincipalDatabagFactoryInstance.<init>(PrincipalDatabagFactoryInstance.java:446)
at com.sap.security.core.persistence.imp.PrincipalDatabagFactory.newInstance(PrincipalDatabagFactory.java:164)
at com.sap.security.core.persistence.imp.PrincipalDatabagFactory.getInstance(PrincipalDatabagFactory.java:117)
at com.sap.security.core.persistence.imp.PrincipalDatabagFactory.getInstance(PrincipalDatabagFactory.java:63)
at com.sap.security.core.InternalUMFactory.initializeUME(InternalUMFactory.java:221)
at com.sap.security.core.server.ume.service.UMEServiceFrame.start(UMEServiceFrame.java:287)
... 6 more
[Framework -> criticalShutdown] Core service com.sap.security.core.ume.service failed. J2EE Engine cannot be started.
Jul 21, 2009 8:31:40 PM com.sap.engine.core.Framework [SAPEngine_System_Thread[impl:5]_65] Fatal: Critical shutdown was invoked. Reason is: Core
service com.sap.security.core.ume.service failed. J2EE Engine cannot be started.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Report Inappropriate Content
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Report Inappropriate Content
e startup of the AS Java.
Jul 21, 2009 8:30:26 PM ...re.server.ume.service.UMEServiceFrame [SAPEngine_System_Thread[impl:5]_64] Fatal:
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: Start of UME service failed. Check help topic "Start of UME Service Failed". Technical details: Name or password is in
correct (repeat logon)
at com.sap.security.core.server.ume.service.UMEServiceFrame.start(UMEServiceFrame.java:398)
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:81)
at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:152)
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:236)
at com.sap.security.core.persistence.datasource.imp.R3PersistenceBase.init(R3PersistenceBase.java:491)
at com.sap.security.core.persistence.imp.PrincipalDatabagFactoryInstance.<init>(PrincipalDatabagFactoryInstance.java:446)
at com.sap.security.core.persistence.imp.PrincipalDatabagFactory.newInstance(PrincipalDatabagFactory.java:164)
at com.sap.security.core.persistence.imp.PrincipalDatabagFactory.getInstance(PrincipalDatabagFactory.java:117)
at com.sap.security.core.persistence.imp.PrincipalDatabagFactory.getInstance(PrincipalDatabagFactory.java:63)
at com.sap.security.core.InternalUMFactory.initializeUME(InternalUMFactory.java:221)
at com.sap.security.core.server.ume.service.UMEServiceFrame.start(UMEServiceFrame.java:287)
... 6 more
com.sap.engine.frame.ServiceException: Start of UME service failed. Check help topic "Start of UME Service Failed". Technical details: Name or password is in
correct (repeat logon)
at com.sap.security.core.server.ume.service.UMEServiceFrame.start(UMEServiceFrame.java:398)
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:81)
at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:152)
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:236)
at com.sap.security.core.persistence.datasource.imp.R3PersistenceBase.init(R3PersistenceBase.java:491)
at com.sap.security.core.persistence.imp.PrincipalDatabagFactoryInstance.<init>(PrincipalDatabagFactoryInstance.java:446)
at com.sap.security.core.persistence.imp.PrincipalDatabagFactory.newInstance(PrincipalDatabagFactory.java:164)
at com.sap.security.core.persistence.imp.PrincipalDatabagFactory.getInstance(PrincipalDatabagFactory.java:117)
at com.sap.security.core.persistence.imp.PrincipalDatabagFactory.getInstance(PrincipalDatabagFactory.java:63)
at com.sap.security.core.InternalUMFactory.initializeUME(InternalUMFactory.java:221)
at com.sap.security.core.server.ume.service.UMEServiceFrame.start(UMEServiceFrame.java:287)
... 6 more
[Framework -> criticalShutdown] Core service com.sap.security.core.ume.service failed. J2EE Engine cannot be started.
Jul 21, 2009 8:30:26 PM com.sap.engine.core.Framework [SAPEngine_System_Thread[impl:5]_64] 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 : 6054
system name : AG5
system nr. : 00
started at : Tue Jul 21 20:30:33 2009
[Thr 1] Tue Jul 21 20:30:34 2009
[Thr 1] MtxInit: -2 0 0
SAP J2EE Engine Version 7.00 PatchLevel 111772.44 is starting...
Loading: LogManager ... 673 ms.
Loading: PoolManager ... 3 ms.
Loading: ApplicationThreadManager ... 68 ms.
Loading: ThreadManager ... 64 ms.
Loading: IpVerificationManager ... 9 ms.
Loading: ClassLoaderManager ... 14 ms.
Loading: ClusterManager ... 250 ms.
Loading: LockingManager ... 639 ms.
Loading: ConfigurationManager ... 4161 ms.
Loading: LicensingManager ... 27 ms.
Loading: CacheManager ... 163 ms.
Loading: ServiceManager ...
10.579: [GC 10.579: [DefNew: 87552K->5950K(131328K), 0.0526911 secs] 87552K->5950K(1004800K), 0.0528194 secs]
Loading services.:
Service memory started. (33 ms).
Service runtimeinfo started. (23 ms).
Service cross started. (104 ms).
Service file started. (106 ms).
Service timeout started. (32 ms).
Service trex.service started. (48 ms).
Service userstore started. (6 ms).
Service p4 started. (196 ms).
Service classpath_resolver started. (21 ms).
Service jmx_notification started. (541 ms).
14.026: [GC 14.026: [DefNew: 93502K->13647K(131328K), 0.0715671 secs] 93502K->13647K(1004800K), 0.0717168 secs]
16.274: [GC 16.275: [DefNew: 101199K->14928K(131328K), 0.0602367 secs] 101199K->14928K(1004800K), 0.0603936 secs]
18.774: [GC 18.774: [DefNew: 102480K->14961K(131328K), 0.0515366 secs] 102480K->14961K(1004800K), 0.0516592 secs]
19.669: [GC 19.669: [DefNew: 102513K->19972K(131328K), 0.0697437 secs] 102513K->19972K(1004800K), 0.0698731 secs]
Service deploy started. (7605 ms).
Service MigrationService started. (27 ms).
Service bimmrdeployer started. (5 ms).
Service log_configurator started. (10946 ms).
Service locking started. (2 ms).
Service http started. (1425 ms).
Service naming started. (1736 ms).
Service failover started. (71 ms).
Service ts started. (100 ms).
Service licensing started. (20 ms).
Service appclient started. (166 ms).
Service javamail started. (216 ms).
Service jmsconnector started. (298 ms).
Service connector started. (341 ms).
25.124: [GC 25.124: [DefNew: 107524K->21744K(131328K), 0.0852919 secs] 107524K->21744K(1004800K), 0.0854282 secs]
Service configuration started. (167 ms).
Service iiop started. (497 ms).
Service webservices started. (4253 ms).
Service dbpool started. (5376 ms).
Service UT started. (6 ms).
Jul 21, 2009 8:31:08 PM com.sap.security.core.persistence [SAPEngine_System_Thread[impl:5]_77] Fatal: Initialization of ABAP data source (com.sap.sec
urity.core.persistence.datasource.imp.R3Persistence) failed: "Name or password is incorrect (repeat logon)". This message is critical if it appears during th
e startup of the AS Java.
Jul 21, 2009 8:31:08 PM ...re.server.ume.service.UMEServiceFrame [SAPEngine_System_Thread[impl:5]_77] Fatal:
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: Start of UME service failed. Check help topic "Start of UME Service Failed". Technical details: Name or password is in
correct (repeat logon)
at com.sap.security.core.server.ume.service.UMEServiceFrame.start(UMEServiceFrame.java:398)
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:81)
at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:107)
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:236)
at com.sap.security.core.persistence.datasource.imp.R3PersistenceBase.init(R3PersistenceBase.java:491)
at com.sap.security.core.persistence.imp.PrincipalDatabagFactoryInstance.<init>(PrincipalDatabagFactoryInstance.java:446)
at com.sap.security.core.persistence.imp.PrincipalDatabagFactory.newInstance(PrincipalDatabagFactory.java:164)
at com.sap.security.core.persistence.imp.PrincipalDatabagFactory.getInstance(PrincipalDatabagFactory.java:117)
at com.sap.security.core.persistence.imp.PrincipalDatabagFactory.getInstance(PrincipalDatabagFactory.java:63)
at com.sap.security.core.InternalUMFactory.initializeUME(InternalUMFactory.java:221)
at com.sap.security.core.server.ume.service.UMEServiceFrame.start(UMEServiceFrame.java:287)
... 6 more
com.sap.engine.frame.ServiceException: Start of UME service failed. Check help topic "Start of UME Service Failed". Technical details: Name or password is in
correct (repeat logon)
at com.sap.security.core.server.ume.service.UMEServiceFrame.start(UMEServiceFrame.java:398)
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:81)
at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:107)
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:236)
at com.sap.security.core.persistence.datasource.imp.R3PersistenceBase.init(R3PersistenceBase.java:491)
at com.sap.security.core.persistence.imp.PrincipalDatabagFactoryInstance.<init>(PrincipalDatabagFactoryInstance.java:446)
at com.sap.security.core.persistence.imp.PrincipalDatabagFactory.newInstance(PrincipalDatabagFactory.java:164)
at com.sap.security.core.persistence.imp.PrincipalDatabagFactory.getInstance(PrincipalDatabagFactory.java:117)
at com.sap.security.core.persistence.imp.PrincipalDatabagFactory.getInstance(PrincipalDatabagFactory.java:63)
at com.sap.security.core.InternalUMFactory.initializeUME(InternalUMFactory.java:221)
at com.sap.security.core.server.ume.service.UMEServiceFrame.start(UMEServiceFrame.java:287)
... 6 more
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Report Inappropriate Content
Here´s the std_server0.out:
Loading services.:
Service memory started. (24 ms).
Service cross started. (212 ms).
Service runtimeinfo started. (30 ms).
Service file started. (286 ms).
Service timeout started. (106 ms).
Service trex.service started. (116 ms).
Service userstore started. (6 ms).
Service p4 started. (1209 ms).
Service classpath_resolver started. (88 ms).
Service jmx_notification started. (556 ms).
432.544: [GC 432.544: 93400K->12753K(1004800K), 0.0826483 secs]
441.484: [GC 441.500: 100305K->13782K(1004800K), 0.0538347 secs]
446.563: [GC 446.563: 101334K->17735K(1004800K), 0.0717018 secs]
447.539: [GC 447.539: 105287K->17180K(1004800K), 0.0593639 secs]
Service log_configurator started. (19151 ms).
Service locking started. (8 ms).
Service http started. (472 ms).
Service naming started. (576 ms).
Service ts started. (71 ms).
Service javamail started. (161 ms).
Service licensing started. (9475 ms).
Service failover started. (13689 ms).
Service deploy started. (33630 ms).
Service appclient started. (13853 ms).
Service jmsconnector started. (13878 ms).
463.649: [GC 463.649: 104732K->22422K(1004800K), 0.1078638 secs]
Service iiop started. (13903 ms).
Service connector started. (13937 ms).
Service configuration started. (40 ms).
Service bimmrdeployer started. (6 ms).
Service MigrationService started. (223 ms).
Service webservices started. (14279 ms).
Service dbpool started. (2356 ms).
Service UT started. (7 ms).
Jul 21, 2009 8:29:32 PM com.sap.security.core.persistence [SAPEngine_System_Thread[impl:5]_76] Fatal: Initialization of ABAP data source (com.sap.sec
urity.core.persistence.datasource.imp.R3Persistence) failed: "Name or password is incorrect (repeat logon)". This message is critical if it appears during th
e startup of the AS Java.
Jul 21, 2009 8:29:32 PM ...re.server.ume.service.UMEServiceFrame [SAPEngine_System_Thread[impl:5]_76] Fatal:
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: Start of UME service failed. Check help topic "Start of UME Service Failed". Technical details: Name or password is in
correct (repeat logon)
at com.sap.security.core.server.ume.service.UMEServiceFrame.start(UMEServiceFrame.java:398)
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:81)
at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:107)
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:236)
at com.sap.security.core.persistence.datasource.imp.R3PersistenceBase.init(R3PersistenceBase.java:491)
at com.sap.security.core.persistence.imp.PrincipalDatabagFactoryInstance.(PrincipalDatabagFactoryInstance.java:446)
at com.sap.security.core.persistence.imp.PrincipalDatabagFactory.newInstance(PrincipalDatabagFactory.java:164)
at com.sap.security.core.persistence.imp.PrincipalDatabagFactory.getInstance(PrincipalDatabagFactory.java:117)
at com.sap.security.core.persistence.imp.PrincipalDatabagFactory.getInstance(PrincipalDatabagFactory.java:63)
at com.sap.security.core.InternalUMFactory.initializeUME(InternalUMFactory.java:221)
at com.sap.security.core.server.ume.service.UMEServiceFrame.start(UMEServiceFrame.java:287)
... 6 more
Core service com.sap.security.core.ume.service failed. J2EE Engine cannot be started.
Jul 21, 2009 8:29:32 PM com.sap.engine.core.Framework [SAPEngine_System_Thread[impl:5]_76] 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 : 6054
system name : AG5
system nr. : 00
started at : Tue Jul 21 20:29:42 2009
SAP J2EE Engine Version 7.00 PatchLevel 111772.44 is starting...
Loading: LogManager ... 904 ms.
Loading: PoolManager ... 4 ms.
Loading: ApplicationThreadManager ... 141 ms.
Loading: ThreadManager ... 28 ms.
Loading: IpVerificationManager ... 10 ms.
Loading: ClassLoaderManager ... 15 ms.
Loading: ClusterManager ... 304 ms.
Loading: LockingManager ... 107 ms.
Loading: ConfigurationManager ... 7853 ms.
Loading: LicensingManager ... 29 ms.
Loading: CacheManager ... 185 ms.
Loading: ServiceManager ...
14.894: [GC 14.895: 87552K->5951K(1004800K), 0.0530908 secs]
Loading services.:
Service memory started. (24 ms).
Service runtimeinfo started. (18 ms).
Service timeout started. (405 ms).
Service cross started. (182 ms).
Service file started. (376 ms).
Service trex.service started. (659 ms).
Service userstore started. (5 ms).
Service p4 started. (206 ms).
Service classpath_resolver started. (20 ms).
Service jmx_notification started. (485 ms).
21.310: [GC 21.310: 93503K->14036K(1004800K), 0.0729995 secs]
27.730: [GC 27.730: 101588K->15274K(1004800K), 0.0567741 secs]
31.078: [GC 31.078: 102826K->16305K(1004800K), 0.0572276 secs]
Service deploy started. (14448 ms).
Service MigrationService started. (27 ms).
Service bimmrdeployer started. (6 ms).
32.073: [GC 32.074: 103857K->20519K(1004800K), 0.0719514 secs]
Service log_configurator started. (16270 ms).
Service locking started. (2 ms).
Service http started. (406 ms).
Service naming started. (1813 ms).
Service appclient started. (41 ms).
Service ts started. (161 ms).
Service failover started. (174 ms).
Service jmsconnector started. (140 ms).
Service javamail started. (229 ms).
Service licensing started. (45 ms).
35.531: [GC 35.531: 108071K->22187K(1004800K), 0.0760607 secs]
Service connector started. (701 ms).
Service iiop started. (738 ms).
Service configuration started. (24 ms).
Service webservices started. (1297 ms).
Service dbpool started. (1865 ms).
Service UT started. (10 ms).
Jul 21, 2009 8:30:26 PM com.sap.security.core.persistence [SAPEngine_System_Thread[impl:5]_64] Fatal: Initialization of ABAP data source (com.sap.sec
urity.core.persistence.datasource.imp.R3Persistence) failed: "Name or password is incorrect (repeat logon)". This message is critical if it appears during th
std_server0.out (34%)
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Report Inappropriate Content
Hi,
please post the default trace:
/usr/sap/FBK/DVEBMGS11/j2ee/cluster/server0/log
and the trace files std_server0.out and std_dispatcher.out from
/usr/sap/FBK/DVEBMGS11/work
Kind regards
Timm
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Report Inappropriate Content
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Report Inappropriate Content
heres the dev_server0:
trc file: "/usr/sap/AG5/DVEBMGS00/work/dev_server0", trc level: 1, release: "700"
-
node name : ID6487550
pid : 6150
system name : AG5
system nr. : 00
started at : Tue Jul 21 20:21:38 2009
arguments :
arg[00] : /usr/sap/AG5/DVEBMGS00/exe/jlaunch
arg[01] : pf=/usr/sap/AG5/SYS/profile/AG5_DVEBMGS00_rx26-333
arg[02] : -DSAPINFO=AG5_00_server
arg[03] : pf=/usr/sap/AG5/SYS/profile/AG5_DVEBMGS00_rx26-333
arg[04] : -DSAPSTART=1
arg[05] : -DCONNECT_PORT=65254
arg[06] : -DSAPSYSTEM=00
arg[07] : -DSAPSYSTEMNAME=AG5
arg[08] : -DSAPMYNAME=rx26-333_AG5_00
arg[09] : -DSAPPROFILE=/usr/sap/AG5/SYS/profile/AG5_DVEBMGS00_rx26-333
arg[10] : -DFRFC_FALLBACK=ON
arg[11] : -DFRFC_FALLBACK_HOST=localhost
[Thr 1] Tue Jul 21 20:21:38 2009
[Thr 1] *** WARNING => INFO: Unknown property [instance.box.number=AG5DVEBMGS00rx26-333] [jstartxx_mt. 840]
[Thr 1] *** WARNING => INFO: Unknown property [instance.en.host=rx26-333] [jstartxx_mt. 840]
[Thr 1] *** WARNING => INFO: Unknown property [instance.en.port=3201] [jstartxx_mt. 840]
[Thr 1] *** WARNING => INFO: Unknown property [instance.system.id=0] [jstartxx_mt. 840]
**********************************************************************
JStartupReadInstanceProperties: read instance properties [/usr/sap/AG5/DVEBMGS00/j2ee/cluster/instance.properties]
-> ms host : rx26-333
-> ms port : 3901
-> OS libs : /usr/sap/AG5/DVEBMGS00/j2ee/os_libs
-> Admin URL :
-> run mode : NORMAL
-> run action : NONE
-> enabled : yes
**********************************************************************
*********************************************************************
**********************************************************************
Instance properties
-> ms host : rx26-333
-> ms port : 3901
-> os libs : /usr/sap/AG5/DVEBMGS00/j2ee/os_libs
-> admin URL :
-> run mode : NORMAL
-> run action : NONE
-> enabled : yes
**********************************************************************
**********************************************************************
Bootstrap nodes
-> [00] bootstrap : /usr/sap/AG5/DVEBMGS00/j2ee/cluster/instance.properties
-> [01] bootstrap_ID6487500 : /usr/sap/AG5/DVEBMGS00/j2ee/cluster/instance.properties
-> [02] bootstrap_ID6487550 : /usr/sap/AG5/DVEBMGS00/j2ee/cluster/instance.properties
**********************************************************************
**********************************************************************
Worker nodes
-> [00] ID6487500 : /usr/sap/AG5/DVEBMGS00/j2ee/cluster/instance.properties
-> [01] ID6487550 : /usr/sap/AG5/DVEBMGS00/j2ee/cluster/instance.properties
**********************************************************************
[Thr 1] JLaunchRequestQueueInit: create named pipe for ipc
[Thr 1] JLaunchRequestQueueInit: create pipe listener thread
[Thr 2] JLaunchRequestFunc: Thread 2 started as listener thread for np messages.
[Thr 3] WaitSyncSemThread: Thread 3 started as semaphore monitor thread.
[Thr 1] SigISetDefaultAction : default handling for signal 18
[Thr 1] Tue Jul 21 20:21:41 2009
[Thr 1] NiInit3: NI already initialized; param 'maxHandles' ignored (1;202)
[Thr 1] CPIC (version=700.2006.09.13)
[Thr 1] [Node: server0] java home is set by profile parameter
Java Home: /opt/java1.4
[Thr 1] JStartupICheckFrameworkPackage: can't find framework package /usr/sap/AG5/DVEBMGS00/exe/jvmx.jar
**********************************************************************
JStartupIReadSection: read node properties [ID6487550]
-> node name : server0
-> node type : server
-> node execute : yes
-> jlaunch parameters :
-> java path : /opt/java1.4
-> java parameters : -Djava.security.policy=./java.policy -Djava.security.egd=file:/dev/urandom -Dorg.omg.CORBA.ORBClass=com.sap.engine.system.ORBProxy -D
org.omg.CORBA.ORBSingletonClass=com.sap.engine.system.ORBSingletonProxy -Djavax.rmi.CORBA.PortableRemoteObjectClass=com.sap.engine.system.PortableRemoteObjec
tProxy -Djco.jarm=1 -XX:MaxPermSize=256M -XX:PermSize=256M -XX:NewSize=171M -XX:MaxNewSize=171M -XX:DisableExplicitGC -verbose:gc -XX:PrintGCDetails -XX:+P
rintGCTimeStamps -Djava.awt.headless=true -Dsun.io.useCanonCaches=false -XX:SoftRefLRUPolicyMSPerMB=1 -XX:SurvivorRatio=2 -XX:TargetSurvivorRatio=90 -Dorg.om
g.PortableInterceptor.ORBInitializerClass.com.sap.engine.services.ts.jts.ots.PortableInterceptor.JTSInitializer
-> java vm version : 1.4.2 1.4.2.17-071106-10:49-IA64W IA64W
-> java vm vendor : Java HotSpot(TM) 64-Bit Server VM (Hewlett-Packard Company)
-> java vm type : server
-> java vm cpu : IA64W
-> heap size : 1024M
-> init heap size : 1024M
-> root path : /usr/sap/AG5/DVEBMGS00/j2ee/cluster/server0
-> class path : ./bin/boot/boot.jar:./bin/boot/jaas.jar:./bin/system/bytecode.jar:.
-> OS libs path : /usr/sap/AG5/DVEBMGS00/j2ee/os_libs
-> main class : com.sap.engine.boot.Start
-> framework class : com.sap.bc.proj.jstartup.JStartupFramework
-> registr. class : com.sap.bc.proj.jstartup.JStartupNatives
-> framework path : /usr/sap/AG5/DVEBMGS00/exe/jstartup.jar:/usr/sap/AG5/DVEBMGS00/exe/jvmx.jar
-> shutdown class : com.sap.engine.boot.Start
-> parameters :
-> debuggable : no
-> debug mode : no
-> debug port : 50021
-> shutdown timeout : 120000
**********************************************************************
[Thr 1] JLaunchISetDebugMode: set debug mode [no]
[Thr 4] JLaunchIStartFunc: Thread 4 started as Java VM thread.
**********************************************************************
JHVM_LoadJavaVM: VM Arguments of node [server0]
-> stack : 1048576 Bytes
-> arg[ 0]: exit
-> arg[ 1]: abort
-> arg[ 2]: vfprintf
-> arg[ 3]: -Djava.security.policy=./java.policy
-> arg[ 4]: -Djava.security.egd=file:/dev/urandom
-> arg[ 5]: -Dorg.omg.CORBA.ORBClass=com.sap.engine.system.ORBProxy
-> arg[ 6]: -Dorg.omg.CORBA.ORBSingletonClass=com.sap.engine.system.ORBSingletonProxy
-> arg[ 7]: -Djavax.rmi.CORBA.PortableRemoteObjectClass=com.sap.engine.system.PortableRemoteObjectProxy
-> arg[ 8]: -Djco.jarm=1
-> arg[ 9]: -XX:MaxPermSize=256M
-> arg[ 10]: -XX:PermSize=256M
-> arg[ 11]: -XX:NewSize=171M
-> arg[ 12]: -XX:MaxNewSize=171M
-> arg[ 13]: -XX:+DisableExplicitGC
-> arg[ 14]: -verbose:gc
-> arg[ 15]: -XX:+PrintGCDetails
-> arg[ 16]: -XX:+PrintGCTimeStamps
-> arg[ 17]: -Djava.awt.headless=true
-> arg[ 18]: -Dsun.io.useCanonCaches=false
-> arg[ 19]: -XX:SoftRefLRUPolicyMSPerMB=1
-> arg[ 20]: -XX:SurvivorRatio=2
-> arg[ 21]: -XX:TargetSurvivorRatio=90
-> arg[ 22]: -Dorg.omg.PortableInterceptor.ORBInitializerClass.com.sap.engine.services.ts.jts.ots.PortableInterceptor.JTSInitializer
-> arg[ 23]: -Dsys.global.dir=/usr/sap/AG5/SYS/global
-> arg[ 24]: -Dapplication.home=/usr/sap/AG5/DVEBMGS00/exe
-> arg[ 25]: -Djava.class.path=/usr/sap/AG5/DVEBMGS00/exe/jstartup.jar:/usr/sap/AG5/DVEBMGS00/exe/jvmx.jar:./bin/boot/boot.jar:./bin/boot/jaas.jar:./bin/syst
em/bytecode.jar:.
-> arg[ 26]: -Djava.library.path=/opt/java1.4/jre/lib/IA64W:/opt/java1.4/jre/lib/IA64W/server:/opt/java1.4/jre/../lib/IA64W:/usr/sap/AG5/DVEBMGS00/exe:/usr/s
ap/AG5/DVEBMGS00/exe::/usr/sap/AG5/DVEBMGS00/exe:/usr/sap/AG5/DVEBMGS00/exe:/usr/sap/AG5/DVEBMGS00/exe:/tmp/sapinst_exe.8372.1232308740:/usr/sap/AG5/SYS/exe/
run:/oracle/client/10x_64/instantclient:/usr/lib:/usr/sap/AG5/DVEBMGS00/j2ee/os_libs:/usr/sap/AG5/DVEBMGS00/exe:/usr/sap/AG5/DVEBMGS00/exe:
-> arg[ 27]: -Dmemory.manager=1024M
-> arg[ 28]: -Xmx1024M
-> arg[ 29]: -Xms1024M
-> arg[ 30]: -DLoadBalanceRestricted=no
-> arg[ 31]: -Djstartup.mode=JCONTROL
-> arg[ 32]: -Djstartup.ownProcessId=6150
-> arg[ 33]: -Djstartup.ownHardwareId=J0798058335
-> arg[ 34]: -Djstartup.whoami=server
-> arg[ 35]: -Djstartup.debuggable=no
-> arg[ 36]: -DSAPINFO=AG5_00_server
-> arg[ 37]: -DSAPSTART=1
-> arg[ 38]: -DCONNECT_PORT=65254
-> arg[ 39]: -DSAPSYSTEM=00
-> arg[ 40]: -DSAPSYSTEMNAME=AG5
-> arg[ 41]: -DSAPMYNAME=rx26-333_AG5_00
-> arg[ 42]: -DSAPPROFILE=/usr/sap/AG5/SYS/profile/AG5_DVEBMGS00_rx26-333
-> arg[ 43]: -DFRFC_FALLBACK=ON
-> arg[ 44]: -DFRFC_FALLBACK_HOST=localhost
-> arg[ 45]: -DSAPSTARTUP=1
-> arg[ 46]: -DSAPSYSTEM=00
-> arg[ 47]: -DSAPSYSTEMNAME=AG5
-> arg[ 48]: -DSAPMYNAME=rx26-333_AG5_00
-> arg[ 49]: -DSAPDBHOST=rx26-333
-> arg[ 50]: -Dj2ee.dbhost=rx26-333
**********************************************************************
[Thr 4] Tue Jul 21 20:25:06 2009
[Thr 4] JHVM_LoadJavaVM: Java VM created OK.
**********************************************************************
JHVM_BuildArgumentList: main method arguments of node [server0]
**********************************************************************
[Thr 17] Tue Jul 21 20:27:10 2009
[Thr 17] JHVM_RegisterNatives: registering methods in com.sap.bc.krn.perf.PerfTimes
[Thr 17] Tue Jul 21 20:28:30 2009
[Thr 17] JHVM_RegisterNatives: registering methods in com.sap.bc.proj.jstartup.JStartupFramework
[Thr 17] JLaunchISetClusterId: set cluster id 6487550
[Thr 17] Tue Jul 21 20:28:31 2009
[Thr 17] JLaunchISetState: change state from [Initial (0)] to [Waiting for start (1)]
[Thr 17] JLaunchISetState: change state from [Waiting for start (1)] to [Starting (2)]
Tue Jul 21 20:28:42 2009
420.227
Tue Jul 21 20:28:43 2009
: [GC 421.615: [DefNew
Tue Jul 21 20:28:44 2009
: 87552K->5848K(131328K), 0.9409365 secs] 87552K->5848K(1004800K), 0.9410944 secs]
Tue Jul 21 20:28:54 2009
432.544: [GC 432.544: [DefNew: 93400K->12753K(131328K), 0.0824729 secs] 93400K->12753K(1004800K), 0.0826483 secs]
Tue Jul 21 20:29:03 2009
441.484: [GC 441.500: [DefNew: 100305K->13782K(131328K), 0.0536882 secs] 100305K->13782K(1004800K), 0.0538347 secs]
Tue Jul 21 20:29:08 2009
446.563: [GC 446.563: [DefNew: 101334K->17735K(131328K), 0.0715624 secs] 101334K->17735K(1004800K), 0.0717018 secs]
Tue Jul 21 20:29:09 2009
447.539: [GC 447.539: [DefNew: 105287K->17180K(131328K), 0.0592224 secs] 105287K->17180K(1004800K), 0.0593639 secs]
Tue Jul 21 20:29:25 2009
463.649: [GC 463.649: [DefNew: 104732K->22422K(131328K), 0.1076987 secs] 104732K->22422K(1004800K), 0.1078638 secs]
[Thr 145] Tue Jul 21 20:29:30 2009
[Thr 145] JHVM_RegisterNatives: registering methods in com.sap.mw.rfc.driver.CpicDriver
[Thr 145] Tue Jul 21 20:29:31 2009
[Thr 145] JHVM_RegisterNatives: registering methods in com.sap.i18n.cp.ConverterJNI
[Thr 6] Tue Jul 21 20:29:32 2009
[Thr 6] JLaunchIExitJava: exit hook is called (rc = -11113)
[Thr 6] **********************************************************************
ERROR => The Java VM terminated with a non-zero exit code.
Please see SAP Note 943602 , section 'J2EE Engine exit codes'
for additional information and trouble shooting.
**********************************************************************
[Thr 6] SigISetIgnoreAction : SIG_IGN for signal 18
[Thr 6] JLaunchCloseProgram: good bye (exitcode = -11113)
-
trc file: "/usr/sap/AG5/DVEBMGS00/work/dev_server0", trc level: 1, release: "700"
-
node name : ID6487550
pid : 6445
system name : AG5
system nr. : 00
started at : Tue Jul 21 20:29:43 2009
arguments :
arg[00] : /usr/sap/AG5/DVEBMGS00/exe/jlaunch
arg[01] : pf=/usr/sap/AG5/SYS/profile/AG5_DVEBMGS00_rx26-333
arg[02] : -DSAPINFO=AG5_00_server
arg[03] : pf=/usr/sap/AG5/SYS/profile/AG5_DVEBMGS00_rx26-333
arg[04] : -DSAPSTART=1
arg[05] : -DCONNECT_PORT=65254
arg[06] : -DSAPSYSTEM=00
arg[07] : -DSAPSYSTEMNAME=AG5
arg[08] : -DSAPMYNAME=rx26-333_AG5_00
arg[09] : -DSAPPROFILE=/usr/sap/AG5/SYS/profile/AG5_DVEBMGS00_rx26-333
arg[10] : -DFRFC_FALLBACK=ON
arg[11] : -DFRFC_FALLBACK_HOST=localhost
[Thr 1] Tue Jul 21 20:29:43 2009
[Thr 1] *** WARNING => INFO: Unknown property [instance.box.number=AG5DVEBMGS00rx26-333] [jstartxx_mt. 840]
[Thr 1] *** WARNING => INFO: Unknown property [instance.en.host=rx26-333] [jstartxx_mt. 840]
[Thr 1] *** WARNING => INFO: Unknown property [instance.en.port=3201] [jstartxx_mt. 840]
[Thr 1] *** WARNING => INFO: Unknown property [instance.system.id=0] [jstartxx_mt. 840]
**********************************************************************
JStartupReadInstanceProperties: read instance properties [/usr/sap/AG5/DVEBMGS00/j2ee/cluster/instance.properties]
-> ms host : rx26-333
-> ms port : 3901
do you need all of the server0 ? this file is very long!
Edited by: Damian Reiner on Jul 22, 2009 1:17 PM
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Report Inappropriate Content
Hi
Have you checked the Host file entires,paste server0 log
Regards
Uday
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Report Inappropriate Content
The Abap stack works, fine.
The dev_ms displays some errors, but i don´t know what this mean:
*** ERROR => MsSSend: NiWrite (rc=NIECONN_BROKEN) to C1 (127.0.0.1) [ms
xxserv_mt. 10846]
*** ERROR => MsSRetClientList: MsSSend failed, rc=-1 [msxxserv_mt. 6818
]
*** ERROR => MsSSend: NiWrite (rc=NIECONN_BROKEN) to C1 (127.0.0.1) [ms
xxserv_mt. 10846]
*** ERROR => MsSAnswer: MsSSend failed, rc=-1
*** ERROR => MsSSend: NiWrite (rc=NIECONN_BROKEN) to C2 (127.0.0.1) [ms
xxserv_mt. 10846]
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Report Inappropriate Content
Hi
1:Check you host file settings
2:Is your ABAP stack running fine r u able to login to SAP
3:Check all the oracle services and listner is running fine
If nothing workst check dev_* and server0 and paste the logs here
Regards
Uday
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
- Cloud Integration: Manually Sign / Verify XML payload based on XML Signature Standard in Technology Blogs by SAP
- SAP Cloud Integration: Understanding the XML Digital Signature Standard in Technology Blogs by SAP
- S/4HANA 2023 FPS00 Upgrade in Technology Blogs by Members
- 10+ ways to reshape your SAP landscape with SAP BTP - Blog 3 Interview in Technology Blogs by SAP
- Taking huge heap memory by SAP JCO library in Technology Q&A
| User | Count |
|---|---|
| 91 | |
| 10 | |
| 10 | |
| 9 | |
| 9 | |
| 7 | |
| 6 | |
| 5 | |
| 5 | |
| 4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.