When upgrading a Java system from NW 7.0x to NW 7.30 or higher using SUM, the upgrade fails to bring up the additional application server instance, also
known as the dialog instance. The primary application server (also referred to as Central Instance) starts normally.
In the work/dev_jstart log these exceptions will be found:
[Thr 8944] *** WARNING => SfCheckJeeVersion: Cannot find JEE binary directory E:\usr\sap\<SID>\<Instance_Number>\j2ee\cluster\bin.
[Thr 8944] *** WARNING => SfCheckJeeVersion: Cannot find JEE application directory E:\usr\sap\<SID>\<Instance_Number>\j2ee\cluster\apps.
[Thr 8944] *** WARNING => SfCheckJeeVersion: Found JEE Dispatcher directory E:\usr\sap\<SID>\<Instance_Number>\j2ee\cluster\dispatcher.
[Thr 8944] *** WARNING => Is this a 7.0 instance?
ERROR => Node 'bootstrap' failed with exit code 66.
In the work/jvm_bootstrap log this exception will be found:
[Bootstrap module]> Bootstrap must be called through the Startup Framework with the appropriate parameters!!
And it will also be observed that the bin and apps folders are missing from the j2ee/cluster folder.
SAP NetWeaver Application Server for Java
Is this a 7.0 instance; exit code 66; , KBA , BC-JAS-SF , Startup Framework , BC-UPG-TLS-TLJ , Upgrade tools for Java , Problem
About this pageThis 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.