cancel
Showing results for 
Search instead for 
Did you mean: 

Sapinst fails on phase: ddic check password

Former Member
0 Kudos

Hello,

We're doing a system copy of ECC (netweaver 7.3). We get an error during sapinst, in phase 23 of 35: "Test logon to SAP system failed. SOLUTION: Make sure that the system is started, that the user DDIC exists and that the password of user DDIC is correct."

SAP is up and running, and it is possible to logon with user sap* in client 000.

What we have tried without success:

* Reset DDIC password in client 000 and 001 (tried different passwords, also default: 19920706)

* Restart of SAP, DB and server

* Closed the sapinst and continued

* Checked listeners

* Changed to proper kernel

Last lines from sapinst.log:

INFO 2015-04-20 10:01:49.441

RFC connection information checked successfully.

WARNING[E] 2015-04-20 10:01:49.644

FRF-00007  Unable to open RFC connection.

INFO 2015-04-20 10:01:49.659

RFC parameter CLIENT set to value 000.

INFO 2015-04-20 10:01:49.659

RFC parameter USER set to value DDIC.

INFO 2015-04-20 10:01:49.659

RFC parameter LCHECK set to value 1.

INFO 2015-04-20 10:01:49.659

RFC parameter PCS set to value 1.

INFO 2015-04-20 10:01:49.659

RFC parameter LANG set to value EN.

INFO 2015-04-20 10:01:49.659

RFC parameter ASHOST set to value sap1xxx.

INFO 2015-04-20 10:01:49.659

RFC parameter SYSNR set to value 00.

INFO 2015-04-20 10:01:49.659

RFC connection information checked successfully.

WARNING[E] 2015-04-20 10:01:49.706

FRF-00007  Unable to open RFC connection.

Last lines from dev_trfc.trc:

*** ERROR file opened at 20150420 100149 W. Europe Daylight Time, SAP-REL 720,0,515 RFC-VER 3 1450009 MT-SL

T:3880 Error in program 'sapinst': ======> Logon not possible (error in license check)

T:3880 Error in program 'sapinst': <* RfcReceive [1] : returns 3:RFC_SYS_EXCEPTION

T:3880 Error in program 'sapinst': ======>

>>> RfcOpenEx ...

Got following connect_param string:

   ASHOST=sap1xxx CLIENT=000 LANG=EN LCHECK=1 PASSWD=******* PCS=1 SYSNR=00 USER=DDIC

<<< RfcOpenEx failed

T:3880 Error in program 'sapinst': ======> Logon not possible (error in license check)

T:3880 Error in program 'sapinst': <* RfcReceive [2] : returns 3:RFC_SYS_EXCEPTION

T:3880 Error in program 'sapinst': ======>

>>> RfcOpenEx ...

Got following connect_param string:

   ASHOST=sap1xxx CLIENT=000 LANG=EN LCHECK=1 PASSWD=******* PCS=1 SYSNR=00 USER=DDIC

<<< RfcOpenEx failed

Thanks!

Accepted Solutions (0)

Answers (6)

Answers (6)

thomas_mhl
Explorer
0 Kudos

Workaround:

Regards

Thomas

Former Member
0 Kudos

Hey guys,

It turned out to be a kernel problem. SAP provided us with a new kernel.

M.

khampariamukesh
Active Participant
0 Kudos

Hi,

I understand that u changed DDIC pass (Dialog user), have you tried login because it will ask to change pass in first screen. Also I dont see any problem loging with DDIC during installation..

Check and let me.. If i can help further..

khampariamukesh
Active Participant
0 Kudos

Please keep you DDIC final password same as you provided in previous stage.

manumohandas82
Active Contributor
0 Kudos

Hi Moye ,

Please go to transaction SLICENSE ( USING SAP* 000 ) and remove all the old licenses . If you  have issues with the transaction

982056 - The license key library has not been initialized yet.


Thanks ,

Manu

Former Member
0 Kudos

There are no licenses listed...

M.

manumohandas82
Active Contributor
0 Kudos

Hi Moye ,

Are you getting the error  "The license key library has not been initialized yet" when you are trying to install new licenses  ? If not  install the new licenses

can you  read sap note 982056  if yes . Check your instance profile . ( You will get lot of threads in SCN  if you search for the error )

Thanks ,

Manu

former_member185954
Active Contributor
0 Kudos

Try installing a templicense in that case.

Sriram2009
Active Contributor
0 Kudos

Hi

OS / DB source and target are same or different? Could you share the OS / DB details?

BR

SS

manumohandas82
Active Contributor
0 Kudos

Hi Moye ,

Are you able to login as SAP* in 000 client ?

If yes this rules out message server issues .

What kernel version are you on ?  are in a version above or equal to 720 ? if No can you check whether the cryptographic libraries are in place ?

Thanks ,

Manu

Former Member
0 Kudos

Hi,

We can logon with sap*  in client 000. Our kernel version is equal to 720.

M.

manumohandas82
Active Contributor
0 Kudos

Hi Moye ,

Please check whether you are able to logon to 001 client using DDIC . If you are getting error in license check   when you try to login to 001 apply the license in 000 client using SAP * and try once again

Thanks ,

Manu

Former Member
0 Kudos

Hi, thanks for replying. Are you sure that we're supposed to be able to logon with user DDIC in this installation phase? I think the license is added in a later step too...

M.

former_member185954
Active Contributor
0 Kudos

Hello Moye,

Did you supply the DDIC password in any of your previous stages/screens during the system copy ?

Regards,

Siddhesh

Former Member
0 Kudos

Hi,

Yes- we did supply a password in earlier step, Define parameters.

M.

manumohandas82
Active Contributor
0 Kudos

Hi Moye ,

You primary application server is installed and there is no issue with you trying to login using DDIC ( 000 client , not 001 typo in previous msg ) .

Error with License check could be because of various reasons like kernel , message server , license or others .

Here  by doing as suggested you could just iterate out  one possible cause ie license

Thanks ,

Manu

former_member185954
Active Contributor
0 Kudos

Hello Moye,

The installation program will attempt to use either standard DDIC/SAP* password if you don't provide this password at the earlier step. If I remember correctly, the install program requires this password to run post installation programs such as RDDMNTAB.

Since, you are doing a system copy, the DB has license which is valid for your OLD system, hence the license error.

Reards,

Siddhesh

Former Member
0 Kudos

Hi,

We can't add new license. We get the error message: "The license key library has not been initialized yet."

M.

Sriram2009
Active Contributor
0 Kudos

Hi Moye

I think DDIC user id locked in client 000  due to master password is wrongly entered ,

you have to stop the installation and SAP ABAP instance, follow the steps

1. On SAP default profile just add the enter "login/no_automatic_user_sapstar=0"

2. Start the SAP instance,

3. Logon to SAP system using user id " SAP* "  password  pass or 06071992

4. Enable the user id DDIC and set the password same as master password or

delete the SAP* enter in DB level, for this refer the SCN thread

sap* user delete in oracle db | SCN

5. start the system copy where it was stopped before.

BR

SS

former_member185954
Active Contributor
0 Kudos

Hello Moye,

Perform the steps which SS gave below, you should be fine then.

Good luck.

Regards,

Siddhesh

Former Member
0 Kudos

Hi,

DDIC is not locked...

M.

Sriram2009
Active Contributor
0 Kudos

Hi

Have to set the right time & Time zone on your SAP system?

Kindly refer the SAP Note for "FRF-00007  Unable to open RFC connection"

1706931 - Inst. SAP Sys. Based on NW 7.3 and higher: SAP HANA DB, Win


BR

SS

Former Member
0 Kudos

Thanks, but this note is not applicable for our case. We did not get the same error message (time difference).

M.

Sriram2009
Active Contributor
0 Kudos

Hi

1.  Have you check the time zone setting at Os level?

2. Refer the SAP KBA  for " Logon not possible (error in license check)"

1512766 - Most common reasons for error message: "Logon not possible (error in license check)"

BR

SS