Unable to migrate to 2010R3.

Article:TECH167208  |  Created: 2011-08-16  |  Updated: 2011-08-16  |  Article URL http://www.symantec.com/docs/TECH167208
Article Type
Technical Solution




Unable to upgrade to Backup exec 2010R3


V-225-206: Cannot open user default database. Login failed. Login failed for user 'DOMAIN\administrator'. Shared Memory Provider: I/O Error detected in read/write operation [4]. Communication link failure

V-225-212: Unable to connect to SQL Server.

Failed to configure SQL instance SERVER\BKUPEXECDLO SQL instance to allow updates.

FATAL ERROR: BEMSI;InstallManager.dll;InstallManager.cpp;ConfigInstall_MSI()-ConfigSQLToAllowUpdates();1602


To resolve this issue ensure that the Registry Key "AppData" is present in the location HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\User Shell Folders\AppData.
If the above mentioned key is not present in both the locations then create the Expandable String Value "AppData" with value %USERPROFILE%\Application Data
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.


1. Login to the server using the Backup Exec Service Account (BESA).

2. Open SQL Management Studio and connect to BKUPEXEC instance.
3. Go to Security > Logins > Open the properties of the BESA account.
4. Set the default database to the master database.
5. Run the installation again using BESA account.

Article URL http://www.symantec.com/docs/TECH167208

Terms of use for this information are found in Legal Notices