PI 7.1 Installation Error - Failed to APYSAP: could not run R3INLPGM succes

[former_member189462]

Hi All,

We are in the process of installing PI 7.1 on iSeries V6R1 DB2/400 and the step u201CLoad System Kernel Iu201D is giving an error. The sapinst.log file shows the following error message. Additionally, the sapinst_dev.log shows the same error message an no other detail.

ERROR 2010-01-15 15:20:23.734

MOS-02001 Call of command "APYSIDKRN SID(<SID>) ARCHIVES('/usr/sap/<SID>/SYS/exe/uc/as400_pase_64') CARPATH('/usr/sap/<SID>/SYS/exe/uc/as400_pase_64') CHGENV(NO) MODE(ILE) ASP(1) LOGPATH('/tmp/sapinst_instdir/PI71/INSTALL/SYSTEM/DB4/STD/AS/apysidkrn

_ILE.log')" failed. Exception is "".

As per the error above, the file apysidkrn_ILE.log was checked, and the following message was found at the bottom of it:

>>> ERROR >>>: APYSAP: could not run R3INLPGM successfully

Please, let me know your suggestions

Thanks for all your.

Best regards

Edited by: diego77 on Jan 19, 2010 3:30 PM

[Former Member]

Hola Diego, cómo estás:

Buscando un error de instalación me encontré con este mensaje que reportaste y quería saber si pudiste solucionarlo. Pues creo que estoy en la misma situación. Estamos instalando un PI 7.1 EHP 1 en versión 6.1 de i5 OS, y se nos presentó el mismo error en la carga del Kernel que reportaste. Ojalá me pudieras colaborar con esto, pues la verdad no se como proceder y veo que como a ti se te presentó la misma situación, posiblemente ya hayas resuelto tu problema.

Gracias en lo que me pudieras colaborar.

Feliz tarde,

John Fredy.

[former_member189462]

Hola John,

En principio este error no debería presentarse si estas utilizando el u201CInstallation Master para PI 7.1 EHP 1u201D, de todas maneras, la forma en que solucionamos el problema fue la siguiente:

Mas allá de que la instalación fallaba, el comando que estaba tratando de ejecutar el sapinst, podía completarse sin problemas si lo corríamos manualmente con el usuario de instalación. Luego, para impedir que el sapinst quisiera ejecutar este paso nuevamente, editamos el archivo keydb.xml (que se encuentra en el dir sapinst_dir y que lleva el progreso de la instalación), reemplazando la palabra "ERROR" por "OK" en el paso que estaba dando el error. Si buscas por "ERROR" y seleccionas la opción "Match case" debería solo mostrarte una ocurrencia de la palabra. Luego de lo anterior, volvimos a ejecutar el sapinst y la instalación continuo sin problemas.

Espero que puedas solucionar tu problema.

Saludos

[JanStallkamp]

Hello.

Please ask and answer future questions in this forum in english. Most of the members in this community are not speaking spanish and we would like to allow everyone to participate here. Describing the solution in English will also help others who search for a similar issue to find this thread and learn from it.

Thank you very much,

Jan Stallkamp

[former_member189462]

Jan,

You are right; here is my response in English. My apologies.

The way we solved the issue was as follows:

A-From the installation logs the command the sapinst was trying to execute was identified.

B- Logged in as the installation user the above mentioned command was successfully executed.

C- The keydb.xml file (you'll find it in the sapinst_dir directory) was edited. The step with ERROR was changed to OK.

D- The sapinst was restarted and the installation continued without problems.

Hope this help.

Thanks and regards

[Former Member]

Hello,

please check whether SAPTMP is owned by R3GROUP. R3GROUP must also have all rights for SAPTMP - DTAAUT/RWX) OBJAUT(ALL) und command CHGAUT.

Bst regards,

B. Wolf

[former_member189462]

Hi Bernhard,

Thanks for your quick response.

We've checked the R3GROUP permissions on library SAPTMP and the group has full rights on it. Do you think we should check anything else?

Thanks again.

[Former Member]

Hello,

did you open a ticket at SAP - this seems to become a case for SAP support.

[former_member189462]

Hi,

Please find bellow the job log:

PF1252

40 18/01/10 11:38:25,542118 QWTSCSBJ QSYS 132E CMDMAINQ

To Module . . . . . . : AS4EXECI

From procedure . . . : as4_run_ca

Statement . . . . . . . . . : 60

Message . . . . : Output queue TO0000020E not found in library SAPTMP.

Recovery . : Correct the output queue name or change library name.

CPF1338

40 18/01/10 11:38:25,546183 QWTCCSBJ QSYS 0164 CMDMAINQ

To Module . . . . . . : AS4EXECI

From procedure. . . : as4_run_ca

Statement . . . . . . . . . : 60

Message. . . . : Errors occurred on SBMJOB command.

Cause . . . . . : See the messages previously listed. Correct the errors and then submit the command again.

SAP0899

40 18/01/10 11:38:25,556635 CMDMAINQ SITMP1 *STMT CMDMAINQ

From Module. . . . . . . : O4SAPUCI

From procedure . . . : O4_QMHSNDPM_RAW__FPCcT1PCUciN21T4PUcR11O4_E

0100

Statement . . . . . . . . . : 6

To module . . . . . . : O4SAPUCI

To procedure . . . : O4_QMHSNDPM_RAW__FPCcT1PCUciN21T4PUcR11O4_E

0100

Statement. . . . . . . . . : 6

Message. . . . : Failed to APYSAP: could not run R3INLPGM successfully.

Failed to APYSAP: could not run R3INLPGM successfully. Read the previous messages in the job log, remove the error conditions and retry the operation.

40 18/01/10 11:38:25,598113 CMDMAINQ SITMP1 *STMT CALLCMD

From Module . . . . . . . : O4SAPUCI

From procedure . . . : O4_QMHSNDPM_RAW__FPCcT1PCUciN21T4PUcR11O4_E

Could the missing queue TO0000020E to cause the error described above? If so, how should I fix it?

However, if there is something else I should check or verify besides the logs above, please let me know. If the complete job log is needed, please let me know and I will post it.

Best regards