November 26, 2006 at 3:35 am
Hi,
This is the message I get when I try and open the Enterprise Manager:
a connection could not be established to ****
Reason: SQL Server does not exist or access denied.
ConnectionOpen (Connect())..
Please verify SQL Server is running and check your SQL Server registration properties (by right-clicking on the **** node) and try again.
I tried checking the SQL Server registration but because the connection couldn't be establish I got no where with it.
Can anyone suggest how to solve this problem?
Is reinstalling the server an expected solution?
Thanks in advance
Malka
November 26, 2006 at 10:00 am
Where is the server located? Is it local or remote?
This is a connection problem. You can check the machine where SQL is running and see if the service is started.
November 27, 2006 at 2:05 am
Can you connect to the server using its IP address?
Can you ping and tracert to the server via its name?
I had this problem and "fixed" it my adding an entry in my hosts file. (For some reason connecting to the server via its name was attempting to log on to somewhere in the US. I'm in the UK!!)
-------------------------------------------------------------------------
Normal chaos will be resumed as soon as possible. :crazy:
November 27, 2006 at 2:31 am
The server is local, and I've restarted the server a few times with no difference in the situation.
I only try and connect to it via its IP address, I am uncertain how to connect to it via its name.
What sort of entry did you add to your hosts file?
November 27, 2006 at 4:32 am
It seems that you have a name resolution problem. Do you have a WINS Server in your domain ?
Try to ping the server with its name. If you get "host not found", try a ping with the FQDN (servername.domain). If you get an answer register the server in EM with the FQDN. If you do not get an answer, the server is not registered in the DNS.
Of course you can then add an entry in your host file as ip number servername.
November 27, 2006 at 4:49 am
Ad the server is local, have you tried rebooting the machine?
-------------------------------------------------------------------------
Normal chaos will be resumed as soon as possible. :crazy:
November 27, 2006 at 7:53 am
Check your registration credentials. If you have registered the server using a SQL user name and password, make sure the server is running in mixed mode (SQL Server and Windows) and that the password is correct.
November 27, 2006 at 9:51 am
Couple of quick questions:
Version & SP level of the SQL you are connecting to ?
What is the instance name ?
When registering you may want to include the instance name, if it is not default
i.e. SQL Server Name\SQL Instance Name
A quick test:
Can you connect to this server by creating a test odbc connection (Control Panel/Administrative Tools/Data Sources/SQL Server), using both Windows and SQL credentials ?
Again be sure to include the instance name, if it is not default.
Hope this helps
November 27, 2006 at 12:23 pm
First thing to do....go to the server itself. Open Query Analyzer and see if you can connect to the database. If not, then you aren't using a valid login for the database.
If your login isn't being accepted. You need to find out what type of authentication is being used by SQL Server and if you have a SQL Server account that works with that type of authentication.
If you can log on at the server itself, you then need to check your connection. Are you using the right IP address? Port number? Is there a firewall blocking access?
-SQLBill
November 27, 2006 at 2:52 pm
As mentioned above, what version are you running (including service packs) . Most of the time I have seen this error it is because of a firewall or networking issue.
Make sure you are on sp3 or above if you are installing on Windows xp or Windows 2003 (its a good idea to be on the latest service pack anyway)
Make sure your client network protocols are enabled for the connection type you are using.
November 27, 2006 at 11:51 pm
Moreno,
Being a complete newbie I don't know how to register the server in EM with FQDN.
I did ping the server with IP address and with its name and in both cases I received a response.
How do I add an entry to my host file? Better yet, what is the host file?
November 27, 2006 at 11:55 pm
How do I check the credentials?
If I try to edit the SQL registration properties I get a response saying that it couldn't connect.
Where do I look to see if it's running in mixed mode? and how do I change the mode?
BTW, the server was working fine for a good few months till the other day when this occured and since then I cannot connect to it.
November 28, 2006 at 12:06 am
First window of Query Analyzer asked for sql server. I put in IP address, checked Start SQL Server if it is stopped, and through windows authentication I got the message:
Unable to connect to server 127.0.0.1:
Server Msg:17, Level 16, State 1
[Microsoft][ODBC SQL Server Driver][TCP/IP Sockets]SQL Server does not exist or access denied.
I get same message using SQL Server authentication. Also same message using all the combinations.
The authentication which is used for this server is SQL Server authentication.
I have accessed the server plenty of times before this occured, I was using the server with no problem.
November 28, 2006 at 12:09 am
It is running on Windows 2000, SP4. No changes have been made to the server. It was working fine till this sudden change.
November 28, 2006 at 8:35 am
Malka,
You say: "BTW, the server was working fine for a good few months till the other day when this occured and since then I cannot connect to it."
Are you the admin on the SQL Server instance? If not, you need to have the admin check your account, it's probably been deleted.
Why do I opine that? Because you can't log on at the SQL Server's server itself. So it can't be a connection issue - you are on the server. It can't be a firewall issue - again you are using the server itself. Being on the server itself eliminates almost everything except that you don't have a login.
-SQLBill
Viewing 15 posts - 1 through 15 (of 17 total)
You must be logged in to reply to this topic. Login to reply