Patch installation or repair operations fail when (LOCAL) variable was used for custom DEFAULT SQL Server instance during initial Backup Exec install.

Article:TECH202939  |  Created: 2013-02-19  |  Updated: 2013-02-20  |  Article URL http://www.symantec.com/docs/TECH202939
Article Type
Technical Solution

Product(s)

Issue



Patch installation or repair operations fail when (LOCAL) variable was used for custom DEFAULT SQL Server instance during initial Backup Exec install.

 

During the Backup Exec installation (LOCAL) was used for the SQL instance for the Backup Exec Database (Figure 1).

 

Figure 1

 

 


Error



Example errors reported in the Backup Exec installation log:


SQLBrowser failed to start. Connection requests to SQL server (local) might fail.
Error returned from OpenSCManager: 1722

V-225-204: Could not start the SQL server (local) with service name of MSSQLSERVER ***To search for information about this error, click here

V-225-215: Unable to connect to SQL Server. ***To search for information about this error, click here
Failed to set Audit Table info for this patch ({05819B14-D0B2-4474-BD25-8AEA2951FE36}).

SQLBrowser service is not running. Starting service.
SQLBrowser failed to start. Connection requests to SQL server (local) might fail.
Error returned from OpenSCManager: 1722
V-225-204: Could not start the SQL server (local) with service name of MSSQLSERVER ***To search for information about this error, click here


V-225-210: Unable to connect to SQL Server (local). ***To search for information about this error, click here ERROR: BEMSI;BEOps.dll;BEOperations.cpp;BE_AttachDB() - Unable to connect to SQL Server (local).;1722V-225-118: Error installing BEDB ***To search for information about this error, click here.

 


 


Environment



Backup Exec 11.0
Backup Exec 12.0
Backup Exec 12.5
Backup Exec 2010
Backup Exec 2012

 

  


Cause



A repair install or patch application may fail in BE_AttachDB when using (LOCAL) SQL variable.

 

Symantec does not recommend using the (LOCAL) SQL variable for installations. Symantec does recommend using the machinename\instance name for custom SQL Server instances.

 


 

 


Solution



1) In the C:\ProgramData\Symantec\Backup Exec\<GUID>\BEInstParams.prm" file locate the line which references the "/DBSERVER:(LOCAL)" and change it to be "/DBSERVER:Machine_name" where "Machine_Name" is the name of your machine (Figure 2)(Figure 3).

For Windows 2003 servers the path to BEInstParams.prm is C:\Documents and Settings\All Users\Application data\Symantec\Backup Exec\<GUID>\BEInstParams.prm".

 

<GUID> represents the Backup Exec Versions listed below:

 

Backup Exec 64 Bit Installation GUIDs

{017CF375-DCCC-4717-B3A2-F549CE54BDE5} BE v14.0.1798
{06B4D29D-D713-4EF3-B399-C4346FB84FF3} BE v13.0.5204
{DD8FD4D3-F0FB-4FB2-8A34-25E2C7756A51} BE v13.0.4164
{BA106948-54B3-4A3F-9B12-98602AABFD43} BE v13.0.2896
{BE61998B-E5BD-4E41-B2D7-96551E6FECE0} BE v12.5.2213
{C6A657A8-2BC8-411D-BDC2-641D752AF46A} BE v12.0.1364
{E00C3233-E12F-428C-9BAE-997D44408CBE} BE v11.0.7170
{ACE16FD9-EB87-42F4-9CB5-6FA8C820C9CD} BE v11.0.6235

Backup Exec 32 Bit Installation GUIDs

{0CDBECFA-4D7E-41FD-932D-24F7F3E1062F} BE v14.0.1798
{0B6FCC43-E46E-49EE-AADB-2DB3C8164E5D} BE v13.0.5204
{DE93FB03-3314-4E2E-8F45-E9BD776C1D25} BE v13.0.4164
{BE576FF1-DC46-4572-A110-3D0ACA97EC3D} BE v13.0.2896
{B52AF7AF-C5B3-47FC-8116-AD2208FC8904} BE v12.5.2213
{CA648C72-66AB-4652-A825-9994AB5F6D15} BE v12.0.1364
{EAB0C0F9-B57B-4865-91A3-DE3B34B1FB02} BE v11.0.7170     
{BEA465C8-2923-42C6-9141-BE44739A6A80} BE v11.0.6235
 

 

Figure 2


Figure 3

  
2) In the following registry locations, change their value from (LOCAL) to the local machine name (Figure 4)(Figure 5).

 

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.

 

 

"HKLM\Software\Symantec\Backup Exec for Windows\ADAMM\Database Server Name"
"HKLM\Software\Symantec\Backup Exec for Windows\BEDatabase\Server Database Server Name"
"HKLM\Software\Symantec\Backup Exec for Windows\BEDatabase\Catalog Database Server Name"


Figure 4

 

Figure 5

 

3)  Re-try the Repair or patch operation.

 

 


Supplemental Materials

ValueV-225-204
Description

Could not start the SQL server (LOCAL) with service name of MSSQLSERVER


SourceUMI
ValueV-225-215
Description

Unable to connect to SQL Server


SourceUMI
ValueV-225-210
Description

***To search for information about this error, click here ERROR: BEMSI;BEOps.dll;BEOperations.cpp;BE_AttachDB() - Unable to connect to SQL Server (local).;1722V-225-118: Error installing BEDB ***To search for information about this error, click here




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


Terms of use for this information are found in Legal Notices