SAP Knowledge Base Article - Preview

3603386 - There is error as "Caught ESAPinstException in module call" during AAS Installation

Symptom

The installation of the additional application server (AAS) failed into the following error in SWPM, the errors can be found in sapinst_dev.log.

ERROR      (root/sapinst) (startInstallation) [CInstallerCallBackImpl.cpp:260] id=ind-rel.ind-os.ind-db.assertionFailed errno=CJS-00030 CInstallerCallBackImpl::abortInstallation()
Assertion failed: in 
function (guid, force) {
    NW.trace("NWInstance._removeInstance(", guid, ", ", force, ")");
    var where = NWInstance._getWhereFromGuid(guid);
    var table = NWInstance._getTable();
    var rows = table.arraySelect(undefined, where);
    var sid;
    var retval;
    if (rows.length) {
        ..
    NW.trace("NWInstance._removeInstance() done");
    return retval;
}
: status of row {
  sid:XXX
  name:DXX
  number:XX
  host:XXX-XXX-XXXX
  installationStatus:partial
  startProfileName:<sid>_<name>_<host>_<the additional extension>
  instProfilePath:
  dir_profile:
  unicode:undefined
  collectSource:fromUser
} is not installing or partialNoProfile


Read more...

Environment

SAP ABAP systems

Keywords

SWPM, patching, app server installation, ESAPinstException, backup profile,  application server infrastructure, AWS, CJS-00030 , KBA , BC-INS-MIG , OS/DB Migrations with SWPM and DB refresh , Problem

About this page

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

Search for additional results

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