cancel
Showing results for 
Search instead for 
Did you mean: 

Help! Cannot install WebAS Test Drive 6.20

Former Member
0 Kudos

I had V6.10 installed and removed it. I am now attemping an install of 6.20. It runs to the point where it has requested info from DATA CDs 1 and 2, and has returned to the Kernel CD. At some point along that path, I see a message that says "Installation of DB Server finished successfully".

However, I am getting this serious installation error:

Error: ADADBREGISTER_IND_ADA ExecuteCheck 2 223

Exit code from C:\sapdb\programs\pgm\dbmcli.exe: 2.

Error: ADADBREGISTER_IND_ADA InternalInstallationDo 2 223

Phase failed.

Error: ADADBREGISTER_IND_ADA InstallationDo 2 223

Phase failed.

Error: Main {} 2 223

Installation aborted.

If I knoew what DBMCLI command it had been attempting, that might give me a clue, but as it stands now I have no idea what's wrong, or how to fix it. Can anyone help? I was looking for a more detailed log than what R3Setup provides online, but can't find anything like a WA1.LOG - is there a log file someplace that might geive me more detailed info?

DBMCLI seems to run ok - is there something I can do with that to surmount this problem? Do I need to diddle with registry entries? (I hope not...)

Any and all help will be greatly appreciated - right now I'm stuck!

Accepted Solutions (0)

Answers (2)

Answers (2)

Former Member
0 Kudos

Well, I removed everything in sight, and now the install goes a lot further, but crases with this message:

INFO 2004-04-18 20:43:01

Creating XUSER File for the User <SAPSID>ADM for Dialog Instance

TRACE 2004-04-18 20:43:01 ADAXUSERSIDADM_DEFAULT_NT_ADA SyCoprocessCreate:0

-> Entering function SyCoprocessCreate (level 1)

INFO 2004-04-18 20:43:01 ADAXUSERSIDADM_DEFAULT_NT_ADA SyCoprocessCreate:931

Creating coprocess C:\sapdb\programs\pgm\dbmcli.exe ...

TRACE 2004-04-18 20:43:01 ADAXUSERSIDADM_DEFAULT_NT_ADA SyCoprocessCreate:0

<- Exiting function SyCoprocessCreate with return code 0 (level 1)

TRACE 2004-04-18 20:43:01 ADAXUSERSIDADM_DEFAULT_NT_ADA SyCoprocessWait:0

-> Entering function SyCoprocessWait (level 1)

TRACE 2004-04-18 20:43:01 ADAXUSERSIDADM_DEFAULT_NT_ADA SyCoprocessWait:0

<- Exiting function SyCoprocessWait with return code 0 (level 1)

INFO 2004-04-18 20:43:01 ADAXUSERSIDADM_DEFAULT_NT_ADA ExecuteDo:0

RC code form SyCoprocessWait = 2 .

ERROR 2004-04-18 20:43:01 ADAXUSERSIDADM_DEFAULT_NT_ADA ExecuteCheck:0

Exit code from C:\sapdb\programs\pgm\dbmcli.exe: 2.

ERROR 2004-04-18 20:43:01 ADAXUSERSIDADM_DEFAULT_NT_ADA InternalInstallationDo:0

Phase failed.

ERROR 2004-04-18 20:43:01 ADAXUSERSIDADM_DEFAULT_NT_ADA InstallationDo:0

Phase failed.

Any idea why I might not be able to create the XUSER file shown above?

Former Member
0 Kudos

The error message in the command window for the previous error is "Incorrect username or password". Now what...????

Former Member
0 Kudos

I have started a new thread for this last question/problem and will show the original problem in this thread as "answered".

Former Member
0 Kudos

David,

I get the same errors by installing MiniWas 6.20. How did you fix this problem?

Thanks.

Peter Specker

Former Member
0 Kudos

I also get these two messages in the command output window:

Setting new Run Directory

Error! Do not mix installation root and instance name!

Is this germane? What do they mean?

Former Member
0 Kudos

Here's what I found in the Kernel CD R3SETYP directory in file BSP.R3S:

[ADADBREGISTER_IND_ADA]

CLASS=CExecute

EXECUTABLE=dbmcli.exe

MSGID=RI_GIST_ADASETRUNDIRECTORY_IND_IND

OPTIONS=-d @DB_NAME@ -u control,control -s -R @DB_HOME@ db_register

PATH=@INDEPENDEND_PROG_PATH@\pgm

STEP_ENV=DB_ENV

I can find some tracks in one of the logs that lead me to believe that:

DB_HOME = C:\sapdb\BSP\db

DB_NAME = BSP

Here's part of the directory structure that's currently on my hardrive:

sapdb

BSP

db

Data

J2E

db

sapdata

saplog

MiniWAS

cache

sapdb

BSP

dbsys

sapdata

saplog

The following service have been started:

SAP DB WWW

Xserver

And finally, I see that one of the logged error messages complains about "mixing installation root and instance names". However, I was never offfered the opportunity during the start of the install to change any of those directlroies - is that normal?

Former Member
0 Kudos

I see that the indention of the directory structure was lost in the post. If it's important, I'll e-mail to whoever's interested...