SAN Shared Storage Option (SSO) secondary server upgrade fails with error 1603

Article:TECH208448  |  Created: 2013-07-09  |  Updated: 2013-09-04  |  Article URL http://www.symantec.com/docs/TECH208448
Article Type
Technical Solution


Issue



An error 1603 may occur when you upgrade a secondary server in a SAN from Backup Exec 12.5 to Backup Exec 2010 R2. The secondary server may also receive an error message that indicates that the Remote Procedure Call service encountered a problem and needs to close.


Error



The install fails with the following error:

Install failed with error code 1603. Right-click on the computer to view logs for more information.

The Install.log displays the following error:

ERROR: Installation failed with error 1603. GetLastError - :0


Cause



When you upgrade the Backup Exec Shared Storage Option on the primary server, you must stop the services on all of the secondary servers. After the primary server is upgraded, if the services on the secondary server are started for any reason such as a manual restart, system restart, or a failed upgrade, the upgrade of the secondary server fails.


Solution



Perform the following on the servers indicated:

Step 1
On the primary server, find the numeric suffix for each secondary server that experienced an error in the SSOData.txt file. The SSOData.txt file is usually located in the following directory where Backup Exec files are installed:
 
\Program Files\Symantec\Backup Exec\Data\SSOData
 
The numeric suffix is in the following format:
bedb_dat[Secondaryservername]_[numericsuffix].mdf
 
Step 2
On each secondary server that experienced an error, do the following in the order listed:
  • Click Start, and then click Run.
     
  • Type Regedit.
     
  • Expand HKEY_LOCAL_MACHINE\SOFTWARE\Symantec\Backup Exec For Windows\Backup Exec\Server.
     
  • Change the value for DataPartitionID from 0 to the numeric suffix of the secondary server that is in the SSOData.txt file.
     
  • Click OK.
Warning: Do not change the Backup Exec services, for example, stopping or starting the services or restarting the services, on the secondary server after you update the DataPartitionID registry key.
 
Step 3
On the primary server, run the install again on the secondary server. If you are upgrading multiple servers, press the <Ctrl> or <Shift> keys while you click other computers that you want to select. Right-click the computers, and then on the shortcut menu, click Retry Validation.
 
Note:  If you receive a write protection memory error, right-click the computer on which the error occurred, select Retry Validation, and then continue with the upgrade.

 



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


Terms of use for this information are found in Legal Notices