Video Screencast Help
Symantec to Separate Into Two Focused, Industry-Leading Technology Companies. Learn more.

Error 1606

Created: 20 Mar 2008 • Updated: 22 May 2010 | 5 comments
Error 1606. Could not access network location \\\C$\program Files\Symantec\Backup Exec\Data
 
Could not get the DLO option to work.  So I tried uninstalling the option and reinstalling it.  Uninstall went fine but now I receive this error everytime I tried to reinstall it or even try to uninstall BE 12 completely.
 
Any insights???

Comments 5 CommentsJump to latest comment

Vijay S Mishra's picture
Make sure that the SQLSERVER (BKUPEXEC) service is running on Local System account .
JayW's picture
SQL Server (BKUPEXEC) is running under Local System       
 
Is there a manual uninstall procedure for BEWS12?   This install is an upgrade from 11d.
 
 
 
Here are the errors in the bkupinst.htm log        
 
 
 
03-20-2008,11:09:28 : Executing RAMain EnumkeyUpdate.
03-20-2008,11:09:28 : Executing RAMain EnumkeyUpdate.
03-20-2008,11:09:28 : Executing BEMain_PrepDLO.
03-20-2008,11:09:28 : m_bUseNativeClient = 1
03-20-2008,11:09:28 : Setting DLO properties.
03-20-2008,11:09:28 : Failed to get SQL Instance.
03-20-2008,11:09:28 : Failed to get SQL Server.
03-20-2008,11:09:28 : There is no MSSQLSERVER Service  <-- should be SQL Server(BKUPEXEC) right?
03-20-2008,11:09:28 : V-225-221: Unable to connect to SQL Server for DB location. ***To search for information about this error, click here
03-20-2008,11:09:28 : Upgrade from 11.0 DLO Admin service data path: C:\Program Files\Symantec\Backup Exec\DATA.
03-20-2008,11:09:28 : MSI has been configured to copy DLO file DLODBUpgrade20.sql from C:\Program Files\Symantec\Backup Exec\DLO to \\\C$\Program Files\Symantec\Backup Exec\DATA.
03-20-2008,11:09:29 : MSI has been configured to copy DLO file DLODBUpgrade30.sql from C:\Program Files\Symantec\Backup Exec\DLO to \\\C$\Program Files\Symantec\Backup Exec\DATA.
03-20-2008,11:09:29 : MSI has been configured to copy DLO file DLODBUpgrade.sql from C:\Program Files\Symantec\Backup Exec\DLO to \\\C$\Program Files\Symantec\Backup Exec\DATA.
03-20-2008,11:09:30 : MSI has been configured to copy DLO file DLODBUpgradeMoe.sql from C:\Program Files\Symantec\Backup Exec\DLO to \\\C$\Program Files\Symantec\Backup Exec\DATA.
03-20-2008,11:09:30 : MSI has been configured to copy DLO upgrade file RunSQLScript.cmd from C:\Program Files\Symantec\Backup Exec\ to \\\C$\Program Files\Symantec\Backup Exec\DATA.
03-20-2008,11:09:30 : Action 11:09:30: PrepAutoLdr. Initializing Robotic Library install components
03-20-2008,11:09:30 : Executing AutoLdr_PrepAutoLdr. Preparing Auto Loader components.
03-20-2008,11:09:30 : Executing NetCHGR_AddToServiceGroup.
03-20-2008,11:09:30 : Executing VSD_InstallVSDTable.
03-20-2008,11:09:31 : Executing VSD_InstallDrivers.
03-20-2008,11:09:31 : VSD files will be copied from to .
03-20-2008,11:09:31 : Executing CHGR_CopySCSIDriver.
03-20-2008,11:09:32 : Executing CHGR_CopyOEMSetup.
03-20-2008,11:09:33 : Executing CHGR_SaveInstallInfo.
03-20-2008,11:09:33 : Action 11:09:33: PrepTSM. Initializing Tivoli Storage Manager install components
03-20-2008,11:09:33 : __stdcall TSM_PrepTSM
03-20-2008,11:09:33 : Executing SetRegKeys for TSM.
03-20-2008,11:09:33 : Action 11:09:33: PrepMSExch. Initializing Agent for Microsoft Exchange Server install components
03-20-2008,11:09:33 : Executing CA PrepMSExch with target MSExch_PrepMSExch.
03-20-2008,11:09:33 : Executing MSExch_SetRegKeys.
03-20-2008,11:09:33 : Executing RemoveBewsaRegistryKeys.
03-20-2008,11:09:33 : Action ended 11:09:33: PrepInstall. Return value 1.
03-20-2008,11:09:33 : Action 11:09:33: SetDbServerName.FBF6AB5B_373C_4CD4_B277_E08D4D444E2C.
03-20-2008,11:09:33 : Action start 11:09:33: SetDbServerName.FBF6AB5B_373C_4CD4_B277_E08D4D444E2C.
03-20-2008,11:09:33 : Action ended 11:09:33: SetDbServerName.FBF6AB5B_373C_4CD4_B277_E08D4D444E2C. Return value 1.
03-20-2008,11:09:33 : Action 11:09:33: GetSqlServerProcType.FBF6AB5B_373C_4CD4_B277_E08D4D444E2C.
03-20-2008,11:09:33 : Action start 11:09:33: GetSqlServerProcType.FBF6AB5B_373C_4CD4_B277_E08D4D444E2C.
03-20-2008,11:09:33 : [SYMANTEC]: ServerName: LEMANS2
03-20-2008,11:09:33 : [SYMANTEC]: InstanceName:
03-20-2008,11:09:33 : [SYMANTEC]: Server: LEMANS2
03-20-2008,11:09:34 : [SYMANTEC]: SQLStatement: SELECT @@VERSION
03-20-2008,11:09:34 : [SYMANTEC]: Connection string: DRIVER={SQL Server};SERVER=LEMANS2;Trusted_Connection=Yes;DATABASE=master
03-20-2008,11:09:50 : [SYMANTEC]: OpenEx exception: SQL Server does not exist or access denied. ConnectionOpen (Connect()).
03-20-2008,11:09:50 : Action ended 11:09:50: GetSqlServerProcType.FBF6AB5B_373C_4CD4_B277_E08D4D444E2C. Return value 1.
03-20-2008,11:09:50 : Action 11:09:50: FileCost. Computing space requirements
03-20-2008,11:09:51 : Action start 11:09:50: FileCost.
03-20-2008,11:09:51 : Action ended 11:09:51: FileCost. Return value 1.
03-20-2008,11:09:51 : Action 11:09:51: IsolateComponents.
03-20-2008,11:09:51 : Action start 11:09:51: IsolateComponents.
03-20-2008,11:09:51 : Action ended 11:09:51: IsolateComponents. Return value 1.
03-20-2008,11:09:51 : Action 11:09:51: CostFinalize. Computing space requirements
03-20-2008,11:09:51 : Action start 11:09:51: CostFinalize.
03-20-2008,11:09:51 : ERROR: Error 1606.Could not access network location \\\C$\Program Files\Symantec\Backup Exec\DATA.
03-20-2008,11:20:22 : ERROR: Error 1606.Could not access network location \\\C$\Program Files\Symantec\Backup Exec\DATA.
03-20-2008,11:20:23 : ERROR: Error 1606.Could not access network location \\\C$\Program Files\Symantec\Backup Exec\DATA.
03-20-2008,11:20:23 : ERROR: Error 1606.Could not access network location \\\C$\Program Files\Symantec\Backup Exec\DATA.
03-20-2008,11:20:24 : ERROR: Error 1606.Could not access network location \\\C$\Program Files\Symantec\Backup Exec\DATA.
03-20-2008,11:20:24 : ERROR: Error 1606.Could not access network location \\\C$\Program Files\Symantec\Backup Exec\DATA.
03-20-2008,11:20:24 : ERROR: Error 1606.Could not access network location \\\C$\Program Files\Symantec\Backup Exec\DATA.
03-20-2008,11:20:27 : Action ended 11:20:27: CostFinalize. Return value 3.
03-20-2008,11:20:27 : Action ended 11:20:27: INSTALL. Return value 3.
03-20-2008,11:20:27 : Property(S): DiskPrompt = [1]
03-20-2008,11:20:27 : Property(S): Registration = No
03-20-2008,11:20:27 : Property(S): UpgradeCode = {279D4253-B155-4E85-9FB8-F4CC81B5BFB8}
03-20-2008,11:20:27 : Property(S): ConfigInstall = TOKEN-INSTALLDIR:C:\Program Files\Symantec\Backup Exec\ TOKEN-SVCNAME:pmadmin TOKEN-SVCPSWD:±øÔþ íÏÒ TOKEN-SVCDOM:PME TOKEN-BE:1 TOKEN-RA:0 TOKEN-TAPEDEV:1 TOKEN-AUTOLDR:1 TOKEN-IDR:0 TOKEN-VSP:0 TOKEN-TSM:0 TOKEN-SSO:0 TOKEN-DLOSVC:1 TOKEN-DLOCLIENT:1 TOKEN-5USERDLOSVC:0 TOKEN-5USERDLOCLIENT:0 TOKEN-TSMSERVER:xxx.xxx.xxx.xxx TOKEN-TSMPORT:1500 TOKEN-SSOPRIMARY:0 TOKEN-SSODATA: TOKEN-SSOSTATE:0 TOKEN-BEUIMODE:1 TOKEN-ADAMMLOCAL:0 TOKEN-PATCH:1 TOKEN-PATCHCODE: TOKEN-PATCHCATEGORY: TOKEN-8XUPG:0 TOKEN-9XUPG:0 TOKEN-PUSHBE:0 TOKEN-CASO:0 TOKEN-MMS:0
03-20-2008,11:20:27 : Property(S): VersionNT = 502
JayW's picture
I was able to get past this by manually unistalling BEWS12 completely and reinstalling without the DLO option, then doing the repair install to get the email working , and finally installing the DLO option.  It was nice having to recreate all my backup jobs.
 
Still waiting for Symantec to figure out why this is happening.  My case was logged as critical and its been 5 days.
 
Symantec Tech Support IS a JOKE!!!!!!!!!!!!!!!!
RahulM's picture
Please provide me with the case number.