SQL 2005 Question

Hello - I am hoping someone can help me.  I need to connect to my BES database via BES Transporter service to migrate users to a new BES.  I receive the following error message.

 Error message

An error has ocurred when establishing a connection to the server.  When connecting to the SQL Server 2005, this failure may be caused by the fact that under the default settings of the SQL server does not allow remote connections.  I have found information online to check the surface configuration.  The strange issue is, I also have by backup exec software on this server - I do not see the properties for the sql configuration to just the main server.  I only see the configuration to the database area for the backup exec software.  I have attached screen shots.  

Any help would be greatly appreciated.

Thank you. sql database shot surface configuration area
kinggirlAsked:
Who is Participating?
 
Anthony PerkinsConnect With a Mentor Commented:
Then there are at least 2 possible reasons (though I am sure there are more) you can only connect on the server:
1. Remote Logins are not enabled. The following query should tell you if it is enabled:
SELECT *
FROM sys.configurations
WHERE name = 'remote access'

2. You are using a protocol not supported by the SQL Server service.
0
 
Anthony PerkinsCommented:
>>this failure may be caused by the fact that under the default settings of the SQL server does not allow remote connections. <<
Have you made sure that you have enabled remote connections?
0
 
kinggirlAuthor Commented:
Hello - yes remote connections is enabled.  The weird issue is I don't see the surface configurations for the service name.  I can only see the service name for the backup exec service.  Sorry, I am very green when it comes to sql.
0
Free Tool: ZipGrep

ZipGrep is a utility that can list and search zip (.war, .ear, .jar, etc) archives for text patterns, without the need to extract the archive's contents.

One of a set of tools we're offering as a way to say thank you for being a part of the community.

 
Anthony PerkinsCommented:
What is not clear to me is whether you are sharing the same server instance for your database with BackupExec.  So what you need to do is verify how many SQL Server services are actually running.  Go the the Services applet and you should find the backupexec instance, see if there are any more.
0
 
kinggirlAuthor Commented:
I only see the one service, but when I connect into sql server manager I have to change the server name.   Services Server
0
 
Anthony PerkinsCommented:
Just to be clear, when you are sitting at the server you can successfully log on to either server instance the default (SCHOMBERG) and the named instance (SCHOMBERG\BACKUPEXEC) ?  But when you are at a workstation you cannot?

Is that correct?
0
 
kinggirlAuthor Commented:
yes, that is right.
0
 
kinggirlAuthor Commented:
Hello - I was able to run the transporter service locally on the server.  Thank you for your help.
0
 
Anthony PerkinsCommented:
I am sorry I could not be of more help.
0
 
kinggirlAuthor Commented:
you did help - you got me thinking more :)  Much appeciated.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.