Please help lost connection urgent!

Hi,
After I install Service Pack3 on my local PC machine, I cannot connect to
the Development Server by using Query Analyzer and SQL Profiler. but the
strangest thing is i can connect to that server by using Enterprise Manager.
The error message showing on QA is
[Microsoft][ODBC SQL Server Driver][DBNETLIB]SQL Server does not exist or
access denied. -- it really doesn't make sense to me to only QA but not EM
.
Please help and thanks
EdThat may help:
http://groups.google.de/groups? q=S...ftngxa06&rnum=1
HTH, Jens Smeyer.
"Ed" <Ed@.discussions.microsoft.com> schrieb im Newsbeitrag
news:C80F022D-B11F-432A-9B86-5A9F86232244@.microsoft.com...
> Hi,
> After I install Service Pack3 on my local PC machine, I cannot connect
> to
> the Development Server by using Query Analyzer and SQL Profiler. but the
> strangest thing is i can connect to that server by using Enterprise
> Manager.
> The error message showing on QA is
> [Microsoft][ODBC SQL Server Driver][DBNETLIB]SQL Server does not exist or
> access denied. -- it really doesn't make sense to me to only QA but not
> EM.
> Please help and thanks
> Ed|||I'll quote you some possible solutions from sswug.org mailing list:
I recall that changing the port at which a named instance exists requires
restart of the default instance (or perhaps just SQL Agent?). If you can
easily restart the default instance and agent on the DEV box, I would do
so.
--
Fixed the problem on the DEV server. When the instance came back up, it
was for some reason, listening on 1433.... same as the default instance.
Changed the port number in SNU, restarted the services, and can connect
fine now.
--
Did you check the local Windows firewall settings on the MSDE machine?
You have to explicitly enable TCP and/or named pipes (globally or for a
single instance of SQL).
--
Is this a clustered instance? If so, disabling named pipes messes up the
named pipes reg key and this messes up both TCP and named pipes
connectivity.
Can you connect locally or does that fail as well? What about if you
force a specific protocol or port?
Np:Server\Instance
TCP:server\instance
LPC:server\instance
TCP:server\instance,port
Maybe some of these q&a's may give an idea.
Regards,
Marko Simic
"Ed" wrote:

> Hi,
> After I install Service Pack3 on my local PC machine, I cannot connect
to
> the Development Server by using Query Analyzer and SQL Profiler. but the
> strangest thing is i can connect to that server by using Enterprise Manage
r.
> The error message showing on QA is
> [Microsoft][ODBC SQL Server Driver][DBNETLIB]SQL Server does not exist or
> access denied. -- it really doesn't make sense to me to only QA but not
EM.
> Please help and thanks
> Ed|||Thanks for the answer from both.
I spent some much time looking at MS website to find the solution.
Finally, after I downloaded the MDAC 2.8 (newest version), everything is
back to normal now.
Ed
"Simic Marko" wrote:
> I'll quote you some possible solutions from sswug.org mailing list:
> --
> I recall that changing the port at which a named instance exists requires
> restart of the default instance (or perhaps just SQL Agent?). If you can
> easily restart the default instance and agent on the DEV box, I would do
> so.
> --
> Fixed the problem on the DEV server. When the instance came back up, it
> was for some reason, listening on 1433.... same as the default instance.
> Changed the port number in SNU, restarted the services, and can connect
> fine now.
> --
> Did you check the local Windows firewall settings on the MSDE machine?
> You have to explicitly enable TCP and/or named pipes (globally or for a
> single instance of SQL).
> --
> Is this a clustered instance? If so, disabling named pipes messes up the
> named pipes reg key and this messes up both TCP and named pipes
> connectivity.
> Can you connect locally or does that fail as well? What about if you
> force a specific protocol or port?
> Np:Server\Instance
> TCP:server\instance
> LPC:server\instance
> TCP:server\instance,port
> Maybe some of these q&a's may give an idea.
> Regards,
> Marko Simic
> "Ed" wrote:
>