Quantcast
Channel: SCN : All Content - All Communities
Viewing all articles
Browse latest Browse all 3523

Disp+work.exe stopped with Server0 service failure to start -11113 RC

$
0
0


Hi All,

 

Server0 service is not starting with -11113 core service or additional service start fails haltonadditionalservicefailure=true error. Then disp+work.exe stopped after stopping all java services. Please help ASAP. I upgraded solution manager production from 7.01 to 7.1. Then performing post upgrade activities in SOLMAN_SETUP. ABAP and java connection was not fully restored, I increased physical memory to 32GB then tried to restart. All issue started arising. I am able to connect to offline configurator and config tool. Please help ASAP. Attached are the log files.

 

 

 

Thanks,

Kavitha Rajan.

 

--------------------------------------------------------------------------------
stdout/stderr redirect
--------------------------------------------------------------------------------
node name  : server0
pid        : 3596
system name : SM1
system nr.  : 01
started at  : Tue Sep 08 13:39:20 2015

[Thr 4796] MtxInit: 10001 0 2
Java HotSpot(TM) 64-Bit Server VM warning: .hotspot_compiler file is present but has been ignored.  Run with -XX:CompileCommandFile=.hotspot_compiler to load the file.

SAP J2EE Engine Version 7.02 SP 16  PatchLevel 122498. is starting...

Loading: LogManager ... 917 ms.
Loading: PoolManager ... 3 ms.
Loading: ApplicationThreadManager ... 81 ms.
Loading: ThreadManager ... 27 ms.
Loading: IpVerificationManager ... 7 ms.
Loading: ClassLoaderManager ... 13 ms.
Loading: ClusterManager ... 175 ms.
Loading: LockingManager ... 59 ms.
Loading: ConfigurationManager ... 1337 ms.
Loading: LicensingManager ... 70 ms.
Loading: CacheManager ... 64 ms.
Loading: ServiceManager ...

Loading services.:
  Service memory started. (23 ms).
  Service runtimeinfo started. (14 ms).
  Service timeout started. (16 ms).
  Service cross started. (20 ms).
  Service trex.service started. (34 ms).
  Service p4 started. (339 ms).
  Service classpath_resolver started. (32 ms).
9.070: [GC 9.071: [DefNew: 174592K->12548K(261888K), 0.0591748 secs] 174592K->12548K(2009856K), 0.0592624 secs]
  Service jmx_notification started. (15 ms).
  Service userstore started. (12 ms).
11.640: [GC 11.640: [DefNew: 187140K->14518K(261888K), 0.0376171 secs] 187140K->14518K(2009856K), 0.0376894 secs]
  Service log_configurator started. (5129 ms).
  Service locking started. (2 ms).
  Service naming started. (421 ms).
13.688: [GC 13.689: [DefNew: 189110K->18916K(261888K), 0.0465959 secs] 189110K->18916K(2009856K), 0.0466631 secs]
  Service ts started. (89 ms).
  Service javamail started. (201 ms).
  Service appclient started. (63 ms).
  Service jmsconnector started. (83 ms).
  Service licensing started. (75 ms).
  Service failover started. (107 ms).
  Service http started. (344 ms).
  Service connector started. (64 ms).
  Service iiop started. (152 ms).
16.604: [GC 16.605: [DefNew: 193508K->21695K(261888K), 0.0369252 secs] 193508K->21695K(2009856K), 0.0369721 secs]
  Service deploy started. (12930 ms).
  Service MigrationService started. (26 ms).
  Service dbpool started. (1405 ms).
  Service UT started. (6 ms).
  Service tc~lm~nzdm~crrsrv started. (648 ms).
  Service bi~mmr~deployer started. (3 ms).
Sep 8, 2015 1:40:01 PM          com.sap.security.core.persistence [SAPEngine_System_Thread[impl:5]_61] Fatal: Initialization of ABAP data source (com.sap.security.core.persistence.datasource.imp.R3Persistence) failed: "Connect to SAP

gateway failed
Connection parameters: TYPE=A DEST=<Java Rfc client> ASHOST=sapsolman SYSNR=01 PCS=1

LOCATION    CPIC (TCP/IP) on local host SAPSOLMAN with Unicode
ERROR      connection to partner '192.168.200.172:3301' broken
TIME      

Tue Sep 08 13:40:01 2015
RELEASE    721
COMPONENT  NI (network interface)
VERSION    40
RC          -6
MODULE      gwxx.c
LINE        646
DETAIL      NiIRead: P=192.168.200.172:3301; L=192.168.200.172:64839
SYSTEM CALL GwRead
ERRNO    

10054
ERRNO TEXT  WSAECONNRESET: Connection reset by peer
COUNTER    2
". This message is critical if it appears during the startup of the AS Java.
Sep 8, 2015 1:40:01 PM  ...re.server.ume.service.UMEServiceFrame [SAPEngine_System_Thread[impl:5]_61] 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: Connect to SAP

gateway failed
Connection parameters: TYPE=A DEST=<Java Rfc client> ASHOST=sapsolman SYSNR=01 PCS=1

LOCATION    CPIC (TCP/IP) on local host SAPSOLMAN with Unicode
ERROR      connection to partner '192.168.200.172:3301' broken
TIME      

Tue Sep 08 13:40:01 2015
RELEASE    721
COMPONENT  NI (network interface)
VERSION    40
RC          -6
MODULE      gwxx.c
LINE        646
DETAIL      NiIRead: P=192.168.200.172:3301; L=192.168.200.172:64839
SYSTEM CALL GwRead
ERRNO    

10054
ERRNO TEXT  WSAECONNRESET: Connection reset by peer
COUNTER    2

at com.sap.security.core.server.ume.service.UMEServiceFrame.start(UMEServiceFrame.java:407)
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:83)
at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:109)
Caused by: com.sap.security.core.persistence.datasource.PersistenceException: Connect to SAP gateway failed
Connection parameters: TYPE=A DEST=<Java Rfc client> ASHOST=sapsolman SYSNR=01 PCS=1

LOCATION    CPIC (TCP/IP) on local host

SAPSOLMAN with Unicode
ERROR      connection to partner '192.168.200.172:3301' broken
TIME        Tue Sep 08 13:40:01 2015
RELEASE    721
COMPONENT  NI (network interface)
VERSION    40
RC          -6
MODULE      gwxx.c
LINE        646
DETAIL

    NiIRead: P=192.168.200.172:3301; L=192.168.200.172:64839
SYSTEM CALL GwRead
ERRNO      10054
ERRNO TEXT  WSAECONNRESET: Connection reset by peer
COUNTER    2

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:447)
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:288)
... 6 more


com.sap.engine.frame.ServiceException: Start of UME service failed. Check help topic "Start of UME Service Failed". Technical details: Connect to SAP gateway failed
Connection parameters: TYPE=A DEST=<Java Rfc client> ASHOST=sapsolman

SYSNR=01 PCS=1

LOCATION    CPIC (TCP/IP) on local host SAPSOLMAN with Unicode
ERROR      connection to partner '192.168.200.172:3301' broken
TIME        Tue Sep 08 13:40:01 2015
RELEASE    721
COMPONENT  NI (network interface)
VERSION  

40
RC          -6
MODULE      gwxx.c
LINE        646
DETAIL      NiIRead: P=192.168.200.172:3301; L=192.168.200.172:64839
SYSTEM CALL GwRead
ERRNO      10054
ERRNO TEXT  WSAECONNRESET: Connection reset by peer
COUNTER    2

at com.sap.security.core.server.ume.service.UMEServiceFrame.start(UMEServiceFrame.java:407)
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:83)
at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:109)
Caused by: com.sap.security.core.persistence.datasource.PersistenceException: Connect to SAP gateway failed
Connection parameters: TYPE=A DEST=<Java Rfc client> ASHOST=sapsolman SYSNR=01 PCS=1

LOCATION    CPIC (TCP/IP) on local host

SAPSOLMAN with Unicode
ERROR      connection to partner '192.168.200.172:3301' broken
TIME        Tue Sep 08 13:40:01 2015
RELEASE    721
COMPONENT  NI (network interface)
VERSION    40
RC          -6
MODULE      gwxx.c
LINE        646
DETAIL

    NiIRead: P=192.168.200.172:3301; L=192.168.200.172:64839
SYSTEM CALL GwRead
ERRNO      10054
ERRNO TEXT  WSAECONNRESET: Connection reset by peer
COUNTER    2

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:447)
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:288)
... 6 more

[Framework -> criticalShutdown] Core service com.sap.security.core.ume.service failed. J2EE Engine cannot be started.
Sep 8, 2015 1:40:01 PM              com.sap.engine.core.Framework [SAPEngine_System_Thread[impl:5]_61] Fatal: Critical shutdown was invoked. Reason is: Core service com.sap.security.core.ume.service failed. J2EE Engine cannot be started.


Viewing all articles
Browse latest Browse all 3523

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>