SAP Knowledge Base Article - Preview

1603834 - system/type not correctly set to start J2EE: SAP startup issue

Symptom

  • The SAP Application Server JAVA startup fails because the ABAP dispatcher is not able to trigger the JAVA startup and control framework and the below error is logged in the ABAP dispatcher trace file.
  • This issue is valid only for ADD IN installations (ABAP+JAVA) and the ABAP server should be up and running:

WARNING => DpJ2eeStart: profile parameter 'system/type' not correctly set to start J2EE; use 'J2EE' for Java only and 'DS'  for double stack instance (info=0x303) [dpxxj2ee.c   343] *** ERROR => DpEnvCheckJ2ee: DpJ2eeStart failed [dpxxdisp2.c  1439]


Read more...

Environment

SAP release independent

Product

SAP Composition Environment all versions ; SAP NetWeaver all versions ; SAP Process Integration all versions ; SAP Solution Manager all versions

Keywords

startup, ICM SAPJSF J2EE_GUEST ,SAP Production ERP SRM CRM ERP PPM SEM APO XI PI PORTAL issue UME expired client SU01 logon data valid from valid through configtool cluster_data Propertysheet com.sap.security. core.ume.service destinations  Propertysheet  UMEBackendConnection Connection and Transport , KBA , BC-JAS-SF , Startup Framework , BC-CST-STS , Startup Service , Problem

About this page

This is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP ONE Support launchpad (Login required).

Search for additional results

Visit SAP Support Portal's SAP Notes and KBA Search.