Search Engine: Elastic

Article ID: 116628, created on Aug 2, 2013, last review on Jul 14, 2018

  • Applies to:
  • Operations Automation


A customer cannot connect to Windows FTP service in their subscription using the existing user they created in POA Customer Control Panel. An attempt to connect fails with the following diagnostics:

530 User cannot log in.

The customer tried to change password of the affected FTP user in POA Control Panel, it did not help to resolve the problem.


Check and unlock the AD user if necessary:

Log into AD Domain Controller by RDP Run 'dsa.msc' in command line tool Find the customer's Organizational Unit in AD and the problem user in it Right-click on the user and choose Properties Switch to the Account tab Unlock the user if it is locked:

Alternatively, customer may wait until the user will be unlocked automatically in accordance with parameters defined in POA system properties:

  1. Failed login attempts checking period (minutes)
  2. User locking period after too many authentication errors (minutes)
  3. Maximum authentication attempts before locking user


Most likely the problem FTP user was locked in Active Directory due to many attempts to log in with wrong password. Changing password in POA Control Panel does not unlock the user.

5356b422f65bdad1c3e9edca5d74a1ae caea8340e2d186a540518d08602aa065 e12cea1d47a3125d335d68e6d4e15e07

Email subscription for changes to this article
Save as PDF