cancel
Showing results for 
Search instead for 
Did you mean: 

sp2 roll back error

David_Slamowitz
Level 4
I get the following error msg from bkupinst.log file after trying to load sp2 after deleting backupexec manually and reinstaling MSDE manually prior to installing SP2. Will changing the name of the catalog folder as noted in previous threads help?

03-30-2005,00:54:05 : In setpercentcomplete no pMigUI returning.
03-30-2005,00:54:05 : Migration running in silent mode
03-30-2005,00:54:05 : Initializing migration library 0
03-30-2005,00:54:05 : Assigning function pointers.
03-30-2005,00:55:22 : Failure 3 initializing migration library 0
03-30-2005,00:55:22 : lp_MG_NoUiInit failed with error 3
03-30-2005,00:55:28 : Executing StopBEServices_MSI.
03-30-2005,00:55:28 : Rolling back stop of BE services.
33 REPLIES 33

A_van_der_Boom
Level 6

> I get the following error msg from bkupinst.log file
> after trying to load sp2 after deleting backupexec
> manually and reinstaling MSDE manually prior to
> installing SP2. Will changing the name of the catalog


You do have installed BE first and then tried to apply BE SP2 ?

Regards
A van der Boom

David_Slamowitz
Level 4
yes, BE was reinstalled after installing MSDE. I then tried installing SP2 and got the error.

Sean_Streets
Level 2
This can be caused by a couple of things.

You need to totally uncluster both nodes before this will actually work.

It may be caused by the MSI broken, there is a MS office utility that will clean up.

It's called the Windows Installer CleanUp Utility. Download it, but use it with caution.

David_Slamowitz
Level 4
I need more specifics about how to do this.

I have Windows Installer CleanUp Utility already insalled. How do I use it?

How do I uncluster a node?

Thanks.

Alan_Foley
Level 4
Please examine the Veritas article 272816.htm. I tried the other articles mentioned and my issue was resolved by changing the upgrade key from a 1 to a 5. Yes the article says it is for SP1, but I had the problem with SP2 after the upgrade was successful on SP1.

My system was a "clean load of W2K3 Standard" with BE 9, version 4454. I upgraded to BE 9.1, SP1. Then had problems. This article fixed it.

David_Slamowitz
Level 4
I looked at Veritas article 272816.htm. There was no upgrade key on my server in the registry at the location specified by the article.

Your issue may have been related to your upgrade. Mine is with a clean install of BE 9.1 after a clean install of the BE MSDE.

I did try to add a key called "upgrade" with a value of 5 in the registry site specified in the article and still got the same error.

Any more ideas would be appreciated.

D.S.

A_van_der_Boom
Level 6
Try running windows update after installing MSDE so the latest hotfixes and patches are applied.

Regards
A van der Boom

Amruta_Purandar
Level 6
Hello,

Please try installing by command line and verify the results.
Title:
How to install a Backup Exec Hotfix or Service Pack without user intervention. (Silent Installation)
http://support.veritas.com/docs/274398

NOTE : If we do not receive your intimation within two business days, this post would be "assumed answered" and archived.

David_Slamowitz
Level 4
I think it worked but when I tried running BE it looks like the BE job engine is not running and when I try to restart it through the tools menu it looks like it starts but I still have a red box in the browser interface. Do I need to reboot?

Here is the bkupinst.log entries:

04-15-2005,10:22:49 : Executing CheckPatchDependencies_MSI.
04-15-2005,10:22:49 : Executing CheckPatchDependencies.
04-15-2005,10:22:49 : Executing GetProductGuid.
04-15-2005,10:22:49 : Executing GetInstalledPatches.
04-15-2005,10:22:49 : Executing GetDependentPatches.
04-15-2005,10:22:49 : Executing CheckForDependencies.
04-15-2005,10:22:49 : All dependencies have been met for this patch.
04-15-2005,10:22:49 : Checking to see if the user has administrator privileges.
04-15-2005,10:22:49 : Checking to see if the Backup Exec UI is running.
04-15-2005,10:22:50 : Executing SetCustomActionData_MSI.
04-15-2005,10:22:50 : Executing DLO_PrepPatch to verify DLO database for patching.
04-15-2005,10:22:50 : There is no BE_DLO.mdf file to check DB version against. Patch process will be able to install updated file IF needed.
04-15-2005,10:22:50 : Executing ECM_PrepECM.
04-15-2005,10:22:50 : Executing CreateECMRegistryKeys.
04-15-2005,10:22:50 : Executing SetWBTVersion_MSI
04-15-2005,10:22:50 : Executing AddECMRemoveFiles.
04-15-2005,10:22:51 : Executing CA PrepBEMain with target BEMain_PrepBEMain.
04-15-2005,10:22:51 : Executing CopySAPR3MediaToAgentsDir
04-15-2005,10:22:51 : Executing SetRegKeys.
04-15-2005,10:22:51 : Executing MakeBEDBBakFile.
04-15-2005,10:22:51 : Executing CA PrepRAMain with target RAMain_PrepRAMain.
04-15-2005,10:22:51 : Executing CopyRAWS32Media
04-15-2005,10:22:51 : Executing CopyRAWS64Media
04-15-2005,10:22:51 : Executing SetRAMainRegKeys.
04-15-2005,10:22:53 : Executing RAMain EnumkeyUpdate.
04-15-2005,10:22:53 : Executing RAMain EnumkeyUpdate.
04-15-2005,10:22:53 : Executing CA PrepIDR with target IDR_PrepIDR.
04-15-2005,10:22:53 : Executing IDR_SetRegKeys.
04-15-2005,10:22:53 : Executing IDR_StreamMyCDSetup.
04-15-2005,10:22:56 : Executing CA PrepAutoLdr with target AutoLdr_PrepAutoLdr.
04-15-2005,10:22:56 : Executing NetCHGR_AddToServiceGroup.
04-15-2005,10:22:56 : Executing VSD_InstallVSDTable.
04-15-2005,10:23:13 : Executing CHGR_CopySCSIDriver.
04-15-2005,10:23:19 : Executing CHGR_CopyOEMSetup.
04-15-2005,10:23:22 : Executing CHGR_SaveInstallInfo.
04-15-2005,10:23:22 : Executing CA PrepMSExch with target MSExch_PrepMSExch.
04-15-2005,10:23:22 : Executing MSExch_SetRegKeys.
04-15-2005,10:23:22 : Executing CA PrepMSSQL with target MSSQL_PrepMSSQL.
04-15-2005,10:23:22 : Executing MSSQL_SetRegKeys.
04-15-2005,10:23:23 : Executing IsSBS()
04-15-2005,10:23:24 : Small Business Server Edition (Premium)
04-15-2005,10:23:24 : Executing ConfigureSBSServer()
04-15-2005,10:23:24 : Executing GetSBSServerVersion()
04-15-2005,10:23:24 : Executing IsIE5()
04-15-2005,10:23:24 : Executing SBS_UpdateBackupKey()
04-15-2005,10:23:24 : Executing SetSBSLinkOnReg()
04-15-2005,10:23:24 : Configure SBS Server successfully.
04-15-2005,10:26:20 : Executing SetMSMInstallDir
04-15-2005,10:26:20 : Executing SetBewsaTargetProperty.
04-15-2005,10:26:20 : BEWSATARGET.52386FC2_5A96_4505_896E_E5A5D41757DC
04-15-2005,10:31:45 : Executing StopBEServices_MSI.
04-15-2005,10:31:45 : Stopping BE services.
04-15-2005,10:33:48 : Executing StopBEServices_MSI.
04-15-2005,10:33:48 : Rolling back stop of BE services.

David_Slamowitz
Level 4
It did not work! The NT folder still has the DLL files from 2003. SP2 was not installed. Any more suggestions? David

Amruta_Purandar
Level 6
Hello,

Please locate the Bkupinst.log
in this log, please search for the error "return value 3" and send us that error message which will help us to further troubleshoot the issue.

NOTE: If we do not receive your intimation within two business days, this post would be assumed answered and archived

David_Slamowitz
Level 4
There is no error like that in the log. Here is the full log entry generated during the install:

04-19-2005,16:00:36 : Executing CheckPatchDependencies_MSI.
04-19-2005,16:00:36 : Executing CheckPatchDependencies.
04-19-2005,16:00:36 : Executing GetProductGuid.
04-19-2005,16:00:36 : Executing GetInstalledPatches.
04-19-2005,16:00:36 : Executing GetDependentPatches.
04-19-2005,16:00:36 : Executing CheckForDependencies.
04-19-2005,16:00:36 : All dependencies have been met for this patch.
04-19-2005,16:00:36 : Checking to see if the user has administrator privileges.
04-19-2005,16:00:36 : Checking to see if the Backup Exec UI is running.
04-19-2005,16:00:36 : Executing SetCustomActionData_MSI.
04-19-2005,16:00:36 : Executing DLO_PrepPatch to verify DLO database for patching.
04-19-2005,16:00:36 : There is no BE_DLO.mdf file to check DB version against. Patch process will be able to install updated file IF needed.
04-19-2005,16:00:36 : Executing ECM_PrepECM.
04-19-2005,16:00:36 : Executing CreateECMRegistryKeys.
04-19-2005,16:00:36 : Executing SetWBTVersion_MSI
04-19-2005,16:00:36 : Executing AddECMRemoveFiles.
04-19-2005,16:00:37 : Executing CA PrepBEMain with target BEMain_PrepBEMain.
04-19-2005,16:00:37 : Executing CopySAPR3MediaToAgentsDir
04-19-2005,16:00:37 : Executing SetRegKeys.
04-19-2005,16:00:37 : Executing MakeBEDBBakFile.
04-19-2005,16:00:37 : Executing CA PrepRAMain with target RAMain_PrepRAMain.
04-19-2005,16:00:37 : Executing CopyRAWS32Media
04-19-2005,16:00:37 : Executing CopyRAWS64Media
04-19-2005,16:00:37 : Executing SetRAMainRegKeys.
04-19-2005,16:00:38 : Executing RAMain EnumkeyUpdate.
04-19-2005,16:00:38 : Executing RAMain EnumkeyUpdate.
04-19-2005,16:00:38 : Executing CA PrepIDR with target IDR_PrepIDR.
04-19-2005,16:00:38 : Executing IDR_SetRegKeys.
04-19-2005,16:00:38 : Executing IDR_StreamMyCDSetup.
04-19-2005,16:00:38 : Executing CA PrepAutoLdr with target AutoLdr_PrepAutoLdr.
04-19-2005,16:00:38 : Executing NetCHGR_AddToServiceGroup.
04-19-2005,16:00:38 : Executing VSD_InstallVSDTable.
04-19-2005,16:00:40 : Executing CHGR_CopySCSIDriver.
04-19-2005,16:00:41 : Executing CHGR_CopyOEMSetup.
04-19-2005,16:00:41 : Executing CHGR_SaveInstallInfo.
04-19-2005,16:00:41 : Executing CA PrepMSExch with target MSExch_PrepMSExch.
04-19-2005,16:00:41 : Executing MSExch_SetRegKeys.
04-19-2005,16:00:41 : Executing CA PrepMSSQL with target MSSQL_PrepMSSQL.
04-19-2005,16:00:41 : Executing MSSQL_SetRegKeys.
04-19-2005,16:00:42 : Executing IsSBS()
04-19-2005,16:00:42 : Small Business Server Edition (Premium)
04-19-2005,16:00:42 : Executing ConfigureSBSServer()
04-19-2005,16:00:42 : Executing GetSBSServerVersion()
04-19-2005,16:00:42 : Executing IsIE5()
04-19-2005,16:00:42 : Executing SBS_UpdateBackupKey()
04-19-2005,16:00:42 : Executing SetSBSLinkOnReg()
04-19-2005,16:00:42 : Configure SBS Server successfully.
04-19-2005,16:00:53 : Executing SetMSMInstallDir
04-19-2005,16:00:53 : Executing SetBewsaTargetProperty.
04-19-2005,16:00:53 : BEWSATARGET.52386FC2_5A96_4505_896E_E5A5D41757DC
04-19-2005,16:01:55 : Executing StopBEServices_MSI.
04-19-2005,16:01:55 : Stopping BE services.
04-19-2005,16:03:03 : Copying symbol files.
04-19-2005,16:03:03 : Unable to copy symbol files.
04-19-2005,16:03:07 : Executing InstallBEServices_MSI.
04-19-2005,16:03:07 : Installing BE services.
04-19-2005,16:03:07 : Executing InstallBEDB_MSI.
04-19-2005,16:03:07 : Installing BE database.
04-19-2005,16:03:07 : Executing BE_AttachDB.
04-19-2005,16:03:07 : Executing Attach_BEDB.
04-19-2005,16:03:11 : SQL Server running.
04-19-2005,16:03:11 : DRIVER={SQL Server};SERVER=SWC-PDC\BKUPEXEC;Trusted_Connection=Yes
04-19-2005,16:03:13 : Connected to SQL Server.
04-19-2005,16:03:13 : A previous BEDB database was found. Detaching current BEDB database now.
04-19-2005,16:03:14 : The original BEDB database was detached. The new BEDB database will now be attached.
04-19-2005,16:03:14 : Attaching BEDB to SQL Server.
04-19-2005,16:03:14 : EXEC sp_attach_db 'BEDB',@filename1 = N'C:\Program Files\VERITAS\Backup Exec\NT\Data\BEDB_Dat.mdf', @filename2 = N'C:\Program Files\VERITAS\Backup Exec\NT\Data\BEDB_Log.ldf'
04-19-2005,16:03:15 : BEDB has been succesfully attached to SQL Server.
04-19-2005,16:03:15 : Executing BE_SetSQLMaxMemory.
04-19-2005,16:03:15 : Executing SetSQLMaxMemory.
04-19-2005,16:03:15 : SQL Server running.
04-19-2005,16:03:15 : DRIVER={SQL Server};SERVER=SWC-PDC\BKUPEXEC;Trusted_Connection=Yes
04-19-2005,16:03:19 : Connected to SQL Server.
04-19-2005,16:03:19 : Setting SQL server max memory to 255 MB
04-19-2005,16:03:20 : SQL Server max memory has been set.
04-19-2005,16:03:20 : Executing BackupDBFiles_MSI.
04-19-2005,16:03:20 : Executing BE_BackupDBFiles.
04-19-2005,16:03:20 : SQL Server running.
04-19-2005,16:03:20 : DRIVER={SQL Server};SERVER=SWC-PDC\BKUPEXEC;Trusted_Connection=Yes
04-19-2005,16:03:20 : Connected to SQL Server.
04-19-2005,16:03:26 : SQL Server stopped
04-19-2005,16:05:28 : SQL Server started
04-19-2005,16:05:28 : Executing CA ConfigBEMain with target BEMain_ConfigBEMain.
04-19-2005,16:05:28 : Executing RegCOMServers.
04-19-2005,16:05:29 : BERegisterDll called for C:\PROGRA~1\VERITAS\BACKUP~1\NT\ipvlapi.dll
04-19-2005,16:05:29 : BERegisterDll: loaded C:\PROGRA~1\VERITAS\BACKUP~1\NT\ipvlapi.dll
04-19-2005,16:05:29 : Getting ProcAddress for DllRegisterServer.
04-19-2005,16:05:29 : BERegisterDll: Successfully called the registration function.
04-19-2005,16:05:29 : BERegisterDll called for C:\PROGRA~1\VERITAS\BACKUP~1\NT\becatdrv.dll
04-19-2005,16:05:29 : BERegisterDll: loaded C:\PROGRA~1\VERITAS\BACKUP~1\NT\becatdrv.dll
04-19-2005,16:05:29 : Getting ProcAddress for DllRegisterServer.
04-19-2005,16:05:29 : BERegisterDll: Successfully called the registration function.
04-19-2005,16:05:29 : BERegisterDll called for C:\Program Files\Common Files\SYSTEM\Ole DB\sqlxmlx.dll
04-19-2005,16:05:29 : BERegisterDll: loaded C:\Program Files\Common Files\SYSTEM\Ole DB\sqlxmlx.dll
04-19-2005,16:05:29 : Getting ProcAddress for DllRegisterServer.
04-19-2005,16:05:29 : BERegisterDll: Successfully called the registration function.
04-19-2005,16:05:29 : BERegisterDll called for C:\Program Files\Common Files\SYSTEM\Ole DB\sqloledb.dll
04-19-2005,16:05:29 : BERegisterDll: loaded C:\Program Files\Common Files\SYSTEM\Ole DB\sqloledb.dll
04-19-2005,16:05:29 : Getting ProcAddress for DllRegisterServer.
04-19-2005,16:05:29 : BERegisterDll: Successfully called the registration function.
04-19-2005,16:05:29 : BERegisterDll called for C:\Program Files\Common Files\SYSTEM\Ole DB\oledb32.dll
04-19-2005,16:05:29 : BERegisterDll: loaded C:\Program Files\Common Files\SYSTEM\Ole DB\oledb32.dll
04-19-2005,16:05:29 : Getting ProcAddress for DllRegisterServer.
04-19-2005,16:05:29 : BERegisterDll: Successfully called the registration function.
04-19-2005,16:05:29 : Executing AddBackupOperatorSecurityRights.
04-19-2005,16:05:29 : Executing AddBackupOperatorSecurity.
04-19-2005,16:05:30 : Executing BE_PerfSetup.
04-19-2005,16:05:30 : C:\PROGRA~1\VERITAS\BACKUP~1\NT\BEPerfSetup.exe -Refresh C:\WINDOWS\system32
04-19-2005,16:05:31 : Executing CA ConfigRAMain with target RAMain_ConfigRAMain.
04-19-2005,16:05:31 : Executing RAMain RegisterDlls.
04-19-2005,16:05:31 : BERegisterDll called for C:\PROGRA~1\VERITAS\BACKUP~1\NT\storex.ocx
04-19-2005,16:05:31 : BERegisterDll: loaded C:\PROGRA~1\VERITAS\BACKUP~1\NT\storex.ocx
04-19-2005,16:05:31 : Getting ProcAddress for DllRegisterServer.
04-19-2005,16:05:31 : BERegisterDll: Successfully called the registration function.
04-19-2005,16:05:31 : BERegisterDll called for C:\PROGRA~1\VERITAS\BACKUP~1\NT\schedu.dll
04-19-2005,16:05:31 : BERegisterDll: loaded C:\PROGRA~1\VERITAS\BACKUP~1\NT\schedu.dll
04-19-2005,16:05:31 : Getting ProcAddress for DllRegisterServer.
04-19-2005,16:05:32 : BERegisterDll: Successfully called the registration function.
04-19-2005,16:05:32 : BERegisterDll called for C:\PROGRA~1\VERITAS\BACKUP~1\NT\scheduiur.dll
04-19-2005,16:05:32 : BERegisterDll: loaded C:\PROGRA~1\VERITAS\BACKUP~1\NT\scheduiur.dll
04-19-2005,16:05:32 : Getting ProcAddress for DllRegisterServer.
04-19-2005,16:05:32 : BERegisterDll: Successfully called the registration function.
04-19-2005,16:05:32 : BERegisterDll called for C:\PROGRA~1\VERITAS\BACKUP~1\NT\schedmgrur.dll
04-19-2005,16:05:32 : BERegisterDll: loaded C:\PROGRA~1\VERITAS\BACKUP~1\NT\schedmgrur.dll
04-19-2005,16:05:32 : Getting ProcAddress for DllRegisterServer.
04-19-2005,16:05:32 : BERegisterDll: Successfully called the registration function.
04-19-2005,16:05:32 : BERegisterDll called for C:\PROGRA~1\VERITAS\BACKUP~1\NT\NotificationUI300U.dll
04-19-2005,16:05:32 : BERegisterDll: loaded C:\PROGRA~1\VERITAS\BACKUP~1\NT\NotificationUI300U.dll
04-19-2005,16:05:32 : Getting ProcAddress for DllRegisterServer.
04-19-2005,16:05:32 : BERegisterDll: Successfully called the registration function.
04-19-2005,16:05:32 : BERegisterDll called for C:\PROGRA~1\VERITAS\BACKUP~1\NT\RecipientUI300U.dll
04-19-2005,16:05:32 : BERegisterDll: loaded C:\PROGRA~1\VERITAS\BACKUP~1\NT\RecipientUI300U.dll
04-19-2005,16:05:32 : Getting ProcAddress for DllRegisterServer.
04-19-2005,16:05:32 : BERegisterDll: Successfully called the registration function.
04-19-2005,16:05:38 : BERegisterDll called for C:\PROGRA~1\VERITAS\BACKUP~1\NT\exportmodeller.dll
04-19-2005,16:05:38 : BERegisterDll: loaded C:\PROGRA~1\VERITAS\BACKUP~1\NT\exportmodeller.dll
04-19-2005,16:05:38 : Getting ProcAddress for DllRegisterServer.
04-19-2005,16:05:39 : BERegisterDll: Successfully called the registration function.
04-19-2005,16:05:39 : BERegisterDll called for C:\PROGRA~1\VERITAS\BACKUP~1\NT\crtslv.dll
04-19-2005,16:05:39 : BERegisterDll: loaded C:\PROGRA~1\VERITAS\BACKUP~1\NT\crtslv.dll
04-19-2005,16:05:39 : Getting ProcAddress for DllRegisterServer.
04-19-2005,16:05:39 : BERegisterDll: Successfully called the registration function.
04-19-2005,16:05:39 : Executing RAMain SetReportFilesToReadOnly.
04-19-2005,16:05:39 : Executing CopyBELogoBmps.
04-19-2005,16:05:39 : Executing CA ConfigIDR with target IDR_ConfigIDR.
04-19-2005,16:05:39 : Executing IDR_LaunchMyCD.
04-19-2005,16:05:39 : C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp\{201E698C-B88E-41AE-8C46-3BBACADCD6E7}\\setup.exe -NOREBOOT
04-19-2005,16:05:40 : Executing ECM_ConfigECM.
04-19-2005,16:05:40 : Executing WriteToEISListFile
04-19-2005,16:05:40 : Executing LaunchTapeinst_MSI.
04-19-2005,16:05:44 : Executing CA ConfigAutoLdr with target AutoLdr_ConfigAutoLdr.
04-19-2005,16:05:44 : Executing VSD_InstallDrivers.
04-19-2005,16:05:44 : C:\Program Files\VERITAS\Backup Exec\NT\loader
04-19-2005,16:05:44 : Executing SetupAutoloader.
04-19-2005,16:05:44 : Failed to create SCSIChanger service.
04-19-2005,16:05:44 : Executing StartAutoldrDrivers.
04-19-2005,16:05:44 : C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp\{201E698C-B88E-41AE-8C46-3BBACADCD6E7}\\startchgdrv.dll
04-19-2005,16:05:44 : Executing DisableDLOSvc_MSI.
04-19-2005,16:05:44 : DLO option has been disabled. Removing DLO service and DLOAgent share.
04-19-2005,16:05:44 : WARNING: Unable to remove DLOAgent share.
04-19-2005,16:05:44 : WARNING: Unable to remove service DLOAdminSvcu. The service does not exist.
04-19-2005,16:05:44 : Executing migration of data from 9.x
04-19-2005,16:05:44 : Loaded C:\Program Files\VERITAS\Backup Exec\NT\bemigl.dll
04-19-2005,16:05:44 : Got the proc address for MG_NonUiInit
04-19-2005,16:05:44 : Got the proc address for MG_Start
04-19-2005,16:05:44 : In BeMigl MG_Init
04-19-2005,16:05:44 : In BeMigl Init
04-19-2005,16:05:44 : Got Module handle for bemigl.dll
04-19-2005,16:05:44 : Xml File name:
04-19-2005,16:05:44 : C:\Program Files\VERITAS\Backup Exec\NT\migconfig.xml
04-19-2005,16:05:44 : Number of libraries to load 3
04-19-2005,16:05:44 : Adding C:\Program Files\VERITAS\Backup Exec\NT\pvlupgrade.dll to the library list
04-19-2005,16:05:44 : Adding C:\Program Files\VERITAS\Backup Exec\NT\jobmigration.dll to the library list
04-19-2005,16:05:44 : Adding C:\Program Files\VERITAS\Backup Exec\NT\catupgrade.dll to the library list
04-19-2005,16:05:44 : exiting ReadXMLFile
04-19-2005,16:05:44 : In setpercentcomplete no pMigUI returning.
04-19-2005,16:05:44 : Migration running in silent mode
04-19-2005,16:05:44 : Initializing migration library 0
04-19-2005,16:05:44 : Assigning function pointers.
04-19-2005,16:07:02 : Failure 3 initializing migration library 0
04-19-2005,16:07:02 : lp_MG_NoUiInit failed with error 3
04-19-2005,16:07:09 : Executing StopBEServices_MSI.
04-19-2005,16:07:09 : Rolling back stop of BE services.

Sharvari_Deshmu
Level 6
Hello,

To resolve the issue please please go to the "migconfig" file under "Drive:\program files\Veritas\BE\NT\"

The current file should look like this:


-
-
VERITAS
Backup Exec
VERITAS Backup Exec For Windows Servers
3
pvlupgrade.dll
jobmigration.dll
catupgrade.dll




Please Delete pvlupgrade.dll line from the above file.

The final file looks something like this:


-
-
VERITAS
Backup Exec
VERITAS Backup Exec For Windows Servers
2 ....3 changed to 2
jobmigration.dll ... 2 changed to 1
catupgrade.dll ... 3 changed to 2




After this please try installing SP2 and then observe the result.


Thanks,
NOTE : If we do not receive your intimation within two business days, this post would be marked 'assumed answered' and would be moved to 'answered questions' pool.Message was edited by:
sharvari

David_Slamowitz
Level 4
Didn't work. Different error now. Here is bkupinst.log excerpt:

05-04-2005,15:26:43 : Executing migration of data from 9.x
05-04-2005,15:26:44 : Loaded C:\Program Files\VERITAS\Backup Exec\NT\bemigl.dll
05-04-2005,15:26:44 : Got the proc address for MG_NonUiInit
05-04-2005,15:26:44 : Got the proc address for MG_Start
05-04-2005,15:26:44 : In BeMigl MG_Init
05-04-2005,15:26:44 : In BeMigl Init
05-04-2005,15:26:44 : Got Module handle for bemigl.dll
05-04-2005,15:26:44 : Xml File name:
05-04-2005,15:26:44 : C:\Program Files\VERITAS\Backup Exec\NT\migconfig.xml
05-04-2005,15:26:44 : Number of libraries to load 2
05-04-2005,15:26:44 : Adding C:\Program Files\VERITAS\Backup Exec\NT\jobmigration.dll to the library list
05-04-2005,15:26:44 : Adding C:\Program Files\VERITAS\Backup Exec\NT\catupgrade.dll to the library list
05-04-2005,15:26:44 : exiting ReadXMLFile
05-04-2005,15:26:44 : In setpercentcomplete no pMigUI returning.
05-04-2005,15:26:44 : Migration running in silent mode
05-04-2005,15:26:44 : Initializing migration library 0
05-04-2005,15:26:44 : Assigning function pointers.
05-04-2005,15:27:03 : Failed to connect to Database.
05-04-2005,15:27:03 : Failed to connect to Database - connection string parameter SWC-PDC\BkupExec, BEDB, 30
05-04-2005,15:27:03 : Failure -1 initializing migration library 0
05-04-2005,15:27:04 : lp_MG_NoUiInit failed with error -1
05-04-2005,15:27:09 : Executing StopBEServices_MSI.
05-04-2005,15:27:09 : Rolling back stop of BE services.

Here is a copy of the new migconfig file:




VERITAS
Backup Exec
VERITAS Backup Exec For Windows Servers
2
jobmigration.dll
catupgrade.dll



what next?

Renuka_-
Level 6
Employee
Hello,





The error will occur if the "Upgrade" key is set to 1 in the following location in the registry on the media server:


HKEY_LOCAL_MACHINE\SOFTWARE\VERITAS\Backup Exec\Install


If the value is set to 1 for the upgrade key, the installation will fail because it is trying to perform an upgrade operation. Changing the value to 5 will allow Backup Exec to install normally.




NOTE : If we do not receive your intimation within two business days, this post would be marked assumed answered and would be moved to the ‘answered threads’ pool.

David_Slamowitz
Level 4
There is no "upgrade" key in the registry only an "upgrade version" key. Here is what the registry location looks like:

Key Name: HKEY_LOCAL_MACHINE\SOFTWARE\VERITAS\Backup Exec\Install
Class Name:
Last Write Time: 5/4/2005 - 3:26 PM
Value 0
Name: Working Product Code
Type: REG_SZ
Data: {201E698C-B88E-41AE-8C46-3BBACADCD6E7}

Value 1
Name: Support Path
Type: REG_SZ
Data: C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp\{201E698C-B88E-41AE-8C46-3BBACADCD6E7}\

Value 2
Name: MSDE Installed
Type: REG_DWORD
Data: 0x1

Value 3
Name: Path 9.0
Type: REG_SZ
Data: C:\Program Files\VERITAS\Backup Exec\NT\

Value 4
Name: Source Path 9.0
Type: REG_SZ
Data: C:\Users Shared Folders\shared\programs\Server software\Backup Exec\Backup Exec revision 4691.1\WINNT\INSTALL\BE\

Value 5
Name: Language
Type: REG_SZ
Data: 0

Value 6
Name: Product Code 9.0
Type: REG_SZ
Data: {201E698C-B88E-41AE-8C46-3BBACADCD6E7}

Value 7
Name: Install Language
Type: REG_DWORD
Data: 0x409

Value 8
Name: Major Version
Type: REG_DWORD
Data: 0x9

Value 9
Name: Minor Version
Type: REG_DWORD
Data: 0x1

Value 10
Name: Build Major
Type: REG_DWORD
Data: 0x1253

Value 11
Name: Build Minor
Type: REG_DWORD
Data: 0

Value 12
Name: Reboot Install
Type: REG_DWORD
Data: 0

Value 13
Name: Upgrade Version
Type: REG_SZ
Data: 9.1.4691


Key Name: HKEY_LOCAL_MACHINE\SOFTWARE\VERITAS\Backup Exec\Install\INF File
Class Name:
Last Write Time: 5/4/2005 - 3:26 PM
Value 0
Name: INF FILE
Type: REG_SZ
Data: C:\WINDOWS\system32\drivers\oemtap0.inf


Key Name: HKEY_LOCAL_MACHINE\SOFTWARE\VERITAS\Backup Exec\Install\Online Registration
Class Name:
Last Write Time: 5/4/2005 - 3:26 PM
Value 0
Name: Registered OnLine
Type: REG_DWORD
Data: 0

Sharvari_Deshmu
Level 6
Hello,

Please try putting the Backup services in start type manual and then please try doing a repair install with the help of the technote below:
http://support.veritas.com/docs/253199

After this please try installing SP2.

Thanks,

NOTE : If we do not receive your reply within two business days, this post would be marked ‘assumed answered’ and would be moved to ‘answered questions’ pool.

David_Slamowitz
Level 4
Didn't work. I set all backup services as start up type manual. Then successfully did a repair. Reboted and tried to reinstall SP2. The same error occurred. In addition, the registry does not have an 'upgrade' key now. Only an 'upgrade version' key. Here is the bkupinst.log file excerpt and registry currently. Any more ideas?

bkupinst.log file:
05-11-2005,22:36:53 : C:\Program Files\VERITAS\Backup Exec\NT\migconfig.xml
05-11-2005,22:36:53 : Number of libraries to load 2
05-11-2005,22:36:53 : Adding C:\Program Files\VERITAS\Backup Exec\NT\jobmigration.dll to the library list
05-11-2005,22:36:53 : Adding C:\Program Files\VERITAS\Backup Exec\NT\catupgrade.dll to the library list
05-11-2005,22:36:53 : exiting ReadXMLFile
05-11-2005,22:36:53 : In setpercentcomplete no pMigUI returning.
05-11-2005,22:36:53 : Migration running in silent mode
05-11-2005,22:36:53 : Initializing migration library 0
05-11-2005,22:36:53 : Assigning function pointers.
05-11-2005,22:37:10 : Failed to connect to Database.
05-11-2005,22:37:10 : Failed to connect to Database - connection string parameter SWC-PDC\BkupExec, BEDB, 30
05-11-2005,22:37:10 : Failure -1 initializing migration library 0
05-11-2005,22:37:10 : lp_MG_NoUiInit failed with error -1
05-11-2005,22:37:16 : Executing StopBEServices_MSI.
05-11-2005,22:37:16 : Rolling back stop of BE services.

Registry:
Key Name: HKEY_LOCAL_MACHINE\SOFTWARE\VERITAS\Backup Exec\Install
Class Name:
Last Write Time: 5/11/2005 - 10:36 PM
Value 0
Name: Working Product Code
Type: REG_SZ
Data: {201E698C-B88E-41AE-8C46-3BBACADCD6E7}

Value 1
Name: Support Path
Type: REG_SZ
Data: C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp\{201E698C-B88E-41AE-8C46-3BBACADCD6E7}\

Value 2
Name: MSDE Installed
Type: REG_DWORD
Data: 0x1

Value 3
Name: Path 9.0
Type: REG_SZ
Data: C:\Program Files\VERITAS\Backup Exec\NT\

Value 4
Name: Source Path 9.0
Type: REG_SZ
Data: C:\Users Shared Folders\shared\programs\Server software\Backup Exec\Backup Exec revision 4691.1\WINNT\INSTALL\BE\

Value 5
Name: Language
Type: REG_SZ
Data: 0

Value 6
Name: Product Code 9.0
Type: REG_SZ
Data: {201E698C-B88E-41AE-8C46-3BBACADCD6E7}

Value 7
Name: Install Language
Type: REG_DWORD
Data: 0x409

Value 8
Name: Major Version
Type: REG_DWORD
Data: 0x9

Value 9
Name: Minor Version
Type: REG_DWORD
Data: 0x1

Value 10
Name: Build Major
Type: REG_DWORD
Data: 0x1253

Value 11
Name: Build Minor
Type: REG_DWORD
Data: 0

Value 12
Name: Reboot Install
Type: REG_DWORD
Data: 0

Value 13
Name: Upgrade Version
Type: REG_SZ
Data: 9.1.4691


Key Name: HKEY_LOCAL_MACHINE\SOFTWARE\VERITAS\Backup Exec\Install\INF File
Class Name:
Last Write Time: 5/11/2005 - 10:36 PM
Value 0
Name: INF FILE
Type: REG_SZ
Data: C:\WINDOWS\system32\drivers\oemtap0.inf


Key Name: HKEY_LOCAL_MACHINE\SOFTWARE\VERITAS\Backup Exec\Install\Online Registration
Class Name:
Last Write Time: 5/11/2005 - 10:36 PM
Value 0
Name: Registered OnLine
Type: REG_DWORD
Data: 0

Amruta_Purandar
Level 6
Hello,

Please reboot the server after installation of SP2. If that does not help, repair Backup Exec installation. Refer the following technote.

Title:
Repairing Backup Exec 9.x and 10.x for Windows Servers
http://support.veritas.com/docs/253199

Then try reinstalling the SP.

NOTE : If we do not receive your reply within two business days, this post would be marked ‘assumed answered’ and would be moved to ‘answered questions’ pool.