server 0 not starting up

[Former Member]

hi all,

Server0 process is not starting up....

I have pasted the log of dev_server0

*

[Thr 5552] * LOCATION CPIC (TCP/IP) on local host with Unicode

[Thr 5552] * ERROR no conversation found with id 58619190

[Thr 5552] *

• TIME Thu Jul 23 18:42:59 2009

[Thr 5552] * RELEASE 701

[Thr 5552] * COMPONENT CPIC (TCP/IP) with Unicode

[Thr 5552] * VERSION 3

[Thr 5552] * RC 473

[Thr 5552] * MODULE r3cpic.c

[Thr 5552] * LINE 6124

[Thr 5552] * COUNTER 1

[Thr 5552] *

[Thr 5552] *****************************************************************************

[Thr 5552]

*****************************************************************************

*

[Thr 5552] * LOCATION CPIC (TCP/IP) on local host with Unicode

[Thr 5552] * ERROR illegal parameter value ( function=SAP_CMTIMEOUT2 /

• parameter=conversation_ID / value=58619190 )

[Thr 5552] *

• TIME Thu Jul 23 18:42:59 2009

[Thr 5552] * RELEASE 701

[Thr 5552] * COMPONENT CPIC (TCP/IP) with Unicode

[Thr 5552] * VERSION 3

[Thr 5552] * RC 769

[Thr 5552] * MODULE r3cpic.c

[Thr 5552] * LINE 7340

[Thr 5552] * COUNTER 2

[Thr 5552] *

[Thr 5552] *****************************************************************************

[Thr 4872] JLaunchIExitJava: exit hook is called (rc = -11113)

[Thr 4872] **********************************************************************

• 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 4872] JLaunchCloseProgram: good bye (exitcode = -11113)

[Former Member · Accepted solution]

HI

Check this out may help you

/people/antal.perger/blog/2009/03/19/java-server-startup-problems--11113

Did you change JVM parameters ?

Regards

Uday

[Former Member · Accepted solution]

We did change the data but only after we got the error.Any pointers would be appreciated .

[Former Member]

Please post the logs for Std_Server.out from work directory.

Thanks

Rishi Abrol

[Former Member]

The logs are below,

Looks like i need to change in config tool since i have changed the data source to abap i will have to change in cinfig tool .I hope i am right.

.

-

---

-

---

stdout/stderr redirect

-

---

node name : server0

pid : 6936

system name : MJ1

system nr. : 02

started at : Thu Jul 23 18:42:21 2009

[Thr 6804] MtxInit: 10001 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.01 PatchLevel 56102. is starting...

Loading: LogManager ... 469 ms.

Loading: PoolManager ... 0 ms.

Loading: ApplicationThreadManager ... 2.450: [GC 2.450: [ParNew: 174592K->1676K(261888K), 0.0085427 secs] 174592K->1676K(2009856K), 0.0086156 secs]

1344 ms.

Loading: ThreadManager ... 16 ms.

Loading: IpVerificationManager ... 15 ms.

Loading: ClassLoaderManager ... 0 ms.

Loading: ClusterManager ... 157 ms.

Loading: LockingManager ... 46 ms.

Loading: ConfigurationManager ... 1469 ms.

Loading: LicensingManager ... 16 ms.

Loading: CacheManager ... 125 ms.

Loading: ServiceManager ...

Loading services.:

Service DQE started. (0 ms).

Service memory started. (63 ms).

Service caf_euodi~mnuacc started. (0 ms).

Service userstore started. (125 ms).

Service cross started. (78 ms).

Service caf_eucc~api started. (31 ms).

Service runtimeinfo started. (78 ms).

Service file started. (187 ms).

Service timeout started. (109 ms).

Service jmx_notification started. (62 ms).

Service trex.service started. (172 ms).

Service p4 started. (125 ms).

Service classpath_resolver started. (16 ms).

9.461: [GC 9.461: [ParNew: 176268K->16515K(261888K), 0.0633080 secs] 176268K->16515K(2009856K), 0.0634111 secs]

13.214: [GC 13.214: [ParNew: 191107K->17966K(261888K), 0.0501642 secs] 191107K->17966K(2009856K), 0.0502382 secs]

Service log_configurator started. (8343 ms).

Service locking started. (16 ms).

16.538: [GC 16.538: [ParNew: 192558K->23249K(261888K), 0.0664322 secs] 192558K->23249K(2009856K), 0.0665219 secs]

Service http started. (500 ms).

Service naming started. (515 ms).

Service failover started. (63 ms).

Service appclient started. (94 ms).

Service jmsconnector started. (140 ms).

Service javamail started. (140 ms).

Service ts started. (125 ms).

Service licensing started. (0 ms).

Service connector started. (250 ms).

Service iiop started. (172 ms).

Service webservices started. (407 ms).

29.271: [GC 29.272: [ParNew: 197841K->33300K(261888K), 0.0993034 secs] 197841K->33300K(2009856K), 0.0993886 secs]

32.741: [GC 32.741: [ParNew: 207892K->28013K(261888K), 0.0690951 secs] 207892K->28013K(2009856K), 0.0691677 secs]

Service deploy started. (26703 ms).

Service com.sap.portal.runtime.config.kmreadonly started. (0 ms).

Service MigrationService started. (32 ms).

Service bi_mmrdeployer started. (16 ms).

Service configuration started. (47 ms).

Service dbpool started. (1578 ms).

Service UT started. (0 ms).

Service caf_eugp_mailcf started. (31 ms).

Jul 23, 2009 6:42:59 PM com.sap.security.core.persistence [SAPEngine_System_Thread[impl:5]_99] Fatal: Initialization of ABAP data source (com.sap.security.core.persistence.datasource.imp.R3Persistence) failed: "Password logon no longer possible - too many failed attempts". This message is critical if it appears during the startup of the AS Java.

Jul 23, 2009 6:42:59 PM ...re.server.ume.service.UMEServiceFrame [SAPEngine_System_Thread[impl:5]_99] 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: Password logon no longer possible - too many failed attempts

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:83)

at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:109)

Caused by: com.sap.security.core.persistence.datasource.PersistenceException: Password logon no longer possible - too many failed attempts

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: Password logon no longer possible - too many failed attempts

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:83)

at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:109)

Caused by: com.sap.security.core.persistence.datasource.PersistenceException: Password logon no longer possible - too many failed attempts

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 23, 2009 6:42:59 PM com.sap.engine.core.Framework [SAPEngine_System_Thread[impl:5]_99] Fatal: Critical shutdown was invoked. Reason is: Core service com.sap.security.core.ume.service failed. J2EE Engine cannot be started.

[Former Member]

Fatal: Initialization of ABAP data source (com.sap.security.core.persistence.datasource.imp.R3Persistence) failed: "Password logon no longer possible - too many failed attempts".

Your account seems to be locked. Check users SAPJSF or any other user used for the connectivity via SU01

[Former Member]

HI ,

The issue got resolved by changing the user name from small letters to capital letters in config tool.

[Former Member]

Thr 5552 * ERROR illegal parameter value ( function=SAP_CMTIMEOUT2 /
* parameter=conversation_ID / value=58619190 )

Is it a result of parameter change?

Refer to following note/links.

Note 723909 - Java VM settings for J2EE 6.40/7.0

[https://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/e09e4a5e-8280-2a10-ca98-a59dd47d396d?overridelayout=true]

Check out following thread with similar problem

[;

[Former Member]

We had done a standalone abap to standalone java connectivity .