Unable to Log-in *SAP System Message : Error while reading a Dynpro*

[Former Member]

Hi,

We are facing issues while logging-in through SAP logon 710.

The system throws an error dialog box with the below message:

SAP System Message : Error while reading a Dynpro

At the OS level Java process server0 is in stop status with exit code -11113. In ABAP WP Table all processes are in wait status.

[Former Member]

Please let us know what is the os level and did you check the server processes.

Check that you have enough Space in your file system.

PLease post the log of std_server.out.

Thanks

Rishi Abrol

[Former Member]

Hi Please find the contents of std_server.out below.

-

---

stdout/stderr redirect

-

---

node name : server0

pid : 4124

system name : KEC

system nr. : 01

started at : Mon Jul 27 15:44:57 2009

[Thr 5656] 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 110760.44 is starting...

Loading: LogManager ... 250 ms.

Loading: PoolManager ... 0 ms.

Loading: ApplicationThreadManager ... 47 ms.

Loading: ThreadManager ... 16 ms.

Loading: IpVerificationManager ... 0 ms.

Loading: ClassLoaderManager ... 16 ms.

Loading: ClusterManager ... 93 ms.

Loading: LockingManager ... 32 ms.

Loading: ConfigurationManager ... 1032 ms.

Loading: LicensingManager ... 0 ms.

Loading: CacheManager ... 93 ms.

Loading: ServiceManager ...

Loading services.:

Service runtimeinfo started. (16 ms).

Service cross started. (31 ms).

Service file started. (31 ms).

Service memory started. (31 ms).

Service timeout started. (16 ms).

Service trex.service started. (32 ms).

Service userstore started. (0 ms).

Service jmx_notification started. (15 ms).

Service p4 started. (62 ms).

Service classpath_resolver started. (16 ms).

Service deploy started. (3722 ms).

Service MigrationService started. (31 ms).

Service bi_mmrdeployer started. (0 ms).

Service log_configurator started. (5177 ms).

Service locking started. (0 ms).

Service http started. (126 ms).

Service naming started. (157 ms).

Service failover started. (16 ms).

Service appclient started. (31 ms).

Service javamail started. (47 ms).

Service ts started. (47 ms).

Service jmsconnector started. (47 ms).

Service licensing started. (15 ms).

Service connector started. (93 ms).

Service iiop started. (94 ms).

Service configuration started. (16 ms).

Service webservices started. (265 ms).

Service dbpool started. (1204 ms).

Service UT started. (0 ms).

Jul 27, 2009 3:45:09 PM com.sap.security.core.persistence [SAPEngine_System_Thread[impl:5]_54] Fatal: Initialization of ABAP data source (com.sap.security.core.persistence.datasource.imp.R3Persistence) failed: " Error while reading a dynpro ". This message is critical if it appears during the startup of the AS Java.

Jul 27, 2009 3:45:09 PM ...re.server.ume.service.UMEServiceFrame [SAPEngine_System_Thread[impl:5]_54] 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: Error while reading a dynpro

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: Error while reading a dynpro

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: Error while reading a dynpro

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: Error while reading a dynpro

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

[Former Member]

PLease check the SAPJSF user in client 001(default)

or if you have changed the UME setting then Check that perticular client.

I think JAVA can not Start because the SAPJSF password is locked in the UME Client

Thanks Rishi Abrol

[Former Member]

Thanks for your reply.

But we are not getting the screen to enter the credentials. Only thing we see is this pop-up with the error message.

[Former Member]

Hi,

Please try to create an rfc from one system and try to login in this system.

Please also check the dev_* logs at os level in the work directory. your Java dint Start because i think SapJSF is locked.

Please try to run dpmon at os level and find out.

Thanks

Rsihi Abrol