1. Please take a little time for this simple survey! Thank you for participating!
    Dismiss Notice
  2. Dear Pleskians, please read this carefully! New attachments and other rules Thank you!
    Dismiss Notice
  3. Dear Pleskians, I really hope that you will share your opinion in this Special topic for chatter about Plesk in the Clouds. Thank you!
    Dismiss Notice

error while setup physical hosting

Discussion in 'Plesk for Windows - 8.x and Older' started by shark95763, Mar 6, 2006.

  1. shark95763

    shark95763 Guest

    0
     
    When I create a new domain, I always get this error , no matter what password's or username's I try to create :

    Unable to assign variables for PHostingForm: Unable to get hardquota state: Unable to add the user (panzernl), invalid parameter is (-1): (2245) The password does not meet the password policy requirements. Check the minimum password length, password complexity and password history requirements.

    --------------------------------------------------------------------------------

    0: D:\Program Files\SWsoft\Plesk\admin\htdocs\domains\hosting\phosting_setup.php:279 psaerror(string "Unable to assign variables for PHostingForm: Unable to get hardquota state: Unable to add the user (panzernl), invalid parameter is (-1): (2245) The password does not meet the password policy requirements. Check the minimum password length, password complexity and password history requirements.")


    how to fix?
     
  2. OlegB

    OlegB Guest

    0
     
    You've got custom password policy configured.

    To disable password checking you need to go

    Start > Administrative Tolls > Local Security Policy > Expand Account Polices > Expand Password Policy > Double click on `Password must meet complexity requirements` > Disable.

    Then the problem will gone.
     
  3. ukjim

    ukjim Guest

    0
     
    The fact we're told to turn off password complexity so that Plesk is able to work if people add users with insufficiently complex passwords is pathetic.
    Plesk should be fixed to respond correctly to user creation errors.
    Also if a user creation fails, it should rollback the addition of the domain entry into the DNS configuration, which you otherwise have to manually remove before re-attempting to create the user with a correct password complexity.
    Plesk should be accomodating ALL industry standard security mechanisms.
     
Loading...