Backup Exec install/upgrade fails with 1406 error

[binhminhitc]

Backup Exec install fails, Fatal Error: Error 1406. Could not write value AdammLocal to key \Software\Symantec\Backup Exec For Windows\Backup Exec\Server. Verify that you have sufficient access to that key, or contact your support personnel.
Cause

1. The account used to Install Backup Exec has insufficient permission in Registry.

2. The Issue is seen if Managed Backup Exec Server feature is selected during an upgrade (to BE 20.1 with Gold License) on a standalone Backup Exec Install.

The upgrade can be completed by clicking ignore but Backup Exec services fail to start.
The application event logs shows event 57802 with below description.

"The Backup Exec Server Service did not start. An internal error (-1) occurred in object 50".
Solution

To resolve this issue, perform the following steps:

Cause 1:

1. Go to Start > Run and type REGEDT32.EXE

Warning: Incorrect use of the Windows registry editor may prevent the operating system from functioning properly. Great care should be taken when making changes to a Windows registry. Registry modifications should only be carried-out by persons experienced in the use of the registry editor application. It is recommended that a complete backup of the registry and workstation be made prior to making any registry changes.

2. Browse to
HKLM|Software|Symantec|Backup Exec for Windows Server|Backup Exec|

3. Right click on the key Backup Exec and select Permissions.

4. Ensure the following accounts are listed with full control:
System
Administrator
Administrators

5. Select "Retry" on the error being prompted on the installation screen or reinitiate the installation.


Cause 2:

The upgrade should be aborted when the error in pop up message box is seen. The Upgrade can then be rerun with Managed Backup Exec Server (MBES) feature deselected.

Note: The managed backup exec server feature should not be installed during upgrade. If the upgrade is completed by selecting ignore then contact technical support for further assistance.

Veritas Technologies LLC has acknowledged that the above-mentioned issue is present in the current version(s) listed under the Product(s) Section of this article. Veritas Technologies LLC is committed to product quality and satisfied customers.

This issue is currently under investigation by Veritas Technologies LLC. Pending the outcome of the investigation, this issue may be resolved by way of a patch or hotfix in current or future revisions of the software. However, this particular issue is not currently scheduled for any release. If you feel this issue has a direct business impact for you and your continued use of the product, please contact your Veritas Sales representative or the Veritas Sales group to discuss these concerns.

Please be sure to refer back to this document periodically as any changes to the status of the issue will be reflected here.