on 2005 Jun 20 2:21 PM
My installation is aborted almost immediatly.
I receive a message saying that my password for j2eadm is too short. This is a standard Windows XP message informing that the password is not within my company's standards.
Since I have not entered any user name or password, I can only assume that the installation tries to create a user on its own with a "simple" password.
<b>Anyone know where is the installation file which controls the passwords?</b>
Help others by sharing your knowledge.
AnswerRequest clarification before answering.
Hi michiel / Yaron ,
I am facing the same situation here . I have created two users namely j2eadm and SAPServiceJ2E manually through window panel and assigned the passwords , admin.123 and admin.234 resp ( as per my company policy ) . Then the installer asked for the password for the above users . I have given as what I have created . Now an error as below and installer exited abruptly .
ERROR 2005-07-08 20:34:01
FJS-00003 TypeError: webas has no properties (in script InstallationScript_59, line 14070: ???)
ERROR 2005-07-08 20:34:01
FJS-00003 TypeError: webas has no properties (in script InstallationScript_59, line 14070: ???)
WARNING 2005-07-08 20:34:01
The step askOSUserParameterWindows with step key J2EE_SystemCopy_OneHost|ind|ind|ind|WebAS|640|0|J2EE_SystemCopy|ind|ind|ind|ind|ind|0|J2EE_EngineEnterpriseDialogs|ind|ind|ind|WebAS|630|0|askOSUserParameterWindows was executed with status ERROR.
I am realy sad about this situation . Could anybody give me a solution .Thanks
Aneez
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello All,
I have gotten to the same point. We have domain password restrictions that require a minimum of 8 characters for password. So, it is not possible to reinstall without the password restrictions.
I have created the 2 initial accounts with password: qw123456. I receive the same error Aneez receives.
It is really frustrating that in this age of ever increasing security policies, SAP is not able to adapt. Can we get some feedback from SAP on this issue?
Kind regards,
Rich
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.