ECC6 Install Error at "Import ABAP" step

[Former Member]

Hi,

I am trying to install ECC6 on Windows Server 2008 R2 with MaxDB. The install get to the "Import ABAP" step and then the following windows error popup is shown:

"The program can't start because libSQLDBC76.dll is missing from your computer. Try reinstalling the program to fix this problem."

I have checked and the DLL file referred to is in fact on the server under \sapdb\programs\pgm\

There seems to be a problem with R3load.exe starting.

Here are logs:

R3load.exe.log

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

C:\usr\sap\<sid>\SYS\exe\uc\NTAMD64\R3load.exe: sccsid @(#) $Id: //bas/700_REL/src/R3ld/R3load/R3ldmain.c#14 $ SAP
C:\usr\sap\<sid>\SYS\exe\uc\NTAMD64\R3load.exe: version R7.00/V1.4 [UNICODE]
Compiled Jan 24 2008 01:41:44
C:\usr\sap\<sid>\SYS\exe\uc\NTAMD64\R3load.exe -testconnect 

(DB) ERROR: DbSlControl(DBSL_CMD_IMP_FUNS_SET) rc = 20
(DB) ERROR: DbSlErrorMsg rc = 20

C:\usr\sap\<sid>\SYS\exe\uc\NTAMD64\R3load.exe: job finished with 1 error(s)
C:\usr\sap\<sid>\SYS\exe\uc\NTAMD64\R3load.exe: END OF LOG: 20101129163047

sapinst.log

...

INFO 2010-11-29 16:24:06.571
Execute step testDatabaseConnection of component |NW_Onehost|ind|ind|ind|ind|0|0|NW_Onehost_System|ind|ind|ind|ind|2|0|NW_CreateDBandLoad|ind|ind|ind|ind|10|0|NW_ABAP_Import_Dialog|ind|ind|ind|ind|5|0|NW_ABAP_Import|ind|ind|ind|ind|0|0

WARNING 2010-11-29 16:24:06.727
Error 234 (More data is available.

) in execution of a 'RegEnumValue' function, line (389), with parameter ().

WARNING[E] 2010-11-29 16:24:06.743
MUT-03001  Value of type HKeyClass has illegal value '0'.

INFO 2010-11-29 16:24:07.946
Switched to user: <sid>adm.

INFO 2010-11-29 16:24:07.977
Creating file C:\Program Files\sapinst_instdir\ERP\SYSTEM\ADA\CENTRAL\AS\R3load.exe.log.

INFO 2010-11-29 16:24:07.977
Switched to user: <sid>adm.

INFO 2010-11-29 16:24:08.211
Working directory changed to C:\Program Files\sapinst_instdir\ERP\SYSTEM\ADA\CENTRAL\AS.

INFO 2010-11-29 16:24:08.211
Output of C:\usr\sap\<sid>\SYS\exe\uc\NTAMD64\R3load.exe -testconnect is written to the logfile R3load.exe.log.

WARNING 2010-11-29 16:30:47.649
Execution of the command "C:\usr\sap\<sid>\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\<sid>\SYS\exe\uc\NTAMD64\R3load.exe: START OF LOG: 20101129162409

C:\usr\sap\<sid>\SYS\exe\uc\NTAMD64\R3load.exe: sccsid @(#) $Id: //bas/700_REL/src/R3ld/R3load/R3ldmain.c#14 $ SAP
C:\usr\sap\<sid>\SYS\exe\uc\NTAMD64\R3load.exe: version R7.00/V1.4 [UNICODE]
Compiled Jan 24 2008 01:41:44
C:\usr\sap\<sid>\SYS\exe\uc\NTAMD64\R3load.exe -testconnect 

(DB) ERROR: DbSlControl(DBSL_CMD_IMP_FUNS_SET) rc = 20
(DB) ERROR: DbSlErrorMsg rc = 20

C:\usr\sap\<sid>\SYS\exe\uc\NTAMD64\R3load.exe: job finished with 1 error(s)
C:\usr\sap\<sid>\SYS\exe\uc\NTAMD64\R3load.exe: END OF LOG: 20101129163047

WARNING[E] 2010-11-29 16:30:47.664
CJS-30023  Process call 'C:\usr\sap\<sid>\SYS\exe\uc\NTAMD64\R3load.exe -testconnect' exits with error code 2. For details see log file(s) R3load.exe.log.

ERROR 2010-11-29 16:30:47.868
FCO-00011  The step testDatabaseConnection with step key |NW_Onehost|ind|ind|ind|ind|0|0|NW_Onehost_System|ind|ind|ind|ind|2|0|NW_CreateDBandLoad|ind|ind|ind|ind|10|0|NW_ABAP_Import_Dialog|ind|ind|ind|ind|5|0|NW_ABAP_Import|ind|ind|ind|ind|0|0|testDatabaseConnection was executed with status ERROR .

XCMDOUT.LOG doesn't seem to have any errors logged.

Where else can I look to find out why R3load.exe won't work? All the install files were downloaded from service.sap.com, so they shouldn't be outdated...

I have even tried to revert to a snapshot before the SAP installation was started, and installed again, with the same error.

Any assistance would be appreciated!

[Former Member · Accepted solution]

Check the below command and see whether you are able to connect or not.

R3load.exe -testconnect

[Former Member · Accepted solution]

I have tried this with no luck - I get the same response as in the R3load.exe.log file in my initial post.

[Former Member · Accepted solution]

are you sure that your database is up and xserver service is running?

[Former Member · Accepted solution]

I have checked and the "xserver" service is running and so is the "maxdb: <sid>" service. I can connect to the DB using the DBM Command Line Interface...

[Former Member · Accepted solution]

Did you check the environment variables?

[Former Member · Accepted solution]

What environment variables must I check?

[Former Member · Accepted solution]

Check the installation guide if there are any settings required. Maybe a path to a library is missing so that the R3load call fails.

[Former Member]

Thanks everyone for your help. I eventually downloaded an updated version of SapInst.exe and reran the installer - this fixed the problem and installed correctly. The instance started, but there was a transaction SICK error when logging in - this was caused because Kernel was not compatible with 2008 R2. I then upgraded the Kernel to version 111, and all worked fine.

[Former Member]

Hi,

sorry to bring the old thread back to life. I tried to download the sapinst.exe, but im not able to find the file in the market. Can anyone lead me to the file or paste a link ?

With friendly greetings & thanks in advance.

[markus_doehr2]

Try to apply

Note 1517280 - MaxDB and Windows 2008 (R2): R3load call fails

Markus

[Former Member]

Hello,

-> did you implement note 688028 for both users : <sid>adm and SAPService<SID>

-> try adding both users to "Administrator" group as well (reboot of Windows server is required for this to work)

Regards

Ivan

[Former Member]

Hello,

1)

last time I checked ECC 6 on MaxDB was not released on Windows Server 2008 R2 so the fact that it does not work could be normal (non R2 WS2008 was released ).

2)

please log in as <sid>adm and run

R3trans.exe -d

you will find file trans.log in your local or home directory, check the log for any error

3)

add "X:\sapdb\programs\pgm\" int your PATH env variable for <sid>adm and SAPService<SID> users

and test the issue again

Regards

Ivan

[Former Member]

I have checked and the environment variables are already set up - this is done as system environment variables and not user variables - I assume that is alright...

Here is an extract from the trans.log file:

4 ETW000  [dev trc     ,00000]   -> connect()                                        181  0.010344
4 ETW000  [dev trc     ,00000]  INFO : SQLOPT= -I 0 -t 0 -S SAPR3                     42  0.010386
4 ETW000  [dev trc     ,00000]  Try to connect (DEFAULT) on connection 0 ...          70  0.010456
4 ETW000  [dbsdbsql    ,00000]  *** ERROR => Connect to database failed, rc = -10709 (Connection failed (RTE:could not create comm. shared memory [5]))
4 ETW000                                                                          344295  0.354751
4 ETW000  [dev trc     ,00000]   -> SetSapdbCA(errcode=-10709)                        23  0.354774
4 ETW000  [dev trc     ,00000]   -> freeConnection(con_hdl=0)                         19  0.354793
4 ETW000  [dev trc     ,00000]   -> sdb_free(p=00000000003EF2F0, size=608 (1145996 bytes allocated))
4 ETW000                                                                              65  0.354858
4 ETW000  [dev trc     ,00000]   -> sdb_free(p=00000000003EEC50, size=1672 (1144308 bytes allocated))
4 ETW000                                                                              40  0.354898
4 ETW000  [dev trc     ,00000]  } DbSlSdbConnect(rc=99)                               14  0.354912
4 ETW000  [dblink      ,00431]  ***LOG BY2=>sql error -10709 performing CON [dblink#5 @ 431]
4 ETW000                                                                             126  0.355038
4 ETW000  [dblink      ,00431]  ***LOG BY0=>Connection failed (RTE:could not create comm. shared memory [5]) [dblink#5 @ 431]

Any ideas what could be causing the problem there?

[Former Member]

Not sure what is your OS and DB version but check below notes

Note 919224 - System requirement Windows X64 liveCache/MaxDB 7.5 to 7.8

Note 919223 - System requirement Windows IA64 liveCache/MaxDB 7.5 to 7.8

[former_member229109]

Hello David,

1.

Concerning your last error in from the trans.log file please check the solution given in SAP Note No. 688028.

2.

It will be helpful to know:

the OS of the database server

The version of the database

the SAP kernel version and patch

R3trans version

Do you have the database and application running on the same server?

The output of the command "sdbregview -l".

3.

I recommend you create the SAP message & get SAP support.

Thank you and best regards, Natalia Khlopina

[Former Member]

Hi Natalia,

Thanks very much for your help so far.

I have implemented note 688028 with no resolution

OS = Win 2008 R2

DB = MaxDB 7.6

SAP Kernel version = 700

R3trans version = 6.14

It is a central installation, so DB and app server are running together.

C:\sapdb\programs\bin>sdbregview -l
DB Analyzer         c:/sapdb/programs    7.6.03.09     64 bit    valid
Server Utilities    c:/sapdb/programs    7.6.03.09     64 bit    valid
PCR 7300            c:/sapdb/programs    7.3.00.59               valid
PCR 7301            c:/sapdb/programs    7.3.01.22               valid
PCR 7500            c:/sapdb/programs    7.5.00.46     64 bit    valid
SAP Utilities       c:/sapdb/programs    7.6.03.09     64 bit    valid
Redist Python       c:/sapdb/programs    7.6.03.09     64 bit    valid
Base                c:/sapdb/programs    7.6.03.09     64 bit    valid
JDBC                c:/sapdb/programs    7.6.03.03               valid
Messages            c:/sapdb/programs    MSG 0.5603              valid
ODBC                c:/sapdb/programs    7.6.03.09     64 bit    valid
Database Kernel     c:/sapdb/k5d/db      7.6.03.09     64 bit    valid
Loader              c:/sapdb/programs    7.6.03.09     64 bit    valid
SQLDBC              c:/sapdb/programs    7.6.03.09     64 bit    valid
SQLDBC 76           c:/sapdb/programs    7.6.03.09     64 bit    valid
Fastload API        c:/sapdb/programs    7.6.03.09     64 bit    valid