Re: mdmConfigDir has no properties (in script MDM_Uninstall|ind|ind|ind|ind, line 69579: ???)

Hi Mahesh,

Did you check this note ,it speaks about error during installation .same might be useful for unistall

Please check once

Note 1919170:TypeError: this.output has no properties

Copying content of the note

Symptom

An installation or system copy fails with the following error:

ERROR 2013-09-11 17:12:26.191 [EJSGlobal.cpp:50]
FJS-00003 TypeError: this.output has no properties (in script
NW_Doublestack_CI ind ind ind ind, line 5871: ???)

Theline number (5871) may vary depending on the SAP system release being installed or copied.
Most commonly, this error happens during the step retrieveSchemaUser of a Java or dual-stack system Central Instance installation and may also be logged as follows:

ERROR 2013-09-11 17:12:27.13 [sixxcstepexecute.cpp:901]
FCO-00011 The step retrieveSchemaUser with step key
NW_Doublestack_CI ind ind ind ind 0 0 NW_CI_Instance ind ind ind ind ci
0 NW_CI_Instance_Configure_Java ind ind ind ind javaconfig 0 retrieveSchemaUser
was executed with status ERROR ( Last error reported by the step:
TypeError: this.output has no properties (in script NW_Doublestack_CI ind ind ind ind, line 5871: ???)).

Environment

• SAP System release independent
• Unix based systems
• Database release independent

Reproducing the Issue

1. Run SAPInst to install a SAP System or perform the Target System Installation portion of a System Copy;
2. The step retrieveSchemaUser fails and the following message is logged: TypeError: this.output has no properties.

CauseThe SAPInst temporary directory has insufficient permission settings.
This prevents the installer from accessing the required JAR files for the execution of step retrieveSchemaUser, causing the code dump.

Resolution

1. Restart SAPInst;
2. Immediately after the restart a new SAPInst temporary extract directory is created;
   
   Normally, the path to this directory has the pattern /tmp/sapinst_exe.<n>*, where <n> is a number that will be increased every time a new temporary directory needs to be created due to a SAPInst restart.
   
   The newest one can be recognized by the creation date.
   
   NOTE: It is also possible to determine the location in which temporary directories are being created by opening the sapinst_dev.log file in the installation directory and searching for the string "sapinst_exe." or checking the value of the environment variable "SAPINST_EXE_DIR" on the same log file. If this approach is used, check all the path to the "sapinst_exe." directory to ensure the changes will applied to the newest / current one.
   
   
3. Once the new directory is found, don't stop SAPInst and change the rights of the ../sapinst_exe.*/JARdirectory to 755;
4. Continue the installation.

Regards,

Murali