Error during the Installation at Import ABAP phase (R3load.exe)

[Former Member]

Hello,

I´m doing a distributed installation of a SAP SRM 7.0 on a Windows Server 2012 with MS SQL Server 2012. I´m doing the installation of the database instance (on database instance host) but the SWPM stopped with an error during the Import ABAP phase.

I checked the log files in sapinst_instdir.

- sapinst.log:

...

INFO 2014-03-29 13:53:10.497

Copied file 'C:/Program Files/sapinst_instdir/BS2008/SRM700/AS-ABAP/MSS/DISTRIBUTED/DB/statistic.xml' to 'C:/Program Files/sapinst_instdir/BS2008/SRM700/AS-ABAP/MSS/DISTRIBUTED/DB/statistic.1.xml'.

WARNING 2014-03-29 13:53:15.177

Unable to get information about path \\LABEL.ASC\ using GetVolumeInformation. Operating system error message: The specified path is invalid.

INFO 2014-03-29 13:53:15.582

Copied file 'C:/Program Files/sapinst_instdir/BS2008/SRM700/AS-ABAP/MSS/DISTRIBUTED/DB/inifile.xml' to 'C:/Program Files/sapinst_instdir/BS2008/SRM700/AS-ABAP/MSS/DISTRIBUTED/DB/inifile.1.xml'.

INFO 2014-03-29 13:53:16.627

Execute step

Preprocess  of component |NW_ABAP_DB|ind|ind|ind|ind|0|0|NW_First_Steps|ind|ind|ind|ind|firstSteps|0|W2K_ServicePack_Check|ind|ind|ind|ind|W2K_ServicePack_Check|0

INFO 2014-03-29 13:53:38.94

Working directory changed to C:/Program Files/sapinst_instdir/BS2008/SRM700/AS-ABAP/MSS/DISTRIBUTED/DB.

INFO 2014-03-29 13:53:47.1

Execute step testDatabaseConnection of component |NW_ABAP_DB|ind|ind|ind|ind|0|0|NW_CreateDBandLoad|ind|ind|ind|ind|createdbandload|0|NW_ABAP_Import_Dialog|ind|ind|ind|ind|abapload|0|NW_ABAP_Import|ind|ind|ind|ind|0|0

INFO 2014-03-29 13:53:54.411

Switched to user: SAPWINSQLDB\wsqadm.

INFO 2014-03-29 13:53:54.505

Creating file C:\Program Files\sapinst_instdir\BS2008\SRM700\AS-ABAP\MSS\DISTRIBUTED\DB\R3load.exe.log.

INFO 2014-03-29 13:53:54.505

Switched to user: SAPWINSQLDB\wsqadm.

INFO 2014-03-29 13:53:54.691

Output of \\sapwinsqlci\sapmnt\WSQ\SYS\exe\uc\NTAMD64\R3load.exe -testconnect is written to the logfile R3load.exe.log.

WARNING 2014-03-29 13:53:55.409

Execution of the command "\\sapwinsqlci\sapmnt\WSQ\SYS\exe\uc\NTAMD64\R3load.exe -testconnect" finished with return code 2. Output:

sapparam: sapargv(argc, argv) has not been called!

sapparam(1c): No Profile used.

sapparam: SAPSYSTEMNAME neither in Profile nor in Commandline

\\sapwinsqlci\sapmnt\WSQ\SYS\exe\uc\NTAMD64\R3load.exe: START OF LOG: 20140329135355

\\sapwinsqlci\sapmnt\WSQ\SYS\exe\uc\NTAMD64\R3load.exe: sccsid @(#) $Id: //bas/720_REL/src/R3ld/R3load/R3ldmain.c#3 $ SAP

\\sapwinsqlci\sapmnt\WSQ\SYS\exe\uc\NTAMD64\R3load.exe: version R7.20/V1.4 [UNICODE]

Compiled May  7 2010 03:20:08

\\sapwinsqlci\sapmnt\WSQ\SYS\exe\uc\NTAMD64\R3load.exe -testconnect

(DB) ERROR: db_connect rc = 256

(DB) ERROR: DbSlErrorMsg rc = 99

\\sapwinsqlci\sapmnt\WSQ\SYS\exe\uc\NTAMD64\R3load.exe: job finished with 1 error(s)

\\sapwinsqlci\sapmnt\WSQ\SYS\exe\uc\NTAMD64\R3load.exe: END OF LOG: 20140329135355

ERROR 2014-03-29 13:53:55.409

CJS-30023  Process call '\\sapwinsqlci\sapmnt\WSQ\SYS\exe\uc\NTAMD64\R3load.exe -testconnect' exits with error code 2. For details see log file(s) R3load.exe.log.

ERROR 2014-03-29 13:53:55.472

FCO-00011  The step testDatabaseConnection with step key |NW_ABAP_DB|ind|ind|ind|ind|0|0|NW_CreateDBandLoad|ind|ind|ind|ind|createdbandload|0|NW_ABAP_Import_Dialog|ind|ind|ind|ind|abapload|0|NW_ABAP_Import|ind|ind|ind|ind|0|0|testDatabaseConnection was executed with status ERROR ( Last error reported by the step: Process call '\\sapwinsqlci\sapmnt\WSQ\SYS\exe\uc\NTAMD64\R3load.exe -testconnect' exits with error code 2. For details see log file(s) R3load.exe.log.).

INFO 2014-03-29 13:53:55.752

Creating file C:\Program Files\sapinst_instdir\BS2008\SRM700\AS-ABAP\MSS\DISTRIBUTED\DB\__instana_tmp.xml.

INFO 2014-03-29 13:53:56.564

Removed file C:\Program Files\sapinst_instdir\BS2008\SRM700\AS-ABAP\MSS\DISTRIBUTED\DB\instslana.xml.

INFO 2014-03-29 13:53:56.564

Creating file C:\Program Files\sapinst_instdir\BS2008\SRM700\AS-ABAP\MSS\DISTRIBUTED\DB\instslana.xml.

- R3load.exe.log:

sapparam: sapargv(argc, argv) has not been called!

sapparam(1c): No Profile used.

sapparam: SAPSYSTEMNAME neither in Profile nor in Commandline

\\sapwinsqlci\sapmnt\WSQ\SYS\exe\uc\NTAMD64\R3load.exe: START OF LOG: 20140329135355

\\sapwinsqlci\sapmnt\WSQ\SYS\exe\uc\NTAMD64\R3load.exe: sccsid @(#) $Id: //bas/720_REL/src/R3ld/R3load/R3ldmain.c#3 $ SAP

\\sapwinsqlci\sapmnt\WSQ\SYS\exe\uc\NTAMD64\R3load.exe: version R7.20/V1.4 [UNICODE]

Compiled May  7 2010 03:20:08

\\sapwinsqlci\sapmnt\WSQ\SYS\exe\uc\NTAMD64\R3load.exe -testconnect

(DB) ERROR: db_connect rc = 256

(DB) ERROR: DbSlErrorMsg rc = 99

\\sapwinsqlci\sapmnt\WSQ\SYS\exe\uc\NTAMD64\R3load.exe: job finished with 1 error(s)

\\sapwinsqlci\sapmnt\WSQ\SYS\exe\uc\NTAMD64\R3load.exe: END OF LOG: 20140329135355

Can you help me please?

Regards,

samid raif

[joo_migueldimas · Accepted solution]

Hi samid raif,

I think the problem is the version of kernel that you´re using. You´re using the Kernel 7.20 UC and if you check the PAM (service.sap.com/pam) that version is not supported for the platform (SO and DB - both version 2012) that you are installing for SAP SRM 7.0!

\sapwinsqlci\sapmnt\WSQ\SYS\exe\uc\NTAMD64\R3load.exe: version R7.20/V1.4 [UNICODE

You need to download the kernel version 7.20 EXT UC (extended version). Try to upgrade the SAP Kernel of your CI host/instance and run again the SWPM from the Import abap phase.

Kind regards,

João Dimas

[Former Member · Accepted solution]

Hello João Dimas,

I did what you recommended and now everything is alright .

The solution was to upgrade the SAP Kernel version to 7.20 EXT (extended version) as you recommended on CI instance host.

Thank you very much,

samid raif

[former_member182657]

Hi Samid,

As said by Dimas try to upgrade your current kernel release with kernel version 7.20 EXT UC or higher.This issue relates with kernel compatibility.

Regards,

Gaurav

[former_member182657]

Hi Samid,

Could you please share result for command R3trans -x from <sid>adm user and also share the trans.log file for analysis.It could be an issue with SSFS database connections.

Thanks,

Gaurav