On Windows 2003,
instance creation might fail if the user password does not meet the
operating system password requirements. Understand the cause of this
problem and follow the steps to resolve it.
Instance creation fails on Windows 2003
- Reason:
- After the installation of IBM® Security
Directory Server, you can create an instance with default options.
Instance creation and configuration utilities of IBM Security
Directory Server might take a password that does not meet the operating
system password requirements.
On Windows 2003,
the configuration fails during the instance owner creation stage with
the following messages. These messages are seen on the console and
are also available in the
idsadm.log file of
directory server:
Jul 16 10:21:42 2008 You have chosen to perform the following actions:
Jul 16 10:21:42 2008 GLPGRP019I System user will be created for directory
server instance.
Jul 16 10:21:42 2008 GLPGRP020I The system user 'idsinst' will be created.
Jul 16 10:21:42 2008 GLPGRP026I The user 'idsinst' will be a member of the
'administrators' group.
Jul 16 10:21:42 2008 GLPGRP005I The password for user 'idsinst' will be set.
Jul 16 10:21:42 2008 GLPGRP002I Creating system user 'idsinst'.
Jul 16 10:21:42 2008 GLPGRP006I Setting the password for user 'idsinst'
Jul 16 10:21:43 2008 GLPGRP043E Failed to create user 'idsinst'. Error code
return by 'NetUserAdd API' is 2245.
Jul 16 10:21:43 2008 GLPGRP010W The program did not complete successfully.
View earlier error messages for information
about the exact error.
- Solution:
- In this particular scenario, the explanation for the message, 2245
- NERR_PasswordTooShort, is that the password was shorter
than the operating system password requirements. To rectify this problem,
use a password that meets the operating system password requirements.
To know more about password requirements for a Windows operating system, see Password
must meet complexity requirements.
The instance creation
can also fail for the following reasons:
- Password is too long
- Password might be the recent most in the change history
- Password does not have enough unique characters
- Password does not meet the password policy requirements