Logging into EZTeller32 as Vault Teller, you receive a BDS login failed but you cannot modify the host security code.

Logging into EZTeller32 as Vault Teller, you receive a BDS login failed but you cannot modify the host security code.

BDS login failed, some inquiries may not be available. Please check your user name and password. 
 


Root Cause:

In EZTeller®32, under the Other > Modify, the option Host Security is disabled so the teller cannot update the host password.

 

By design, the Vault Teller (authority level -0-) cannot process customer transactions. The vault can do internal transactions such as buying and selling cash. This is why the Other > Modify > Host Security is disabled. 


However, EZTeller32 does connect to the host during the login so the Vault Teller can do host inquiries.


Environment:

EZTeller32 and ITI Standard

Workaround:

Follow the steps below to resolve this issue:

  1. Log in to Superview®32 and go to Tellers > Edit.
  2. Select the Vault Teller role (Teller 4 in this example) and click Edit.
  3. Change the Authority Level from Vault Teller to Teller.
  4. Click Apply and OK.
  5. Log in to EZTeller32 as Teller 4. 
  6. Go to Other > Modify > Host Security and complete the fields.

Note: The Host Security Code can have up to 4 numbers. The Host Password can have up to 6 letters, capital letters, or numbers.  

  1. Exit EZTeller32.
  2. Log in to Superview32 and go to Tellers > Edit.
  3. Highlight Teller 4 and click Edit.
  4. Change the Authority Level from Teller to Vault Teller.
  5. Click Apply and OK.
  6. Teller 4, the Vault Teller, is now back at its original configuration and should no longer get the BDS login fail error upon login.

ArticleNumber:

000041308

    • Related Articles

    • Error: Host Rejection Message: Invalid Teller Number, when signing into EZTeller.

      Host rejection message: Invalid Teller Number. Root Cause: You have just upgraded from EZTeller32 to EZTeller Enterprise and receive the following host rejection message: "Invalid Teller Number." Environment: EZTeller Workaround: AS400 Mainframe ...

    • Teller using ALLTEL HORIZON Host Receives the Following Error: Non-Sufficient Cash

      Non-Sufficient Cash Root Cause: ALLTEL HORIZON is currently the only host that keeps track of teller cash. If the setting for Auto Cash Adjust is disabled, then a cashed check is sent to the host as a cash-out transaction, and the teller’s available ...

    • Login failed for user LoanServicing

      Microsoft SQL Server Login Connection failed: SQLState: '28000' SQL Server Error: 18456 [Microsoft][SQL Server Native Client 11.0][SQL Server]Login failed for user 'LoanServicing'. Root Cause: This can be caused by changes to your SQL server, where ...

    • Teller Receives a Host Rejection Message When Attempting to Reverse a Transaction in EZTeller

      Host rejection: Memo post does not exist. Root Cause: A transaction was done while offline to the host. When the teller went back online and attempted to upload the transaction, the host rejected it. This could be because the account number or ...

    • Password Validation Failed

      Password validation failed. The password for the user is too recent to change. Root Cause: The employee's login name, created in SQL Server Management Studio, has the Enforce password policy and Enforce password expiration boxes selected. Workaround: ...