I have SQL 2005 installed on a Windows 2003 server. I have installed Backup
Exec 10d and get an error when trying to backup the SQL database. I can
see/backup the Backup Exec SQL db but when I try to backup the other SQL db
( used for Sharepoint and Insight ) it gives me this error...

An error was encountered while attempting to browse the contents of
<servername>.
A network connection to the server could not be established

Any help would be much appreciated !!

Make sure you have the SQL Server 2005 instance set to allow remote
connections.


--
MeanOldDBA
derrickleggett (AT) hotmail (DOT) com
http://weblogs.sqlteam.com/derrickl

When life gives you a lemon, fire the DBA.


"microsoft" wrote:

i am having the same problem,
i have looked in to this a it seems that Backup Exec 10d can only backup
SQL 2005 remotly !
symantec have not confirmed this i am waiting on a reply from them as we
are symantec partners.

p.s i update in the next 24 hours, hopefuly !


*** Sent via Developersdex http://www.developersdex.com ***

i have spoken to symantec, and they say as long as you install and
configure SQL 2005 before installing 'Backup Exec 10d' and install sp1
for Backup Exec then is should select the instance no problem & backup.

p.s sorry for the wait.

*** Sent via Developersdex http://www.developersdex.com ***

We are experiencing the same problem here
Backup Exec 10d worked with 1 SQL2000 server
When tried to connect to SQL2005 servers (agents installed on the sql
server), it says "A network connection to the server cannot be
established"

We had the SQL2005 installed before installing the Backup Exec SQL
Server agent, and our software has SP1 as well
SQL server allows remote connection too

Any other causes/guesses?



*** Sent via Developersdex http://www.developersdex.com ***

Do you have the correct protocol enabled on the SQL 2005 instance?

I would open up the SQL Server 2005 Configuration Manager and check to see
if TCP/IP (or whatever protocol your backup exec is using) and make sure
they are enabled under --> SQL Server Network Configuration --> Protocols
for MSSQLServer

see if that might be an issue...


thanks,


--
/*
Warren Brunk - MCITP - SQL 2005, MCDBA
www.techintsolutions.com
*/


"Jerry Hung" <jerryhung (AT) hotmail (DOT) com> wrote

Same problem here. I have had backup exec installed and running for a
while, and added a new sql2005 express instance to the server.

We have tcp/ip enabled, remote connections are allowed

Hi,

I'm wondering if anyone has ever had resolution to this problem. I have
it eventually, it's fairly easy - ensure that the file - bedssql2.dll
(Found in C:\Program Files\VERITAS\Backup Exec\NT) has the same version
on eht remote MS SQL server.

Should be (as of 15th May 2007) Version 10.1.5629.37 (go to PROPERTIES >
VERSION (Tab) File Version will be at the top

If the remote M SQL server shows a different version, copy this one to
the same directory, restart all services on both machines and relaunch
Backup Exec.

Hope this helps everyone seeing as it took 3 long days and the patience
of one Symantec engineer to resolve it.

Cheers

*** Sent via Developersdex http://www.developersdex.com ***