Error "V-225-229: Unable to connect to SQL Server" occurs during the installation of Backup Exec for Windows Servers

Article:TECH59962  |  Created: 2008-01-28  |  Updated: 2013-02-19  |  Article URL http://www.symantec.com/docs/TECH59962
Article Type
Technical Solution

Product(s)

Subject

Issue



Error "V-225-229: Unable to connect to SQL Server" occurs during the installation of Backup Exec for Windows Servers


Error



V-225-229: Unable to connect to SQL Server


Cause



This error is generated when installing Backup Exec to an existing instance of Microsoft SQL.

The error may occur if Backup Exec is unable to connect to the SQL instance that was specified during the installation.


Solution



Perform the following troubleshooting:
 
  1. If "LOCAL" SQL variable was used during Backup Exec installation change if from LOCAL to the Server Name (TECH202939).
  2. Test connectivity to the SQL instance's MASTER database from the Backup Exec media server using a .UDL file and verify if it is successful. For more information refer to the TECH24708 in the Related Documents section.
  3. Make sure that the instance name is provided correctly during the installation.
  4. Ensure that the SQL server data directory can be accessed from the Backup Exec media server.
  5. If the above steps do not resolve the issue, as a workaround install Backup Exec using a local instance and (only if it is needed) use the Beutility to move the BE database to the required instance. See the Related Documents section for additional information.

 


Supplemental Materials

SourceUMI
ValueV-225-229
Description

Unable to connect to the SQL Server


SourceUMI
ValueV-225-204
Description

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



Legacy ID



303327


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


Terms of use for this information are found in Legal Notices