all groups > sql server connect > september 2003 >
You're in the

sql server connect

group:

Sql Server does not exist or access denied


Sql Server does not exist or access denied jay
9/4/2003 5:14:54 AM
sql server connect:
I am currently only connecting to 2 outside SQL DB's using
Enterprise Manager. I have had no problems with either
account as of last Thursday. I started my system up after
4 days out of town and found that I could not connect to
either DB, always getting the following error "Sql Server
does not exist or access denied"

- I have since re-installed SQL Server added the SQL3
service pack.
- Installed and run Netshield to check for viruses "which
showed none".
- I deleted and recreated both accounts multiple times.
- Have checked and am sure that both of the host SQL
Servers are up and running and accessable from other
users.
- I installed SQL Server on the other machine on my home
network and recreated the same problem. I am however able
to connect to the other local machines SQL Server.

The only thing I can think of is a recent download of
windows service pack 4 or perhaps my Internet Provider no
longer allowing the use of port 1443.

Please help, project deadline becoming oh so close.

Re: Sql Server does not exist or access denied Sue Hoegemeier
9/4/2003 7:53:55 AM
There is an article to help with troubleshooting this error
message. It will give you a start on tracking down the
issue:
INF: Potential Causes of the "SQL Server Does Not Exist or
Access Denied" Error Message
http://support.microsoft.com/?id=328306

-Sue

On Thu, 4 Sep 2003 05:14:54 -0700, "jay"
[quoted text, click to view]
Re: Sql Server does not exist or access denied Leah Zagreus
9/12/2003 2:49:00 PM
Hello,

The article Sue mentioned was very helpful. However I
still had problems connecting until I did the following:

- Had my ISP open the firewall port 1433

- Installed MDAC 2.8

Hope this helps.

Leah


[quoted text, click to view]
Re: Sql Server does not exist or access denied Skip Borland
9/24/2003 12:24:05 AM
This also helps:

Somehow during the application of the SQL SP3 patch, it wiped out the port
setting for TCP. You can verify that by looking at the SQL logs. On startup
it shows the server listening on Named Pipes, but not TCP. If you look at
the protocols in the Enterprise Manager, it shows TCP installed to listen on
port 1433. But if you look at it in the registry, the entry is blank. I
believe that the Enterprise manager shows it as 1433 as a defualt, even if
it is not there. By removing the TCP protocol, saving the settings, then
re-adding the TCP protocol, the correct entries were made in the registry.

Skip

[quoted text, click to view]

AddThis Social Bookmark Button