cancel
Showing results for 
Search instead for 
Did you mean: 

SolMan 4.0 SR2 Step 30 Password Not Allowed Error Changing DDIC Pwd

Former Member
0 Kudos

I'm on Step 30 of my SOLMAN install. SAPInst is trying to change the DDIC.000 password and gets the error, "PASSWORD_NOT_ALLOWED". DDIC can connect to the RFC just fine. I went in through the client and changed DDIC and SAP* passwords back to the default numeric values.

I did notice that in sapinst_dev.log there were these lines ...

TRACE [sixxbinifileparameter.cpp:397]

InifileParameterManager::getAndSetIniFileParameter()

Set value to context parameter ddic000Password of component instance |NW_Onehost|ind|ind|ind|ind|0|0|NW_Onehost_System|ind|ind|ind|ind|1|0|NW_CI_Instance|ind|ind|ind|ind|11|0|NW_CI_Instance_ABAP_Reports|ind|ind|ind|ind|2|0|NW_DDIC_Password|ind|ind|ind|ind|0|0 to value ""

TRACE [sixxbinifileparameter.cpp:397]

InifileParameterManager::getAndSetIniFileParameter()

Set value to context parameter ddic001Password of component instance |NW_Onehost|ind|ind|ind|ind|0|0|NW_Onehost_System|ind|ind|ind|ind|1|0|NW_CI_Instance|ind|ind|ind|ind|11|0|NW_CI_Instance_ABAP_Reports|ind|ind|ind|ind|2|0|NW_DDIC_Password|ind|ind|ind|ind|0|0 to value ""

TRACE [sixxbinifileparameter.cpp:397]

InifileParameterManager::getAndSetIniFileParameter()

Set value to context parameter needDDICPasswords of component instance |NW_Onehost|ind|ind|ind|ind|0|0|NW_Onehost_System|ind|ind|ind|ind|1|0|NW_CI_Instance|ind|ind|ind|ind|11|0|NW_CI_Instance_ABAP_Reports|ind|ind|ind|ind|2|0|NW_DDIC_Password|ind|ind|ind|ind|0|0 to value "false"

where it looks like the DDIC passwords are being set to "". I know that when you log in, a blank pwd isn't allowed. Does this setting make it revert to the std numeric one or is it telling me that a blank pwd isn't allowed? Is there a way to change this?

Points, as usual ... and thanks!

Rod Wagoner

Accepted Solutions (0)

Answers (1)

Answers (1)

Former Member
0 Kudos

Hi Rod,

Have you given the password of DDIC as 19920706? If not try that.Also check if DDIC is locked.

Did you at any stage change the DDIC password ?

Regards.

Ruchit.

Former Member
0 Kudos

Hi Ruchit,

I never set or entered a password for DDIC, but I did logon as sap* and change it to the default, 19920706. This allowed me to get past a previous step in the installation.

No, DDIC is not locked. It is able to connect but it seems like the password that it wants to change to isn't right. Is it trying to change it to "PASS"? The logon client demands at least 6 characters.

Here's the ouput of SAPInst.log

INFO 2007-05-17 11:01:33

Copied file 'C:/Program Files/sapinst_instdir/SOLMAN/SYSTEM/MSS/CENTRAL/AS/inifile.xml' to 'C:/Program Files/sapinst_instdir/SOLMAN/SYSTEM/MSS/CENTRAL/AS/inifile.22.xml'.

INFO 2007-05-17 11:01:33

Copied file 'C:/Program Files/sapinst_instdir/SOLMAN/SYSTEM/MSS/CENTRAL/AS/inifile.xml' to 'C:/Program Files/sapinst_instdir/SOLMAN/SYSTEM/MSS/CENTRAL/AS/inifile.23.xml'.

INFO 2007-05-17 11:01:36

Execute step

Component W2K_ServicePack_Check|ind|ind|ind|ind

Preprocess of component |NW_Onehost|ind|ind|ind|ind|0|0|NW_First_Steps|ind|ind|ind|ind|0|0|W2K_ServicePack_Check|ind|ind|ind|ind|2|0.

INFO 2007-05-17 11:01:47

Copied file 'C:/Program Files/sapinst_instdir/SOLMAN/SYSTEM/MSS/CENTRAL/AS/keydb.xml' to 'C:/Program Files/sapinst_instdir/SOLMAN/SYSTEM/MSS/CENTRAL/AS/keydb.12.xml'.

INFO 2007-05-17 11:01:47

Execute step changeDDIC000Password of component |NW_Onehost|ind|ind|ind|ind|0|0|NW_Onehost_System|ind|ind|ind|ind|1|0|NW_CI_Instance|ind|ind|ind|ind|11|0|NW_CI_Instance_ABAP_Reports|ind|ind|ind|ind|2|0|NW_CI_Instance_ABAP_Passwords|ind|ind|ind|ind|3|0.

INFO 2007-05-17 11:01:48

RFC parameter CLIENT set to value 000.

INFO 2007-05-17 11:01:48

RFC parameter USER set to value DDIC.

INFO 2007-05-17 11:01:48

RFC parameter LCHECK set to value 1.

INFO 2007-05-17 11:01:48

RFC parameter PCS set to value 1.

INFO 2007-05-17 11:01:48

RFC parameter LANG set to value EN.

INFO 2007-05-17 11:01:48

RFC parameter ASHOST set to value uspowsqa1.

INFO 2007-05-17 11:01:48

RFC parameter SYSNR set to value 00.

INFO 2007-05-17 11:01:48

RFC connection information checked successfully.

INFO 2007-05-17 11:01:48

RFC connection opened successfully.

INFO 2007-05-17 11:01:48

Setting new application function RFC_SYSTEM_INFO.

INFO 2007-05-17 11:01:48

Generating interface for remote function.

INFO 2007-05-17 11:01:49

Function call was successful.

INFO 2007-05-17 11:01:49

Function interface generated successfully.

INFO 2007-05-17 11:01:49

Technical properties of function set successfully.

INFO 2007-05-17 11:01:49

Information for application function RFC_SYSTEM_INFO copied to local Repository.

INFO 2007-05-17 11:01:49

Function module RFC_SYSTEM_INFO set successfully.

INFO 2007-05-17 11:01:49

Executing function call RFC_SYSTEM_INFO.

INFO 2007-05-17 11:01:49

Function call was successful.

INFO 2007-05-17 11:01:49

Version 700 of remote SAP System UGS accepted.

INFO 2007-05-17 11:01:49

Setting new application function SUSR_USER_CHANGE_PASSWORD_RFC.

INFO 2007-05-17 11:01:49

Generating interface for remote function.

INFO 2007-05-17 11:01:49

Function call was successful.

INFO 2007-05-17 11:01:49

Function interface generated successfully.

INFO 2007-05-17 11:01:49

Technical properties of function set successfully.

INFO 2007-05-17 11:01:49

Information for application function SUSR_USER_CHANGE_PASSWORD_RFC copied to local Repository.

INFO 2007-05-17 11:01:49

Function module SUSR_USER_CHANGE_PASSWORD_RFC set successfully.

INFO 2007-05-17 11:01:49

Executing function call SUSR_USER_CHANGE_PASSWORD_RFC.

ERROR 2007-05-17 11:01:49

FRF-00028 Function call raised a program-driven exception PASSWORD_NOT_ALLOWED.

INFO 2007-05-17 11:01:49

RFC connection closed.

ERROR 2007-05-17 11:01:49

MUT-03025 Caught ERfcExcept in Modulecall: PASSWORD_NOT_ALLOWED.

ERROR 2007-05-17 11:01:49

FCO-00011 The step changeDDIC000Password with step key |NW_Onehost|ind|ind|ind|ind|0|0|NW_Onehost_System|ind|ind|ind|ind|1|0|NW_CI_Instance|ind|ind|ind|ind|11|0|NW_CI_Instance_ABAP_Reports|ind|ind|ind|ind|2|0|NW_CI_Instance_ABAP_Passwords|ind|ind|ind|ind|3|0|changeDDIC000Password was executed with status ERROR .

INFO 2007-05-17 11:02:03

An error occured and the user decide to stop.\n Current step "|NW_Onehost|ind|ind|ind|ind|0|0|NW_Onehost_System|ind|ind|ind|ind|1|0|NW_CI_Instance|ind|ind|ind|ind|11|0|NW_CI_Instance_ABAP_Reports|ind|ind|ind|ind|2|0|NW_CI_Instance_ABAP_Passwords|ind|ind|ind|ind|3|0|changeDDIC000Password".

I'm hoping not to have to reinstall.

Thanks for your reply,

Rod

Former Member
0 Kudos

Here's a question ...

What does this funtion try to change the password to?

Thanks,

Rod

Former Member
0 Kudos

Hi Rod,

I think the function module is trying to set the password to 19920706. This will not happen since the password is already 19920706 and old and new password cannot be same. What I will suggest is that at this stage change the password to something else, note it down and continue with the installation.

I hope it will work.

Regards.

Ruchit.

Former Member
0 Kudos

Hi Ruchit,

in webas7 the default password are defined during the installation not 1990706

Hi Rod :

check wether you are trying with password is not the same which you gave during installation also new password cannot be <b>pass</b> try giving password having missed charecters i.e, alphanumaric

Samrat

Former Member
0 Kudos

Hello Samrat,

Sorry did not get what you mean by:

in webas7 the default password are defined during the installation not 1990706

Regards.

Ruchit.

Former Member
0 Kudos

solman4.0 is considered to be on WEBAS700

till 4.7EE ddic and sap* passwords of client 000 used to be 19920706 & 06071992 but when we do installation of starting from ECC5 which runs on WEBAS640 they picks up password from keydb.xml which we need to feed the during input phase of installation

Former Member
0 Kudos

Hello Samrat,

Thanks a lot for the clarification.

Frankly I will not completely disagree with you. However my understanding of this is that during installation SAP asks you for the password of DDIC. However if I remember correctly then you may choose to skip that part and in that case SAP will automatically take the default password. That is if memory serves me right. I might be wrong but also check this link:

http://help.sap.com/saphelp_nw04s/helpdata/en/3e/cdaccbedc411d3a6510000e835363f/content.htm

This is for Netweaver 2004s which as per the definition will also fall into WEB AS 700.

However another interesting thing.With Netweaver 2004s the concept of WAS or WebAS is gone . Check out this:

/people/michael.eacrett/blog/2006/06/17/obituary-for-sap-netweaver-components-2003-150-2005

So WEBAS 700 is not a correct terminology anymore.

Regards.

Ruchit.