Error 1606 when attempting to upgrade or un-install the ESM console

Article:TECH137799  |  Created: 2010-08-16  |  Updated: 2012-04-27  |  Article URL
NOTE: If you are experiencing this particular known issue, we recommend that you Subscribe to receive email notification each time this article is updated. Subscribers will be the first to learn about any releases, status changes, workarounds or decisions made.
Article Type
Technical Solution


During upgrade or uninstallation of the ESM Console error 1606 is displayed. 





Another error possibility is that it lists a network path instead of the path to the console.  For example:   \\<machinename>\folder



Two known causes:

1. The screenshot above shows an error indicating that not all registry keys were created correctly during the original console installation.

During the installation of the ESM console registry keys get created which hold information about the Installation folder of the ESM Console. For some reason those keys didn get created and the installer is now not able to determine where the Console is installed.

2. If the 1606 error indicates a network path such as \\machinename\folder  then this indicates that the ID being used during installation\upgrade is a domain ID that has an entry in its Active Directory record for the home directory being located on a network drive.  The installation is failing because this path is inaccessible from the ESM console machine for some reason. 



The solution to issue number 1 is:

Please check that the following keys are present:

HKLM\SOFTWARE\Symantec\ESM Enterprise Console\installDir



If they are not present please create the two keys and give as value the path where the ESM Console is installed. By default this is C:\Program Files\Symantec\Enterprise Security Manager\Symantec ESM Enterprise Console

Solution to issue number 2:

Contact the Active Directory administrator and have the profile changed to indicate a non-network path.  Alternatively, use another ID to uninstall\upgrade the ESM console.  In all cases the ID needs to be a member of the administrators group on the ESM console machine.  Use of the local administrator account would also be a solution here.

Article URL

Terms of use for this information are found in Legal Notices