Ucybcryp creates encrypted password not recognized correctly by Automation Engine or Utilities

Document ID : KB000084645
Last Modified Date : 14/04/2018
Show Technical Document Details
Error Message :
SQL Server : U00003590 UCUDB - DB error: 'SQLDriverConnect', 'ERROR ', '28000', 'Login failed for user 'uc4'.'
Oracle : U00003592 UCUDB - Status: '' Native error: '1017' Msg: 'ORA-01017: invalid username/password; logon denied'

The program ucybcryp creates an encrypted password that is not decoded correctly by the Automation Engine or by the Utilities.

The component using this password (i.e. Utility or AE server) returns an invalid credentials error, then writes a forced trace and crashes.

  • Change the password of the AE DB user to 'te^st'
  • Encode the password with the following command: UCYBCRYP[.exe] -p -n te^st
  • Copy the encrypted password into the ini file of a component that connects to the AE DB (a utility or the DB server itself), then start this component.


Expected : the component should run with no issues.

Actual : the connection to the database fails with an 'invalid login' error.

OS: All Windows
Cause type:
By design
Root Cause: This is not related to the encryption tool. The issue is related to the escape character (^), which is interpreted by the windows shell (cmd.exe).
There can be 2 causes:

1 - The two leading hyphens of the encrypted password (stored in Password.ucc) should not be copy / pasted, but rather typed in manually inside the ini file. If they are copied the password will not be correctly recognized.

2 - The password contains a '^' (escape character) which is wrongly interpreted by the windows "shell". This prevents the encryption tool from working properly.
In order to generate a password that is recognized, use Powershell to start the encryption tool.

Example: the password 'te^st' is encrypted

a - With cmd:


b - With Powershell:



Fix Status: No Fix

Additional Information:
Workaround :