Backup Exec 2010 upgrade reports there was a problem upgrading the Backup Exec Device & Media Service and the Backup Exec services will not start.

Article:TECH125397  |  Created: 2010-01-23  |  Updated: 2011-03-31  |  Article URL http://www.symantec.com/docs/TECH125397
Article Type
Technical Solution

Product(s)

Environment

Languages

Problem



Backup Exec for Windows 2010 upgrade reports there was a problem upgrading the Backup Exec Device & Media Service and the Backup Exec services will not start.

During an upgrade from Backup Exec for Windows 11d, 12.0 , and 12.5 to Backup Exec for Windows 2010 the upgrade reports the following message at the end of the installation:


Error



Database upgrade did not complete successfully. All devices, media and jobs will not be migrated from your prior version.
There was a problem upgrading the Backup Exec Device & Media Service

The Backup Exec 2010 upgrade completes and the Backup Exec Service will not start. 

The following error is observed in the Application Log when attempting to start the Backup Exec services:
 
Event Type: Error
Event Source: Service Control Manager
Description:
The Backup Exec Device & Media Service service terminated with service-specific error 536928977 (0x2000E2D1).
  
Reviewing the Backup Exec Installation Log (BKUPINST.HTM) the following error "Failure 1 running migration library 0" is observed:
 
In BeMigl MG_Start
Running migration library 0
library Name C:\Program Files\Symantec\Backup Exec\pvlupgrade.dll
Pvlupgrade MIG_Start()- start
ADAMM upgrade started
Querying version data
VersionName = ADAMM 12.5, VersionNumber = 12.5000000000
There was a problem upgrading the Backup Exec Device & Media Service Database, version 12.500000.
ADAMM upgrade ended
Failure 1 running migration library 0

 


Solution



1. Start the Backup Exec live Debugger utility (SGMON.exe) located in the Backup Exec install directory (X:\Program files\Symantec\Backup Exec\SGMON.EXE).
  
2. In SGMON check the boxes to Capture "Third Party Debug Output" and "Capture to file".  See related documents for more information about SGMON debug utility.
  
3. Backup Exec has a command line migration tool (BEMIG.EXE) that can be used to manually upgrade previous supported version of Backup Exec databases to Backup Exec 2010.
  
4. Open a command prompt to the Backup Exec install directory (X:\Program Files\Symantec\Backup Exec) and type BEMIG.exe.
  
5. Review the output of BEMIG in the command window.  If the message "Upgrade State Set to 805306369" appears (figure 1) then review the SGMON output.
  
FIGURE 1

 
BEMIG: [0000]
BEMIG: [0000]     VersionName   = ADAMM 12.5,  VersionNumber = 12.5000000000
BEMIG: [0000]     UpgradeTo13_000000
BEMIG: [0000]     SQL script name: C:\Program Files\Symantec\Backup Exec\AdammUpgrade126.sql
BEMIG: [0000]     [Microsoft][ODBC SQL Server Driver][SQL Server]Column names in each table must be unique. Column name 'AllocatedTo' in table 'PhysicalDisk' is specified more than once.
BEMIG: [0000]     , retval: 1
BEMIG: [0000]     There was a problem upgrading the Backup Exec Device & Media Service Database, version 12.500000.


This issue has been resolved with Hotfix 344584. (See the related documents for download information)
  • Apply Backup Exec 2010 R1 Hotfix 344584 or Service Pack 1.
  • Run BEMIG Migration Command line utility after creating the appropriate Upgrade and Upgrade Version Registry keys per Technote (TECH50537).
  • Start the Backup Exec Services

Supplemental Materials

SourceETrack
Value1974283
Description

Upgrade from BEWS 12.5 to BEWS 2010 fails There was a problem upgrading the Backup Exec Device & Media Service Database, version 12.500000 Failure 1 running migration library 0

SourceEvent ID
Value7024
Description

The Backup Exec Device & Media Service service terminated with service-specific error 536928977 (0x2000E2D1)

Related Articles



Legacy ID



346113


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


Terms of use for this information are found in Legal Notices

Please Sign In

Login using SymAccount.

Knowledge Base Search

Knowledge Base Search

Rate this Article

Help us improve your support experience.

MySymantec

MySymantec

Contacting Support

Contacting Support