Skip to Content

Archived discussions are read-only. Learn more about SAP Q&A

Solution Manager 7.1 Installation Error

Hi Experts,

I am installating solution manager 7.1 on Windows 2003 + oracle and seeing the below error. Please help on how to fix this issue.

INFO 2013-05-20 05:12:19.968
Creating file C:\Program Files\sapinst_instdir\SOLMAN71SR1\SYSTEM\ORA\CENTRAL\AS\R3load.exe.log.

INFO 2013-05-20 05:12:20.0
Switched to user: solman\srpadm.

INFO 2013-05-20 05:12:20.187
Output of C:\usr\sap\SRP\SYS\exe\uc\NTAMD64\R3load.exe -testconnect is written to the logfile R3load.exe.log.

WARNING 2013-05-20 05:12:24.531
Execution of the command "C:\usr\sap\SRP\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
C:\usr\sap\SRP\SYS\exe\uc\NTAMD64\R3load.exe: START OF LOG: 20130520051220

C:\usr\sap\SRP\SYS\exe\uc\NTAMD64\R3load.exe: sccsid @(#) $Id: //bas/720_REL/src/R3ld/R3load/R3ldmain.c#13 $ SAP
C:\usr\sap\SRP\SYS\exe\uc\NTAMD64\R3load.exe: version R7.20/V1.4 [UNICODE]
Compiled Dec  1 2011 23:35:03
patchinfo (patches.h): (0.113) NewDB R3load better support (note 1564286)
process id 3868
C:\usr\sap\SRP\SYS\exe\uc\NTAMD64\R3load.exe -testconnect

DbSl Trace: CONNECT failed with sql error '12541'

(DB) ERROR: db_connect rc = 256
DbSl Trace: CONNECT failed with sql error '12541'

(DB) ERROR: DbSlErrorMsg rc = 99

C:\usr\sap\SRP\SYS\exe\uc\NTAMD64\R3load.exe: job finished with 1 error(s)
C:\usr\sap\SRP\SYS\exe\uc\NTAMD64\R3load.exe: END OF LOG: 20130520051224

ERROR 2013-05-20 05:12:24.531
CJS-30023  Process call 'C:\usr\sap\SRP\SYS\exe\uc\NTAMD64\R3load.exe -testconnect' exits with error code 2. For details see log file(s) R3load.exe.log.

ERROR 2013-05-20 05:12:24.703
FCO-00011  The step testDatabaseConnection with step key |NW_Onehost|ind|ind|ind|ind|0|0|NW_Onehost_System|ind|ind|ind|ind|onehost|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 'C:\usr\sap\SRP\SYS\exe\uc\NTAMD64\R3load.exe -testconnect' exits with error code 2. For details see log file(s) R3load.exe.log.).

INFO 2013-05-20 05:12:25.234

R3load.exe.log below

sapparam: sapargv(argc, argv) has not been called!
sapparam(1c): No Profile used.
sapparam: SAPSYSTEMNAME neither in Profile nor in Commandline
C:\usr\sap\SRP\SYS\exe\uc\NTAMD64\R3load.exe: START OF LOG: 20130520051220

C:\usr\sap\SRP\SYS\exe\uc\NTAMD64\R3load.exe: sccsid @(#) $Id: //bas/720_REL/src/R3ld/R3load/R3ldmain.c#13 $ SAP
C:\usr\sap\SRP\SYS\exe\uc\NTAMD64\R3load.exe: version R7.20/V1.4 [UNICODE]
Compiled Dec  1 2011 23:35:03
patchinfo (patches.h): (0.113) NewDB R3load better support (note 1564286)
process id 3868
C:\usr\sap\SRP\SYS\exe\uc\NTAMD64\R3load.exe -testconnect

DbSl Trace: CONNECT failed with sql error '12541'

(DB) ERROR: db_connect rc = 256
DbSl Trace: CONNECT failed with sql error '12541'

(DB) ERROR: DbSlErrorMsg rc = 99

C:\usr\sap\SRP\SYS\exe\uc\NTAMD64\R3load.exe: job finished with 1 error(s)
C:\usr\sap\SRP\SYS\exe\uc\NTAMD64\R3load.exe: END OF LOG: 20130520051224

Thanks,

Ranjith

Tags:

Helpful Answer

by
Not what you were looking for? View more on this topic or Ask a question