Unable to connect to a remote SQL Express installation for use with the Backup Exec for Windows Server database (BEDB).
Cannot connect to Microsoft SQL Server 'SERVERNAME'.
Backup Exec Version 10.x uses the Microsoft Desktop Engine (MSDE) to connect to BEDB database.
Backup Exec 11.x and above uses Microsoft SQL Express to connect to BEDB database, and supports use of SQL Express instance installed on a Local as well as remote server .
When opting to use a current SQL Express installation be aware that a default installation of SQL Express is not properly configured for use with a remote installation of Backup Exec 11.d for Windows Servers. This is because a default installation of SQL Express does not enable the ability to communicate with database applications on remote systems; the networking components must still be enabled.
When attempting to connect to a remote SQL Express instance, if remote connections are not allowed the error in Figure 1 will be displayed.
To enable networking components in SQL Express
- Click Start Run and type cliconfg and click OK
- Under General tab from Disabled protocols, select Named Pipes and TCP/IP and click Enable>> and click OK. (Figure 4)
The SQL Express installation is now ready to accept Backup Exec for Windows Servers 11d during installation on a server remote to the SQL Express server.
Selecting the remote SQL Express instance during Backup Exec installation
- During installation, when given the opportunity to select the remote server running SQL Express, the server name only may be displayed in the selection list.
- If the server running SQL Express is rebooted after enabling remote TCPIP connections, and the SQL Server Browser service is set to start automatically, then the installation routine will display the format of SERVER_A\SQLEXPRESS.
- In most cases, a reboot is not necessary. The server name can be appended manually by adding the (\) backslash followed by the instance name (SQLEXPRESS).