Can't disable publishing

I have a server work as publisher and distributor for a database and another
remote server work as subscriber. The remote server downed and reformatted
due to system failure. We setup another remote server with different name.
But when I tried to disable publishing/ delete and recreate subscription at
publisher/distributor server, i received the following error:
The server has been disconnected. Please reconnect it and perform this
action again.
How should i fixed it?
Thank you.
In article <E87D093B-0F0D-4601-9D00-
6988821C47DB@.microsoft.com>, Clarin@.discussions.microsoft.com
says...
> I have a server work as publisher and distributor for a database and another
> remote server work as subscriber. The remote server downed and reformatted
> due to system failure. We setup another remote server with different name.
> But when I tried to disable publishing/ delete and recreate subscription at
> publisher/distributor server, i received the following error:
> The server has been disconnected. Please reconnect it and perform this
> action again.
> How should i fixed it?
> Thank you.
I have had this problem twice. You can do the sp that paul
said to do, but for it work you need to reboot the
publisher. I kept running it, and kept receiving the same
error you were getting. We finally rebooted the publisher
and stopped getting the error.
You can also set a fake subscriber with the same
name/db/tables as the old one (just no data in them), and
then delete it. That worked for us also.

Can't create linked server

Dear Sir,
I have a remote db server which I can connect using Query Analyzer but can't
setup a linked server to it, using same user account, any suggestion how to
trouble shoot?
Henry
Henry
What is an error you are getting?
"Henry" <Henry@.discussions.microsoft.com> wrote in message
news:C31AA693-9574-4636-B56E-5E004189F6CF@.microsoft.com...
> Dear Sir,
> I have a remote db server which I can connect using Query Analyzer but
> can't
> setup a linked server to it, using same user account, any suggestion how
> to
> trouble shoot?
> Henry
|||Dear Uri Dimant,
I can create the linked server but whenever I tried to access, e.g. click on
the Security->Linked Server->RemoteServer->Table/View, it return the error of
Error 7399
Both of my local and remote db are SQL 2000.
Henry
"Uri Dimant" wrote:

> Henry
> What is an error you are getting?
> "Henry" <Henry@.discussions.microsoft.com> wrote in message
> news:C31AA693-9574-4636-B56E-5E004189F6CF@.microsoft.com...
>
>
|||Hi Henry,
Do u have sa password on both the server.
if yes then drop ur linked server and create another one
give remote user and local user as sa and sa password.
in the other server type should be sql server if u create linked
server between sql server.
click the remote login option and give sa and sa password.
check the server option
these three should be selected
dataaccess,
RPC and RPC Out.
hope this help u
from
Doller
Henry wrote:[vbcol=seagreen]
> Dear Uri Dimant,
> I can create the linked server but whenever I tried to access, e.g. click on
> the Security->Linked Server->RemoteServer->Table/View, it return the error of
> Error 7399
> Both of my local and remote db are SQL 2000.
> Henry
> "Uri Dimant" wrote:
|||This has some example syntax for adding a linked server:
http://msdn.microsoft.com/library/en..._adda_8gqa.asp
-oj
"Henry" <Henry@.discussions.microsoft.com> wrote in message
news:5B480C91-E86A-46FC-AFC3-D59D8CBBBCCA@.microsoft.com...[vbcol=seagreen]
> Dear Uri Dimant,
> I can create the linked server but whenever I tried to access, e.g. click
> on
> the Security->Linked Server->RemoteServer->Table/View, it return the error
> of
> Error 7399
> Both of my local and remote db are SQL 2000.
> Henry
> "Uri Dimant" wrote:
|||Dear Doller,
I don't have SA account on remote db right now, but I have other linked
server using account without SA rights, e.g. have dbo rights and can also
make connection. Do you know if there any docuement for the access rights
requirement?
Henry
"doller" wrote:

> Hi Henry,
> Do u have sa password on both the server.
> if yes then drop ur linked server and create another one
> give remote user and local user as sa and sa password.
> in the other server type should be sql server if u create linked
> server between sql server.
> click the remote login option and give sa and sa password.
> check the server option
> these three should be selected
> dataaccess,
> RPC and RPC Out.
> hope this help u
> from
> Doller
>
> Henry wrote:
>

Can't create linked server

Dear Sir,
I have a remote db server which I can connect using Query Analyzer but can't
setup a linked server to it, using same user account, any suggestion how to
trouble shoot?
HenryHenry
What is an error you are getting?
"Henry" <Henry@.discussions.microsoft.com> wrote in message
news:C31AA693-9574-4636-B56E-5E004189F6CF@.microsoft.com...
> Dear Sir,
> I have a remote db server which I can connect using Query Analyzer but
> can't
> setup a linked server to it, using same user account, any suggestion how
> to
> trouble shoot?
> Henry|||Dear Uri Dimant,
I can create the linked server but whenever I tried to access, e.g. click on
the Security->Linked Server->RemoteServer->Table/View, it return the error of
Error 7399
Both of my local and remote db are SQL 2000.
Henry
"Uri Dimant" wrote:
> Henry
> What is an error you are getting?
> "Henry" <Henry@.discussions.microsoft.com> wrote in message
> news:C31AA693-9574-4636-B56E-5E004189F6CF@.microsoft.com...
> > Dear Sir,
> > I have a remote db server which I can connect using Query Analyzer but
> > can't
> > setup a linked server to it, using same user account, any suggestion how
> > to
> > trouble shoot?
> > Henry
>
>|||Hi Henry,
Do u have sa password on both the server.
if yes then drop ur linked server and create another one
give remote user and local user as sa and sa password.
in the other server type should be sql server if u create linked
server between sql server.
click the remote login option and give sa and sa password.
check the server option
these three should be selected
dataaccess,
RPC and RPC Out.
hope this help u
from
Doller
Henry wrote:
> Dear Uri Dimant,
> I can create the linked server but whenever I tried to access, e.g. click on
> the Security->Linked Server->RemoteServer->Table/View, it return the error of
> Error 7399
> Both of my local and remote db are SQL 2000.
> Henry
> "Uri Dimant" wrote:
> > Henry
> > What is an error you are getting?
> >
> > "Henry" <Henry@.discussions.microsoft.com> wrote in message
> > news:C31AA693-9574-4636-B56E-5E004189F6CF@.microsoft.com...
> > > Dear Sir,
> > > I have a remote db server which I can connect using Query Analyzer but
> > > can't
> > > setup a linked server to it, using same user account, any suggestion how
> > > to
> > > trouble shoot?
> > > Henry
> >
> >
> >|||This has some example syntax for adding a linked server:
http://msdn.microsoft.com/library/en-us/tsqlref/ts_sp_adda_8gqa.asp
-oj
"Henry" <Henry@.discussions.microsoft.com> wrote in message
news:5B480C91-E86A-46FC-AFC3-D59D8CBBBCCA@.microsoft.com...
> Dear Uri Dimant,
> I can create the linked server but whenever I tried to access, e.g. click
> on
> the Security->Linked Server->RemoteServer->Table/View, it return the error
> of
> Error 7399
> Both of my local and remote db are SQL 2000.
> Henry
> "Uri Dimant" wrote:
>> Henry
>> What is an error you are getting?
>> "Henry" <Henry@.discussions.microsoft.com> wrote in message
>> news:C31AA693-9574-4636-B56E-5E004189F6CF@.microsoft.com...
>> > Dear Sir,
>> > I have a remote db server which I can connect using Query Analyzer but
>> > can't
>> > setup a linked server to it, using same user account, any suggestion
>> > how
>> > to
>> > trouble shoot?
>> > Henry
>>|||Dear Doller,
I don't have SA account on remote db right now, but I have other linked
server using account without SA rights, e.g. have dbo rights and can also
make connection. Do you know if there any docuement for the access rights
requirement?
Henry
"doller" wrote:
> Hi Henry,
> Do u have sa password on both the server.
> if yes then drop ur linked server and create another one
> give remote user and local user as sa and sa password.
> in the other server type should be sql server if u create linked
> server between sql server.
> click the remote login option and give sa and sa password.
> check the server option
> these three should be selected
> dataaccess,
> RPC and RPC Out.
> hope this help u
> from
> Doller
>
> Henry wrote:
> > Dear Uri Dimant,
> > I can create the linked server but whenever I tried to access, e.g. click on
> > the Security->Linked Server->RemoteServer->Table/View, it return the error of
> > Error 7399
> >
> > Both of my local and remote db are SQL 2000.
> >
> > Henry
> >
> > "Uri Dimant" wrote:
> >
> > > Henry
> > > What is an error you are getting?
> > >
> > > "Henry" <Henry@.discussions.microsoft.com> wrote in message
> > > news:C31AA693-9574-4636-B56E-5E004189F6CF@.microsoft.com...
> > > > Dear Sir,
> > > > I have a remote db server which I can connect using Query Analyzer but
> > > > can't
> > > > setup a linked server to it, using same user account, any suggestion how
> > > > to
> > > > trouble shoot?
> > > > Henry
> > >
> > >
> > >
>

Can't create linked server

Dear Sir,
I have a remote db server which I can connect using Query Analyzer but can't
setup a linked server to it, using same user account, any suggestion how to
trouble shoot?
HenryHenry
What is an error you are getting?
"Henry" <Henry@.discussions.microsoft.com> wrote in message
news:C31AA693-9574-4636-B56E-5E004189F6CF@.microsoft.com...
> Dear Sir,
> I have a remote db server which I can connect using Query Analyzer but
> can't
> setup a linked server to it, using same user account, any suggestion how
> to
> trouble shoot?
> Henry|||Dear Uri Dimant,
I can create the linked server but whenever I tried to access, e.g. click on
the Security->Linked Server->RemoteServer->Table/View, it return the error o
f
Error 7399
Both of my local and remote db are SQL 2000.
Henry
"Uri Dimant" wrote:

> Henry
> What is an error you are getting?
> "Henry" <Henry@.discussions.microsoft.com> wrote in message
> news:C31AA693-9574-4636-B56E-5E004189F6CF@.microsoft.com...
>
>|||Hi Henry,
Do u have sa password on both the server.
if yes then drop ur linked server and create another one
give remote user and local user as sa and sa password.
in the other server type should be sql server if u create linked
server between sql server.
click the remote login option and give sa and sa password.
check the server option
these three should be selected
dataaccess,
RPC and RPC Out.
hope this help u
from
Doller
Henry wrote:[vbcol=seagreen]
> Dear Uri Dimant,
> I can create the linked server but whenever I tried to access, e.g. click
on
> the Security->Linked Server->RemoteServer->Table/View, it return the error
of
> Error 7399
> Both of my local and remote db are SQL 2000.
> Henry
> "Uri Dimant" wrote:
>|||This has some example syntax for adding a linked server:
http://msdn.microsoft.com/library/e...p_adda_8gqa.asp
-oj
"Henry" <Henry@.discussions.microsoft.com> wrote in message
news:5B480C91-E86A-46FC-AFC3-D59D8CBBBCCA@.microsoft.com...[vbcol=seagreen]
> Dear Uri Dimant,
> I can create the linked server but whenever I tried to access, e.g. click
> on
> the Security->Linked Server->RemoteServer->Table/View, it return the error
> of
> Error 7399
> Both of my local and remote db are SQL 2000.
> Henry
> "Uri Dimant" wrote:
>|||Dear Doller,
I don't have SA account on remote db right now, but I have other linked
server using account without SA rights, e.g. have dbo rights and can also
make connection. Do you know if there any docuement for the access rights
requirement?
Henry
"doller" wrote:

> Hi Henry,
> Do u have sa password on both the server.
> if yes then drop ur linked server and create another one
> give remote user and local user as sa and sa password.
> in the other server type should be sql server if u create linked
> server between sql server.
> click the remote login option and give sa and sa password.
> check the server option
> these three should be selected
> dataaccess,
> RPC and RPC Out.
> hope this help u
> from
> Doller
>
> Henry wrote:
>

Can't create a ODBC DSN to a remote MSDE instance

Hello,
I need to create an ODBC DNS that points to a remote MSDE instance, but I
can only get it to work if I turn Windows Firewall off. Both the local and
remote machines are WinXP SP2 and have SQL2000 and MSDE, same domain and I
can login as the same person on each machine.
On the remote machine I've enabled TCP/IP and the default port, and I've
added that port to the firewall, but when I try to add a DSN (on the local
machine) in the ODBC control panel it says
[Microsoft][ODBC SQL Server Driver][DBNETLIB]SQL Server does not exist or
access denied.
I've looked at the instance via Enterprise Manager and my domain login has
admin privs, and can connect a DSN to the SQL2000 server on that machine.
Stumped.
Suggestions?
Keith
hi Keith,
Keith wrote:
> Hello,
> I need to create an ODBC DNS that points to a remote MSDE instance,
> but I can only get it to work if I turn Windows Firewall off. Both
> the local and remote machines are WinXP SP2 and have SQL2000 and
> MSDE, same domain and I can login as the same person on each machine.
> On the remote machine I've enabled TCP/IP and the default port, and
> I've added that port to the firewall, but when I try to add a DSN (on
> the local machine) in the ODBC control panel it says
> [Microsoft][ODBC SQL Server Driver][DBNETLIB]SQL Server does not
> exist or access denied.
> I've looked at the instance via Enterprise Manager and my domain
> login has admin privs, and can connect a DSN to the SQL2000 server on
> that machine.
did you define an exception on the server's firewall on the MSDE used TCP/IP
port or on the service itself?
http://support.microsoft.com/default.aspx?kbid=841249
http://support.microsoft.com/default.aspx?scid=kb;[LN];841251
http://support.microsoft.com/default.aspx?scid=kb;[LN];884012 (Win2003)
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.12.0 - DbaMgr ver 0.58.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
|||>
> did you define an exception on the server's firewall on the MSDE used
> TCP/IP port or on the service itself?
> http://support.microsoft.com/default.aspx?kbid=841249
> http://support.microsoft.com/default.aspx?scid=kb;[LN];841251
> http://support.microsoft.com/default.aspx?scid=kb;[LN];884012 (Win2003)
Well, after some reboots and a walk around the block it works now.
I finally got it to work either with firewall port exception, or a service
exception, but neither way seemed very consistent. Making changes to the
firewall while it is running just doesn't seem to work that well; perhaps I
wasn't waiting long enough for the changes to propagate or I just need to
stop/start the firewall after changing something.
And I suspect that some of the changes that don't "require" rebooting really
do.
Anyway, thanks for the quick response and support links.
Keith

Can't connection to SQL 2000 on Windows 2003 from web application running on windows x

I'm developing a web application that is running locally on my Windows XP PC
. It connects to remote database server which sits on a Windows 2003 server.
When i try to open the connection, i recieve an error, "SQL Server does not
exist or access denied". I
know for fact this connection string works, because I can use the same conne
ction string in a console application, and retrieve data. So far I have esta
blished the following:
-- I can connect to the DB via all client applications (query analyzer, .net
console appliation etc.), except from .net web application.
-- Other developers running windows 2003 and II6 can connect to DB using the
same configuration.
-- Developers, like myself, running on XP and IIS 5.1 can NOT connect.
-- from the .net web application I can connect to SQL servers that reside on
Windows 2000 server.
thanksThanks for posting what you've tried:
This helps enormously. <g>
-- I can connect to the DB via all client applications (query analyzer,
.net console appliation etc.), except from .net web application.
-- Other developers running windows 2003 and II6 can connect to DB using
the same configuration.
-- Developers, like myself, running on XP and IIS 5.1 can NOT connect.
-- from the .net web application I can connect to SQL servers that reside
on Windows 2000 serv
So, what's missing here is what security context or that your web
application is using and what security mode
IIS is in.
Are you running the IIS site in Annony, Basic or Windows Auth ?
Are you attempting to connect to SQL from IIS using an account with
username & password or
with a Trusted Connection?
Does the .NET app attempt to Impersonate?
Thanks,
Kevin McDonnell
Microsoft Corporation
This posting is provided AS IS with no warranties, and confers no rights.|||Kevin,
thank you for the reply. The settings on the IIS and the web application are
fairly generic, I believe I'm using all the default values for configuratio
n.

>Are you running the IIS site in Annony, Basic or Windows Auth ?
Annonymous access is enable on the IIS.

>Are you attempting to connect to SQL from IIS using an account with
username & password or with a Trusted Connection?
I'm using an SQL account with username and password to connect to the DB

>Does the .NET app attempt to Impersonate?
there is no impersonation involved.
-- Kevin McDonnell [MSFT] wrote: --
Thanks for posting what you've tried:
This helps enormously. <g>
-- I can connect to the DB via all client applications (query analyzer,
.net console appliation etc.), except from .net web application.
-- Other developers running windows 2003 and II6 can connect to DB using
the same configuration.
-- Developers, like myself, running on XP and IIS 5.1 can NOT connect.
-- from the .net web application I can connect to SQL servers that reside
on Windows 2000 serv
So, what's missing here is what security context or that your web
application is using and what security mode
IIS is in.
Are you running the IIS site in Annony, Basic or Windows Auth ?
Are you attempting to connect to SQL from IIS using an account with
username & password or
with a Trusted Connection?
Does the .NET app attempt to Impersonate?
Thanks,
Kevin McDonnell
Microsoft Corporation
This posting is provided AS IS with no warranties, and confers no rights.|||it turns out, to resolve the issue, we just needed to install sp3 a couple o
f times on the SQL server.|||Hi,
I'm having the same problem. And these are mine settings:
Q: Are you running the IIS site in Annony, Basic or Windows Auth ?
A: I'm using FORMS-authentification (web.config)
Q: Are you attempting to connect to SQL from IIS using an account with usern
ame & password or with a Trusted Connection?
A: I want to connect throug username and password
Q: Does the .NET app attempt to Impersonate?
A: As far as i know i don't.
I hope u can explain me the problem.
Thanx Bram
Posted using Wimdows.net NntpNews Component -
Post Made from http://www.SqlJunkies.com/newsgroups Our newsgroup engine sup
ports Post Alerts, Ratings, and Searching.

Can't Connect with Remote Sql server.

Hello All ,

I had installed Sql Server 2000 on Windows server 2003 enterprize Edition. But when I Try to connect it with Remote, 'Sql Server doesn't exists' message appears..

anybody know what may be the reason?

Moving this thread to the SQL Server forums.|||

By default, SQL Server 2005 does not allows remote connections. To configure SQL Server 2005 to allow remote connections, complete all the following steps:

1.Select the SQL Server Surface Area Configuration tool from the Configuration Tools and then click Surface Area Configuration for Services and Connections option. expand Database Engine, click Remote Connections, click Local and remote connections, click the appropriate protocol to enable for your environment, and then click Apply and Ok for restarting the Database engine service.

2. Try adding sqlservr.exe (present in \MSSQL\Binn directory for the default instance and \MSSQL$instance_name\Binn directory for the named instance) in the list of allowed firewall exceptions on the Windows 2003 box.

Regards,

Rajesh

|||

My question was slightly wrong..

I want to connect with sqlserver 2000 with Ip address.

-my installments are

1. Microsoft Windows Xp or window 2003 server

2 Sql Server 2000

and just want to do to connect with ip address.

I can connect to sqlserver with ip in windows2000

|||

You can connect using IP Address without any problem and for that ensure to add an entry on the client network utility on your client's machine.

Also refer to KBA http://www.sql-server-performance.com/faq/sqlviewfaq.aspx?topicid=12&faqid=143 which helps to resolve any issues you might get.

Can't Connect with Remote Sql server.

Hello All ,

I had installed Sql Server 2000 on Windows server 2003 enterprize Edition. But when I Try to connect it with Remote, 'Sql Server doesn't exists' message appears..

anybody know what may be the reason?

Moving this thread to the SQL Server forums.|||

By default, SQL Server 2005 does not allows remote connections. To configure SQL Server 2005 to allow remote connections, complete all the following steps:

1.Select the SQL Server Surface Area Configuration tool from the Configuration Tools and then click Surface Area Configuration for Services and Connections option. expand Database Engine, click Remote Connections, click Local and remote connections, click the appropriate protocol to enable for your environment, and then click Apply and Ok for restarting the Database engine service.

2. Try adding sqlservr.exe (present in \MSSQL\Binn directory for the default instance and \MSSQL$instance_name\Binn directory for the named instance) in the list of allowed firewall exceptions on the Windows 2003 box.

Regards,

Rajesh

|||

My question was slightly wrong..

I want to connect with sqlserver 2000 with Ip address.

-my installments are

1. Microsoft Windows Xp or window 2003 server

2 Sql Server 2000

and just want to do to connect with ip address.

I can connect to sqlserver with ip in windows2000

|||

You can connect using IP Address without any problem and for that ensure to add an entry on the client network utility on your client's machine.

Also refer to KBA http://www.sql-server-performance.com/faq/sqlviewfaq.aspx?topicid=12&faqid=143 which helps to resolve any issues you might get.

Can't Connect with EM

When tring to connect to a remote sql server through EM, I get the following
error message: "SQL Server does not exist or access denied[]ConnectionOpen"
How can I resolve this? Any help is appriciated.
New SQL Server DBA
I believe this would be because the account you are using to access the
Remote SQL Server is not valid, or you do not have the correct password.
Register the server in EM with a valid account and password. A local
administrator account on the Remote SQL Server server has access to SQL
Server. If you are added to the Local Administrators Group, then register
the server in EM using Windows Authentication...Ibelieve this will get you
going.
"Newbie" wrote:

> When tring to connect to a remote sql server through EM, I get the following
> error message: "SQL Server does not exist or access denied[]ConnectionOpen"
> How can I resolve this? Any help is appriciated.
> --
> New SQL Server DBA
|||Newbie (Newbie@.discussions.microsoft.com) writes:
> When tring to connect to a remote sql server through EM, I get the
> following error message: "SQL Server does not exist or access
> denied[]ConnectionOpen"
> How can I resolve this? Any help is appriciated.
This message means that for some reason you cannot reach SQL Server. (Thus
not as NetByTelDBA suggested that your account is not valid.) There are
a number of possible reasons for this. The SQL Server could be down. The
server name you are trying to use does not resolve. You have no connection
to that network. Or you have no permission to that network.
This KN article discusses the matter further:
http://support.microsoft.com/default...EN-US;q328306.
Erland Sommarskog, SQL Server MVP, esquel@.sommarskog.se
Books Online for SQL Server SP3 at
http://www.microsoft.com/sql/techinf...2000/books.asp

Can't Connect with EM

When tring to connect to a remote sql server through EM, I get the following
error message: "SQL Server does not exist or access denied[]ConnectionO
pen"
How can I resolve this? Any help is appriciated.
New SQL Server DBAI believe this would be because the account you are using to access the
Remote SQL Server is not valid, or you do not have the correct password.
Register the server in EM with a valid account and password. A local
administrator account on the Remote SQL Server server has access to SQL
Server. If you are added to the Local Administrators Group, then register
the server in EM using Windows Authentication...Ibelieve this will get you
going.
"Newbie" wrote:

> When tring to connect to a remote sql server through EM, I get the followi
ng
> error message: "SQL Server does not exist or access denied[]Connectio
nOpen"
> How can I resolve this? Any help is appriciated.
> --
> New SQL Server DBA|||Newbie (Newbie@.discussions.microsoft.com) writes:
> When tring to connect to a remote sql server through EM, I get the
> following error message: "SQL Server does not exist or access
> denied[]ConnectionOpen"
> How can I resolve this? Any help is appriciated.
This message means that for some reason you cannot reach SQL Server. (Thus
not as NetByTelDBA suggested that your account is not valid.) There are
a number of possible reasons for this. The SQL Server could be down. The
server name you are trying to use does not resolve. You have no connection
to that network. Or you have no permission to that network.
This KN article discusses the matter further:
http://support.microsoft.com/defaul...;EN-US;q328306.
Erland Sommarskog, SQL Server MVP, esquel@.sommarskog.se
Books Online for SQL Server SP3 at
http://www.microsoft.com/sql/techin.../2000/books.asp

Can't Connect with EM

When tring to connect to a remote sql server through EM, I get the following
error message: "SQL Server does not exist or access denied[]ConnectionOpen"
How can I resolve this? Any help is appriciated.
--
New SQL Server DBAI believe this would be because the account you are using to access the
Remote SQL Server is not valid, or you do not have the correct password.
Register the server in EM with a valid account and password. A local
administrator account on the Remote SQL Server server has access to SQL
Server. If you are added to the Local Administrators Group, then register
the server in EM using Windows Authentication...Ibelieve this will get you
going.
"Newbie" wrote:
> When tring to connect to a remote sql server through EM, I get the following
> error message: "SQL Server does not exist or access denied[]ConnectionOpen"
> How can I resolve this? Any help is appriciated.
> --
> New SQL Server DBA|||Newbie (Newbie@.discussions.microsoft.com) writes:
> When tring to connect to a remote sql server through EM, I get the
> following error message: "SQL Server does not exist or access
> denied[]ConnectionOpen"
> How can I resolve this? Any help is appriciated.
This message means that for some reason you cannot reach SQL Server. (Thus
not as NetByTelDBA suggested that your account is not valid.) There are
a number of possible reasons for this. The SQL Server could be down. The
server name you are trying to use does not resolve. You have no connection
to that network. Or you have no permission to that network.
This KN article discusses the matter further:
http://support.microsoft.com/default.aspx?scid=KB;EN-US;q328306.
--
Erland Sommarskog, SQL Server MVP, esquel@.sommarskog.se
Books Online for SQL Server SP3 at
http://www.microsoft.com/sql/techinfo/productdoc/2000/books.asp

Can't connect using management studio while using remote desktop connection on lan.

I get the error message:

An error has occurred while establishing a connection to the server.

When connecting to SQL Server 2005, this failure may be caused by the

fact that under the default settings SQL Server does not allow remote

connections.

I am not able to find this setting. Could someone please inform me of where to look and maybe what to do?

Thanks in advance.

Start/Programs/Microsoft SQL Server 2005/Configuration Tools/SQL Server Surface Area Configuration Manager/
Click Surface Area Configuration for Services and Connections
Click Database Engines / Remote connections
Select Local and Remote connections and one of the 3 choices below

also make sure the Allow Remote Connection to This Server option is checked on the
Server Properties/Connections page

|||

lkh wrote:

Start/Programs/Microsoft SQL Server 2005/Configuration Tools/SQL Server Surface Area Configuration Manager/
Click Surface Area Configuration for Services and Connections
Click Database Engines / Remote connections
Select Local and Remote connections and one of the 3 choices below

also make sure the Allow Remote Connection to This Server option is checked on the
Server Properties/Connections page

I have found the settings within the configuration tools up to the part where you mention the 3 choices below with success.

The part:
also make sure the Allow Remote Connection to This Server option is checked on the
Server Properties/Connections page

Is that from within the same configuration area or elsewhere?
Thanks so much.|||In Object Explorer in SQL Server Management Studio (SSMS) right click the server, click properties.|||

lkh wrote:

In Object Explorer in SQL Server Management Studio (SSMS) right click the server, click properties.

I'm sorry, there is nothing listed under object explorer pane. I see a default server under database engine in the registered servers pane.

Maybe because I haven't been able to connect yet? I'm not sure where else to look. I'm prolly goofed atm.

Maybe I'll have to do this the normal way and actually connect locally on that computer, then set that setting you mention.

I was hoping I could avoid having to do that, but I will if I have to.|||

right-click the default server, then click Connect/Object Explorer

SQL Server service also has to be started

|||Thanks so much for the help, the second part is already set to allow remote connections.
Turns out the problem I was having was due to my logging in as the second admin account on that pc. I could swear I installed it from that user account but it's acting like I can only connect to SQL via the original account on the pc.
Can't put my finger on it as it's been too long since the install.

Thanks for the help, all's good for now.|||Are you connecting with server\instance?

Can't connect to through OLE DB to remote host - Database 'XXX' does not exist.

My application is to get some data from SQL/OLAP server.
When I try to open OleDbConnection using connection string:
"Provider=MSOLAP;Data Source=servername;Initial Catalog=dbname;"
I get message:
Database 'XXX' does not exist.
I can easily connect in the same way to localhost.
My user is olap administrator on the remote and localhost.
Using Analysis Manager or MDX Sample App from my PC I can connect to
both - local and remote DB.
The problem is I think that I still log in as anonymous user - I found
it in remote server's event log.
How can I log on authenticated? Analysis Manager can!
Any suggestions welcome!It seems that only I have that kind of problem.
Is there something I'm doing wrong?
Is it possible that my pc has to be in a domain? What if there is no
domain?
Guys please suggest me some checks or tests. Ask me something :)
This is my first approach to OLAP.
I don't know what to do.
On 27 Sie, 18:02, panko <PKoper...@.gmail.com> wrote:
> My application is to get some data from SQL/OLAP server.
> When I try to open OleDbConnection using connection string:
> "Provider=MSOLAP;Data Source=servername;Initial Catalog=dbname;"
> I get message:
> Database 'XXX' does not exist.
> I can easily connect in the same way to localhost.
> My user is olap administrator on the remote and localhost.
> Using Analysis Manager or MDX Sample App from my PC I can connect to
> both - local and remote DB.
> The problem is I think that I still log in as anonymous user - I found
> it in remote server's event log.
> How can I log on authenticated? Analysis Manager can!
> Any suggestions welcome!|||You all miserable geeks! ;)
I finally solved the problem.
The application was running as service. This service by default was
using System Local Account to log on. Therefore was refused by the
remote machine system which was not allowing this user to be
authenticated.
Solution was:
Services: MyService>Properties>Log On
Radio button on 'This Account': user and password that has right on
remote host.

Cant connect to SQL Server 2005 Express from VStudio 2005 pro.?

Hello
I can't do subject. It says the SQL Server does not allow remote connections, but in SQL Server surface area conf. it is turned on.
What to do?
CheersGot it to work now. I wrote localhost as with SQL Server 2000, and changed it to .\SQLExpress
Cheers

Cant connect to sql server 2000 from asp.net

I installed sql server 2000 on a remote server. I can connect toit from the client with query analyzer, but I cannot connect to it fromASP.NET. I'm using Sql authentication, and the account has everypermission under the sun. I can also connect to it from theserver explorer in visual studio.net. I turned off thefirewall. I tried connecting with the same asp.net code from adifferent computer and still no luck. I've triple-double-checkedthe connectionstring. It's the same credentials I'm using forquery analyzer and server explorer, which both work fine. Anytroubleshooting tips would be GREATLY appreciated.

Thank you.What error message are you receiving?|||The problem ended up being with the version of .net I was using. I hadinstalled 1.1 initially, but someone installed commerce server 2002 andit installed .net 1.0 on top of that, which messed everything up. I reinstalled windows 2003 and then reinstalled .net 1.1, and all isgood.

Can't Connect to SQL 2005 Using Remote Desktop and Local Administr

I installed SQL 2005 Standard on Windows 2003 R2, and when I connect to the
server (no firewall involved) using Remote Desktop, I can't login to
Management Studio using the local administrator account. However, I can log
in using the domain administrator account. The local administrator account i
s
not locked out. I get the following error when trying to access Management
Studio using the local admin. account:
An error has occurred while establishing a connection to the server. When
connecting to SQL Server 2005, this failure may be caused by the fact that
under the default settings SQL Server does not allow remote connections.
(provider: Named Pipes Provider, error: 40 - Could not open a connection to
SQL Server) (.Net SqlClient Data Provider)
Any ideas?***UPDATE***
Actually, it has nothing to do with remote connectivity. I tried to log in
to Management Studio locally as the local administrator, and it still
wouldn't let me and gave the same error. As mentioned previously, the domain
admin. works.
Thanks.
"Marks70" wrote:

> I installed SQL 2005 Standard on Windows 2003 R2, and when I connect to th
e
> server (no firewall involved) using Remote Desktop, I can't login to
> Management Studio using the local administrator account. However, I can lo
g
> in using the domain administrator account. The local administrator account
is
> not locked out. I get the following error when trying to access Management
> Studio using the local admin. account:
> An error has occurred while establishing a connection to the server. When
> connecting to SQL Server 2005, this failure may be caused by the fact that
> under the default settings SQL Server does not allow remote connections.
> (provider: Named Pipes Provider, error: 40 - Could not open a connection t
o
> SQL Server) (.Net SqlClient Data Provider)
> Any ideas?

Can't connect to SQL

Hello,
We just installed SQL 2000 on a remote server. We can't connect to SQL
remotely from a desktop PC. When we try to register the SQL server in
Enterprise Mgr. we get the error:
"Client unable to establish connection. Named Pipes Provider: The network
path was not found. Timeout expired."
I checked the protocols on the SQL server and there is: TCP/IP and Named
Pipes (the default), so I disabled Named Pipes, but the error still occurs.
Anyone know what might be the problem?
Thanks!
What Network Operating System (NOS) are you running?
What service packs have been applied?
Are both servers in the same domain?
Do you have to go through a firewall?
More information would be helpful.
Rick Sawtell
MCT, MCSD, MCDBA
"Dean J Garrett" <info@.amuletc.com> wrote in message
news:u14$po%23qEHA.2588@.TK2MSFTNGP12.phx.gbl...
> Hello,
> We just installed SQL 2000 on a remote server. We can't connect to SQL
> remotely from a desktop PC. When we try to register the SQL server in
> Enterprise Mgr. we get the error:
> "Client unable to establish connection. Named Pipes Provider: The network
> path was not found. Timeout expired."
> I checked the protocols on the SQL server and there is: TCP/IP and Named
> Pipes (the default), so I disabled Named Pipes, but the error still
occurs.
> Anyone know what might be the problem?
> Thanks!
>
|||Rick,
The SQL Server is Windows 2003 Server, the desktop is XP Pro (not SP2).
There is no firewall on the SQL server (not supposed to be). The server and
desktop PC are not in the same domain. Any clues?
Thanks!
"Rick Sawtell" <ricksawtell@.hotmail.com> wrote in message
news:ushY2w#qEHA.2340@.TK2MSFTNGP11.phx.gbl...[vbcol=seagreen]
> What Network Operating System (NOS) are you running?
> What service packs have been applied?
> Are both servers in the same domain?
> Do you have to go through a firewall?
> More information would be helpful.
> Rick Sawtell
> MCT, MCSD, MCDBA
>
> "Dean J Garrett" <info@.amuletc.com> wrote in message
> news:u14$po%23qEHA.2588@.TK2MSFTNGP12.phx.gbl...
network
> occurs.
>
|||Does the client PC list the sqlserver when you try to register it or you type it in?
"Dean J Garrett" <info@.amuletc.com> wrote in message news:e1vxB2#qEHA.1644@.tk2msftngp13.phx.gbl...
Rick,
The SQL Server is Windows 2003 Server, the desktop is XP Pro (not SP2).
There is no firewall on the SQL server (not supposed to be). The server and
desktop PC are not in the same domain. Any clues?
Thanks!
"Rick Sawtell" <ricksawtell@.hotmail.com> wrote in message
news:ushY2w#qEHA.2340@.TK2MSFTNGP11.phx.gbl...[vbcol=seagreen]
> What Network Operating System (NOS) are you running?
> What service packs have been applied?
> Are both servers in the same domain?
> Do you have to go through a firewall?
> More information would be helpful.
> Rick Sawtell
> MCT, MCSD, MCDBA
>
> "Dean J Garrett" <info@.amuletc.com> wrote in message
> news:u14$po%23qEHA.2588@.TK2MSFTNGP12.phx.gbl...
network
> occurs.
>
|||Sounds like a security issue to me.
Are you using SQL validation or Windows validation? If Windows validation, then you need to ensure that your workstation is trusted by the W2k3 server's DC.
If you are trying to connect through a named pipe, then umm. (I'm a bit out of my element on this one), but you may need to set up some type of Share on the W2k3 server so that the pipe is able to connect to the server.
Hope this helps, maybe someone with some additional insight can be of service on this one.
Rick
"TJ" <tunj@.hotmail.com> wrote in message news:eY%23g28ArEHA.1644@.tk2msftngp13.phx.gbl...
Does the client PC list the sqlserver when you try to register it or you type it in?
"Dean J Garrett" <info@.amuletc.com> wrote in message news:e1vxB2#qEHA.1644@.tk2msftngp13.phx.gbl...
Rick,
The SQL Server is Windows 2003 Server, the desktop is XP Pro (not SP2).
There is no firewall on the SQL server (not supposed to be). The server and
desktop PC are not in the same domain. Any clues?
Thanks!
"Rick Sawtell" <ricksawtell@.hotmail.com> wrote in message
news:ushY2w#qEHA.2340@.TK2MSFTNGP11.phx.gbl...[vbcol=seagreen]
> What Network Operating System (NOS) are you running?
> What service packs have been applied?
> Are both servers in the same domain?
> Do you have to go through a firewall?
> More information would be helpful.
> Rick Sawtell
> MCT, MCSD, MCDBA
>
> "Dean J Garrett" <info@.amuletc.com> wrote in message
> news:u14$po%23qEHA.2588@.TK2MSFTNGP12.phx.gbl...
network
> occurs.
>
|||Can you ping the server from the client?
Jeff
"Dean J Garrett" <info@.amuletc.com> wrote in message
news:u14$po#qEHA.2588@.TK2MSFTNGP12.phx.gbl...
> Hello,
> We just installed SQL 2000 on a remote server. We can't connect to SQL
> remotely from a desktop PC. When we try to register the SQL server in
> Enterprise Mgr. we get the error:
> "Client unable to establish connection. Named Pipes Provider: The network
> path was not found. Timeout expired."
> I checked the protocols on the SQL server and there is: TCP/IP and Named
> Pipes (the default), so I disabled Named Pipes, but the error still
occurs.
> Anyone know what might be the problem?
> Thanks!
>
|||Hello, when I try to register the remote SQL Server, it does not list it in the pull-down because I'm using a workstation in an office, and the SQL Server is a machine in an ISPs data center across the country. Instead, I type in the IP address for the remote SQL box, and then enter SQL authentication that works fine when I'm using the SQL Server directly (via remote desktop). The SQL registration process fails due to the error:
"Client unable to establish connection. Named pipes provider: The network path was not found. Time-out expired."
Any clues?
"TJ" <tunj@.hotmail.com> wrote in message news:eY#g28ArEHA.1644@.tk2msftngp13.phx.gbl...
Does the client PC list the sqlserver when you try to register it or you type it in?
"Dean J Garrett" <info@.amuletc.com> wrote in message news:e1vxB2#qEHA.1644@.tk2msftngp13.phx.gbl...
Rick,
The SQL Server is Windows 2003 Server, the desktop is XP Pro (not SP2).
There is no firewall on the SQL server (not supposed to be). The server and
desktop PC are not in the same domain. Any clues?
Thanks!
"Rick Sawtell" <ricksawtell@.hotmail.com> wrote in message
news:ushY2w#qEHA.2340@.TK2MSFTNGP11.phx.gbl...[vbcol=seagreen]
> What Network Operating System (NOS) are you running?
> What service packs have been applied?
> Are both servers in the same domain?
> Do you have to go through a firewall?
> More information would be helpful.
> Rick Sawtell
> MCT, MCSD, MCDBA
>
> "Dean J Garrett" <info@.amuletc.com> wrote in message
> news:u14$po%23qEHA.2588@.TK2MSFTNGP12.phx.gbl...
network
> occurs.
>
|||Hello, the SQL Server 2000 installation uses Mixed authentication, SQL and Windows. When I try to register the SQL Server remotely from my desktop, I enter SQL username/password. This always worked in the past with other SQL servers.
I don't know if I'm trying to use named pipes, in fact I'd rather use only TCP/IP. As a suggestion by another newsgroup member, I disabled Name Pipes completely on the remote SQL server, but I still get the error message below:
"Client unable to establish connection. Named pipes provider: The network path was not found. Timeout expired."
Any clues?
"Rick Sawtell" <r_sawtell@.hotmail.com> wrote in message news:#3KkuSBrEHA.332@.TK2MSFTNGP14.phx.gbl...
Sounds like a security issue to me.
Are you using SQL validation or Windows validation? If Windows validation, then you need to ensure that your workstation is trusted by the W2k3 server's DC.
If you are trying to connect through a named pipe, then umm. (I'm a bit out of my element on this one), but you may need to set up some type of Share on the W2k3 server so that the pipe is able to connect to the server.
Hope this helps, maybe someone with some additional insight can be of service on this one.
Rick
"TJ" <tunj@.hotmail.com> wrote in message news:eY%23g28ArEHA.1644@.tk2msftngp13.phx.gbl...
Does the client PC list the sqlserver when you try to register it or you type it in?
"Dean J Garrett" <info@.amuletc.com> wrote in message news:e1vxB2#qEHA.1644@.tk2msftngp13.phx.gbl...
Rick,
The SQL Server is Windows 2003 Server, the desktop is XP Pro (not SP2).
There is no firewall on the SQL server (not supposed to be). The server and
desktop PC are not in the same domain. Any clues?
Thanks!
"Rick Sawtell" <ricksawtell@.hotmail.com> wrote in message
news:ushY2w#qEHA.2340@.TK2MSFTNGP11.phx.gbl...[vbcol=seagreen]
> What Network Operating System (NOS) are you running?
> What service packs have been applied?
> Are both servers in the same domain?
> Do you have to go through a firewall?
> More information would be helpful.
> Rick Sawtell
> MCT, MCSD, MCDBA
>
> "Dean J Garrett" <info@.amuletc.com> wrote in message
> news:u14$po%23qEHA.2588@.TK2MSFTNGP12.phx.gbl...
network
> occurs.
>
|||Yes, absolutely.
"Jeff Dillon" <jeff@.removeemergencyreporting.com> wrote in message
news:eGqYVuIrEHA.1272@.TK2MSFTNGP09.phx.gbl...[vbcol=seagreen]
> Can you ping the server from the client?
> Jeff
> "Dean J Garrett" <info@.amuletc.com> wrote in message
> news:u14$po#qEHA.2588@.TK2MSFTNGP12.phx.gbl...
network
> occurs.
>
|||You're still trying to use Named Pipes. Use both Client and Server Network
Utilities to ensure TCP/IP
Jeff
"Dean J Garrett" <info@.amuletc.com> wrote in message
news:#co#$xJrEHA.452@.TK2MSFTNGP09.phx.gbl...
Hello, the SQL Server 2000 installation uses Mixed authentication, SQL and
Windows. When I try to register the SQL Server remotely from my desktop, I
enter SQL username/password. This always worked in the past with other SQL
servers.
I don't know if I'm trying to use named pipes, in fact I'd rather use only
TCP/IP. As a suggestion by another newsgroup member, I disabled Name Pipes
completely on the remote SQL server, but I still get the error message
below:
"Client unable to establish connection. Named pipes provider: The network
path was not found. Timeout expired."
Any clues?
"Rick Sawtell" <r_sawtell@.hotmail.com> wrote in message
news:#3KkuSBrEHA.332@.TK2MSFTNGP14.phx.gbl...
Sounds like a security issue to me.
Are you using SQL validation or Windows validation? If Windows
validation, then you need to ensure that your workstation is trusted by the
W2k3 server's DC.
If you are trying to connect through a named pipe, then umm. (I'm a bit
out of my element on this one), but you may need to set up some type of
Share on the W2k3 server so that the pipe is able to connect to the server.
Hope this helps, maybe someone with some additional insight can be of
service on this one.
Rick
"TJ" <tunj@.hotmail.com> wrote in message
news:eY%23g28ArEHA.1644@.tk2msftngp13.phx.gbl...
Does the client PC list the sqlserver when you try to register it or you
type it in?
"Dean J Garrett" <info@.amuletc.com> wrote in message
news:e1vxB2#qEHA.1644@.tk2msftngp13.phx.gbl...
Rick,
The SQL Server is Windows 2003 Server, the desktop is XP Pro (not
SP2).
There is no firewall on the SQL server (not supposed to be). The
server and
desktop PC are not in the same domain. Any clues?
Thanks!
"Rick Sawtell" <ricksawtell@.hotmail.com> wrote in message
news:ushY2w#qEHA.2340@.TK2MSFTNGP11.phx.gbl...[vbcol=seagreen]
> What Network Operating System (NOS) are you running?
> What service packs have been applied?
> Are both servers in the same domain?
> Do you have to go through a firewall?
> More information would be helpful.
> Rick Sawtell
> MCT, MCSD, MCDBA
>
> "Dean J Garrett" <info@.amuletc.com> wrote in message
> news:u14$po%23qEHA.2588@.TK2MSFTNGP12.phx.gbl...
SQL[vbcol=seagreen]
in[vbcol=seagreen]
network[vbcol=seagreen]
Named[vbcol=seagreen]
still
> occurs.
>

Can't connect to SQL

Hello,
We just installed SQL 2000 on a remote server. We can't connect to SQL
remotely from a desktop PC. When we try to register the SQL server in
Enterprise Mgr. we get the error:
"Client unable to establish connection. Named Pipes Provider: The network
path was not found. Timeout expired."
I checked the protocols on the SQL server and there is: TCP/IP and Named
Pipes (the default), so I disabled Named Pipes, but the error still occurs.
Anyone know what might be the problem?
Thanks!What Network Operating System (NOS) are you running?
What service packs have been applied?
Are both servers in the same domain?
Do you have to go through a firewall?
More information would be helpful.
Rick Sawtell
MCT, MCSD, MCDBA
"Dean J Garrett" <info@.amuletc.com> wrote in message
news:u14$po%23qEHA.2588@.TK2MSFTNGP12.phx.gbl...
> Hello,
> We just installed SQL 2000 on a remote server. We can't connect to SQL
> remotely from a desktop PC. When we try to register the SQL server in
> Enterprise Mgr. we get the error:
> "Client unable to establish connection. Named Pipes Provider: The network
> path was not found. Timeout expired."
> I checked the protocols on the SQL server and there is: TCP/IP and Named
> Pipes (the default), so I disabled Named Pipes, but the error still
occurs.
> Anyone know what might be the problem?
> Thanks!
>|||Rick,
The SQL Server is Windows 2003 Server, the desktop is XP Pro (not SP2).
There is no firewall on the SQL server (not supposed to be). The server and
desktop PC are not in the same domain. Any clues?
Thanks!
"Rick Sawtell" <ricksawtell@.hotmail.com> wrote in message
news:ushY2w#qEHA.2340@.TK2MSFTNGP11.phx.gbl...
> What Network Operating System (NOS) are you running?
> What service packs have been applied?
> Are both servers in the same domain?
> Do you have to go through a firewall?
> More information would be helpful.
> Rick Sawtell
> MCT, MCSD, MCDBA
>
> "Dean J Garrett" <info@.amuletc.com> wrote in message
> news:u14$po%23qEHA.2588@.TK2MSFTNGP12.phx.gbl...
> > Hello,
> >
> > We just installed SQL 2000 on a remote server. We can't connect to SQL
> > remotely from a desktop PC. When we try to register the SQL server in
> > Enterprise Mgr. we get the error:
> >
> > "Client unable to establish connection. Named Pipes Provider: The
network
> > path was not found. Timeout expired."
> >
> > I checked the protocols on the SQL server and there is: TCP/IP and Named
> > Pipes (the default), so I disabled Named Pipes, but the error still
> occurs.
> > Anyone know what might be the problem?
> >
> > Thanks!
> >
> >
>|||This is a multi-part message in MIME format.
--=_NextPart_000_0063_01C4ABE6.48846340
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Does the client PC list the sqlserver when you try to register it or you =type it in?
"Dean J Garrett" <info@.amuletc.com> wrote in message =news:e1vxB2#qEHA.1644@.tk2msftngp13.phx.gbl...
Rick,
The SQL Server is Windows 2003 Server, the desktop is XP Pro (not =SP2).
There is no firewall on the SQL server (not supposed to be). The =server and
desktop PC are not in the same domain. Any clues?
Thanks!
"Rick Sawtell" <ricksawtell@.hotmail.com> wrote in message
news:ushY2w#qEHA.2340@.TK2MSFTNGP11.phx.gbl...
> What Network Operating System (NOS) are you running?
> What service packs have been applied?
> Are both servers in the same domain?
> Do you have to go through a firewall?
>
> More information would be helpful.
>
> Rick Sawtell
> MCT, MCSD, MCDBA
>
>
>
> "Dean J Garrett" <info@.amuletc.com> wrote in message
> news:u14$po%23qEHA.2588@.TK2MSFTNGP12.phx.gbl...
> > Hello,
> >
> > We just installed SQL 2000 on a remote server. We can't connect to =SQL
> > remotely from a desktop PC. When we try to register the SQL server =in
> > Enterprise Mgr. we get the error:
> >
> > "Client unable to establish connection. Named Pipes Provider: The
network
> > path was not found. Timeout expired."
> >
> > I checked the protocols on the SQL server and there is: TCP/IP and =Named
> > Pipes (the default), so I disabled Named Pipes, but the error =still
> occurs.
> > Anyone know what might be the problem?
> >
> > Thanks!
> >
> >
>
>
--=_NextPart_000_0063_01C4ABE6.48846340
Content-Type: text/html;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
&

---

Does the client PC list the sqlserver =when you try to register it or you type it in?
"Dean J Garrett" wrote in =message news:e1vxB2#qEHA.1644=@.tk2msftngp13.phx.gbl...Rick,The SQL Server is Windows 2003 Server, the desktop is XP Pro (not =SP2).There is no firewall on the SQL server (not supposed to be). The server anddesktop PC are not in the same domain. Any clues?Thanks!"Rick Sawtell" =wrote in messagenews:ushY2w#qEHA.2340=@.TK2MSFTNGP11.phx.gbl...> What Network Operating System (NOS) are you running?> What =service packs have been applied?> Are both servers in the same =domain?> Do you have to go through a firewall?>> More information =would be helpful.>> Rick Sawtell> MCT, MCSD, MCDBA>>>> "Dean J Garrett" wrote in message> news:u14$po%23qEHA.=2588@.TK2MSFTNGP12.phx.gbl...> > Hello,> >> > We just installed SQL 2000 on a =remote server. We can't connect to SQL> > remotely from a desktop =PC. When we try to register the SQL server in> > Enterprise Mgr. we =get the error:> >> > "Client unable to establish =connection. Named Pipes Provider: Thenetwork> > path was not found. =Timeout expired."> >> > I checked the protocols on the SQL =server and there is: TCP/IP and Named> > Pipes (the default), so I =disabled Named Pipes, but the error still> occurs.> > Anyone =know what might be the problem?> >> > Thanks!> =>> >>>

---

--=_NextPart_000_0063_01C4ABE6.48846340--|||This is a multi-part message in MIME format.
--=_NextPart_000_007F_01C4ABDA.3DAB8E50
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Sounds like a security issue to me.
Are you using SQL validation or Windows validation? If Windows =validation, then you need to ensure that your workstation is trusted by =the W2k3 server's DC.
If you are trying to connect through a named pipe, then umm. (I'm a bit =out of my element on this one), but you may need to set up some type of =Share on the W2k3 server so that the pipe is able to connect to the =server.
Hope this helps, maybe someone with some additional insight can be of =service on this one.
Rick
"TJ" <tunj@.hotmail.com> wrote in message =news:eY%23g28ArEHA.1644@.tk2msftngp13.phx.gbl...
Does the client PC list the sqlserver when you try to register it or =you type it in?
"Dean J Garrett" <info@.amuletc.com> wrote in message =news:e1vxB2#qEHA.1644@.tk2msftngp13.phx.gbl...
Rick,
The SQL Server is Windows 2003 Server, the desktop is XP Pro (not =SP2).
There is no firewall on the SQL server (not supposed to be). The =server and
desktop PC are not in the same domain. Any clues?
Thanks!
"Rick Sawtell" <ricksawtell@.hotmail.com> wrote in message
news:ushY2w#qEHA.2340@.TK2MSFTNGP11.phx.gbl...
> What Network Operating System (NOS) are you running?
> What service packs have been applied?
> Are both servers in the same domain?
> Do you have to go through a firewall?
>
> More information would be helpful.
>
> Rick Sawtell
> MCT, MCSD, MCDBA
>
>
>
> "Dean J Garrett" <info@.amuletc.com> wrote in message
> news:u14$po%23qEHA.2588@.TK2MSFTNGP12.phx.gbl...
> > Hello,
> >
> > We just installed SQL 2000 on a remote server. We can't connect =to SQL
> > remotely from a desktop PC. When we try to register the SQL =server in
> > Enterprise Mgr. we get the error:
> >
> > "Client unable to establish connection. Named Pipes Provider: =The
network
> > path was not found. Timeout expired."
> >
> > I checked the protocols on the SQL server and there is: TCP/IP =and Named
> > Pipes (the default), so I disabled Named Pipes, but the error =still
> occurs.
> > Anyone know what might be the problem?
> >
> > Thanks!
> >
> >
>
>
--=_NextPart_000_007F_01C4ABDA.3DAB8E50
Content-Type: text/html;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
&

---

Sounds like a security issue to me. =
Are you using SQL validation or Windows =validation? If Windows validation, then you need to ensure that your workstation is =trusted by the W2k3 server's DC.
If you are trying to connect through a named =pipe, then umm. (I'm a bit out of my element on this one), but you may need =to set up some type of Share on the W2k3 server so that the pipe is able to =connect to the server.
Hope this helps, maybe someone with =some additional insight can be of service on this one.
Rick
"TJ" wrote in message news:eY%23g28ArEHA.=1644@.tk2msftngp13.phx.gbl...
Does the client PC list the sqlserver =when you try to register it or you type it in?
"Dean J Garrett" wrote in =message news:e1vxB2#qEHA.1644=@.tk2msftngp13.phx.gbl...Rick,The SQL Server is Windows 2003 Server, the desktop is XP Pro (not =SP2).There is no firewall on the SQL server (not supposed to be). The server anddesktop PC are not in the same domain. Any clues?Thanks!"Rick Sawtell" =wrote in messagenews:ushY2w#qEHA.2340=@.TK2MSFTNGP11.phx.gbl...> What Network Operating System (NOS) are you running?> What =service packs have been applied?> Are both servers in the same domain?> Do you have to go through a =firewall?>> More information would be helpful.>> Rick Sawtell> =MCT, MCSD, MCDBA>>>> "Dean J Garrett" wrote in message> news:u14$po%23qEHA.=2588@.TK2MSFTNGP12.phx.gbl...> > Hello,> >> > We just installed SQL 2000 on =a remote server. We can't connect to SQL> > remotely from a desktop =PC. When we try to register the SQL server in> > Enterprise =Mgr. we get the error:> >> > "Client unable to establish = connection. Named Pipes Provider: Thenetwork> > path =was not found. Timeout expired."> >> > I checked the =protocols on the SQL server and there is: TCP/IP and Named> > Pipes =(the default), so I disabled Named Pipes, but the error still> occurs.> > Anyone know what might be the problem?> >> > Thanks!> >> >>>

---

--=_NextPart_000_007F_01C4ABDA.3DAB8E50--|||Can you ping the server from the client?
Jeff
"Dean J Garrett" <info@.amuletc.com> wrote in message
news:u14$po#qEHA.2588@.TK2MSFTNGP12.phx.gbl...
> Hello,
> We just installed SQL 2000 on a remote server. We can't connect to SQL
> remotely from a desktop PC. When we try to register the SQL server in
> Enterprise Mgr. we get the error:
> "Client unable to establish connection. Named Pipes Provider: The network
> path was not found. Timeout expired."
> I checked the protocols on the SQL server and there is: TCP/IP and Named
> Pipes (the default), so I disabled Named Pipes, but the error still
occurs.
> Anyone know what might be the problem?
> Thanks!
>|||This is a multi-part message in MIME format.
--=_NextPart_000_00BC_01C4AC60.FF9D8E10
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Hello, when I try to register the remote SQL Server, it does not list it =in the pull-down because I'm using a workstation in an office, and the =SQL Server is a machine in an ISPs data center across the country. =Instead, I type in the IP address for the remote SQL box, and then enter =SQL authentication that works fine when I'm using the SQL Server =directly (via remote desktop). The SQL registration process fails due to =the error:
"Client unable to establish connection. Named pipes provider: The =network path was not found. Time-out expired."
Any clues?
"TJ" <tunj@.hotmail.com> wrote in message =news:eY#g28ArEHA.1644@.tk2msftngp13.phx.gbl...
Does the client PC list the sqlserver when you try to register it or =you type it in?
"Dean J Garrett" <info@.amuletc.com> wrote in message =news:e1vxB2#qEHA.1644@.tk2msftngp13.phx.gbl...
Rick,
The SQL Server is Windows 2003 Server, the desktop is XP Pro (not =SP2).
There is no firewall on the SQL server (not supposed to be). The =server and
desktop PC are not in the same domain. Any clues?
Thanks!
"Rick Sawtell" <ricksawtell@.hotmail.com> wrote in message
news:ushY2w#qEHA.2340@.TK2MSFTNGP11.phx.gbl...
> What Network Operating System (NOS) are you running?
> What service packs have been applied?
> Are both servers in the same domain?
> Do you have to go through a firewall?
>
> More information would be helpful.
>
> Rick Sawtell
> MCT, MCSD, MCDBA
>
>
>
> "Dean J Garrett" <info@.amuletc.com> wrote in message
> news:u14$po%23qEHA.2588@.TK2MSFTNGP12.phx.gbl...
> > Hello,
> >
> > We just installed SQL 2000 on a remote server. We can't connect =to SQL
> > remotely from a desktop PC. When we try to register the SQL =server in
> > Enterprise Mgr. we get the error:
> >
> > "Client unable to establish connection. Named Pipes Provider: =The
network
> > path was not found. Timeout expired."
> >
> > I checked the protocols on the SQL server and there is: TCP/IP =and Named
> > Pipes (the default), so I disabled Named Pipes, but the error =still
> occurs.
> > Anyone know what might be the problem?
> >
> > Thanks!
> >
> >
>
>
--=_NextPart_000_00BC_01C4AC60.FF9D8E10
Content-Type: text/html;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
&

---

Hello, when I try to register the =remote SQL Server, it does not list it in the pull-down because I'm using a =workstation in an office, and the SQL Server is a machine in an ISPs data center across =the country. Instead, I type in the IP address for the remote SQL box, and =then enter SQL authentication that works fine when I'm using the SQL Server =directly (via remote desktop). The SQL registration process fails due to the error:
"Client unable to establish connection. =Named pipes provider: The network path was not found. Time-out =expired."
Any clues?
"TJ" wrote in message news:eY#g28ArEHA.1644=@.tk2msftngp13.phx.gbl...
Does the client PC list the sqlserver =when you try to register it or you type it in?
"Dean J Garrett" wrote in =message news:e1vxB2#qEHA.1644=@.tk2msftngp13.phx.gbl...Rick,The SQL Server is Windows 2003 Server, the desktop is XP Pro (not =SP2).There is no firewall on the SQL server (not supposed to be). The server anddesktop PC are not in the same domain. Any clues?Thanks!"Rick Sawtell" =wrote in messagenews:ushY2w#qEHA.2340=@.TK2MSFTNGP11.phx.gbl...> What Network Operating System (NOS) are you running?> What =service packs have been applied?> Are both servers in the same domain?> Do you have to go through a =firewall?>> More information would be helpful.>> Rick Sawtell> =MCT, MCSD, MCDBA>>>> "Dean J Garrett" wrote in message> news:u14$po%23qEHA.=2588@.TK2MSFTNGP12.phx.gbl...> > Hello,> >> > We just installed SQL 2000 on =a remote server. We can't connect to SQL> > remotely from a desktop =PC. When we try to register the SQL server in> > Enterprise =Mgr. we get the error:> >> > "Client unable to establish = connection. Named Pipes Provider: Thenetwork> > path =was not found. Timeout expired."> >> > I checked the =protocols on the SQL server and there is: TCP/IP and Named> > Pipes =(the default), so I disabled Named Pipes, but the error still> occurs.> > Anyone know what might be the problem?> >> > Thanks!> >> >>>

---

--=_NextPart_000_00BC_01C4AC60.FF9D8E10--|||This is a multi-part message in MIME format.
--=_NextPart_000_00C8_01C4AC61.6F469B80
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Hello, the SQL Server 2000 installation uses Mixed authentication, SQL =and Windows. When I try to register the SQL Server remotely from my =desktop, I enter SQL username/password. This always worked in the past =with other SQL servers.
I don't know if I'm trying to use named pipes, in fact I'd rather use =only TCP/IP. As a suggestion by another newsgroup member, I disabled =Name Pipes completely on the remote SQL server, but I still get the =error message below:
"Client unable to establish connection. Named pipes provider: The =network path was not found. Timeout expired."
Any clues?
"Rick Sawtell" <r_sawtell@.hotmail.com> wrote in message =news:#3KkuSBrEHA.332@.TK2MSFTNGP14.phx.gbl...
Sounds like a security issue to me.
Are you using SQL validation or Windows validation? If Windows =validation, then you need to ensure that your workstation is trusted by =the W2k3 server's DC.
If you are trying to connect through a named pipe, then umm. (I'm a =bit out of my element on this one), but you may need to set up some type =of Share on the W2k3 server so that the pipe is able to connect to the =server.
Hope this helps, maybe someone with some additional insight can be =of service on this one.
Rick
"TJ" <tunj@.hotmail.com> wrote in message =news:eY%23g28ArEHA.1644@.tk2msftngp13.phx.gbl...
Does the client PC list the sqlserver when you try to register it or =you type it in?
"Dean J Garrett" <info@.amuletc.com> wrote in message =news:e1vxB2#qEHA.1644@.tk2msftngp13.phx.gbl...
Rick,
The SQL Server is Windows 2003 Server, the desktop is XP Pro (not =SP2).
There is no firewall on the SQL server (not supposed to be). The =server and
desktop PC are not in the same domain. Any clues?
Thanks!
"Rick Sawtell" <ricksawtell@.hotmail.com> wrote in message
news:ushY2w#qEHA.2340@.TK2MSFTNGP11.phx.gbl...
> What Network Operating System (NOS) are you running?
> What service packs have been applied?
> Are both servers in the same domain?
> Do you have to go through a firewall?
>
> More information would be helpful.
>
> Rick Sawtell
> MCT, MCSD, MCDBA
>
>
>
> "Dean J Garrett" <info@.amuletc.com> wrote in message
> news:u14$po%23qEHA.2588@.TK2MSFTNGP12.phx.gbl...
> > Hello,
> >
> > We just installed SQL 2000 on a remote server. We can't =connect to SQL
> > remotely from a desktop PC. When we try to register the SQL =server in
> > Enterprise Mgr. we get the error:
> >
> > "Client unable to establish connection. Named Pipes Provider: =The
network
> > path was not found. Timeout expired."
> >
> > I checked the protocols on the SQL server and there is: TCP/IP =and Named
> > Pipes (the default), so I disabled Named Pipes, but the error =still
> occurs.
> > Anyone know what might be the problem?
> >
> > Thanks!
> >
> >
>
>
--=_NextPart_000_00C8_01C4AC61.6F469B80
Content-Type: text/html;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
&

---

Hello, the SQL Server 2000 installation =uses Mixed authentication, SQL and Windows. When I try to register the SQL Server =remotely from my desktop, I enter SQL username/password. This always worked in =the past with other SQL servers.
I don't know if I'm trying to use named =pipes, in fact I'd rather use only TCP/IP. As a suggestion by another newsgroup =member, I disabled Name Pipes completely on the remote SQL server, but I still get =the error message below:
"Client unable to establish connection. =Named pipes provider: The network path was not found. Timeout expired."
Any clues?
"Rick Sawtell" =wrote in message news:#3KkuSBrEHA.332@.T=K2MSFTNGP14.phx.gbl...
Sounds like a security issue to me. =
Are you using SQL validation or Windows validation? If Windows validation, then you need to ensure that =your workstation is trusted by the W2k3 server's DC.

If you are trying to connect through a named =pipe, then umm. (I'm a bit out of my element on this one), but you may need =to set up some type of Share on the W2k3 server so that the pipe is able to =connect to the server.

Hope this helps, maybe someone =with some additional insight can be of service on this one.

Rick

"TJ" wrote in message news:eY%23g28ArEHA.=1644@.tk2msftngp13.phx.gbl...
Does the client PC list the =sqlserver when you try to register it or you type it in?
"Dean J Garrett" wrote in =message news:e1vxB2#qEHA.1644=@.tk2msftngp13.phx.gbl...Rick,The SQL Server is Windows 2003 Server, the desktop is XP Pro (not SP2).There is no firewall on the SQL server (not supposed to =be). The server anddesktop PC are not in the same domain. Any clues?Thanks!"Rick Sawtell" wrote in messagenews:ushY2w#qEHA.2340=@.TK2MSFTNGP11.phx.gbl...> What Network Operating System (NOS) are you running?> What =service packs have been applied?> Are both servers in the same domain?> Do you have to go through a =firewall?>> More information would be helpful.>> Rick Sawtell> =MCT, MCSD, MCDBA>>>> "Dean J Garrett" = wrote in = message> news:u14$po%23qEHA.=2588@.TK2MSFTNGP12.phx.gbl...> > Hello,> >> > We just installed SQL 2000 =on a remote server. We can't connect to SQL> > remotely from =a desktop PC. When we try to register the SQL server in> > = Enterprise Mgr. we get the error:> >> > ="Client unable to establish connection. Named Pipes Provider: =Thenetwork> > path was not found. Timeout expired."> >> > I =checked the protocols on the SQL server and there is: TCP/IP and =Named> > Pipes (the default), so I disabled Named Pipes, but the error = still> occurs.> > Anyone know what might be the problem?> >> > Thanks!> >> =>>>

---

--=_NextPart_000_00C8_01C4AC61.6F469B80--|||Yes, absolutely.
"Jeff Dillon" <jeff@.removeemergencyreporting.com> wrote in message
news:eGqYVuIrEHA.1272@.TK2MSFTNGP09.phx.gbl...
> Can you ping the server from the client?
> Jeff
> "Dean J Garrett" <info@.amuletc.com> wrote in message
> news:u14$po#qEHA.2588@.TK2MSFTNGP12.phx.gbl...
> > Hello,
> >
> > We just installed SQL 2000 on a remote server. We can't connect to SQL
> > remotely from a desktop PC. When we try to register the SQL server in
> > Enterprise Mgr. we get the error:
> >
> > "Client unable to establish connection. Named Pipes Provider: The
network
> > path was not found. Timeout expired."
> >
> > I checked the protocols on the SQL server and there is: TCP/IP and Named
> > Pipes (the default), so I disabled Named Pipes, but the error still
> occurs.
> > Anyone know what might be the problem?
> >
> > Thanks!
> >
> >
>|||You're still trying to use Named Pipes. Use both Client and Server Network
Utilities to ensure TCP/IP
Jeff
"Dean J Garrett" <info@.amuletc.com> wrote in message
news:#co#$xJrEHA.452@.TK2MSFTNGP09.phx.gbl...
Hello, the SQL Server 2000 installation uses Mixed authentication, SQL and
Windows. When I try to register the SQL Server remotely from my desktop, I
enter SQL username/password. This always worked in the past with other SQL
servers.
I don't know if I'm trying to use named pipes, in fact I'd rather use only
TCP/IP. As a suggestion by another newsgroup member, I disabled Name Pipes
completely on the remote SQL server, but I still get the error message
below:
"Client unable to establish connection. Named pipes provider: The network
path was not found. Timeout expired."
Any clues?
"Rick Sawtell" <r_sawtell@.hotmail.com> wrote in message
news:#3KkuSBrEHA.332@.TK2MSFTNGP14.phx.gbl...
Sounds like a security issue to me.
Are you using SQL validation or Windows validation? If Windows
validation, then you need to ensure that your workstation is trusted by the
W2k3 server's DC.
If you are trying to connect through a named pipe, then umm. (I'm a bit
out of my element on this one), but you may need to set up some type of
Share on the W2k3 server so that the pipe is able to connect to the server.
Hope this helps, maybe someone with some additional insight can be of
service on this one.
Rick
"TJ" <tunj@.hotmail.com> wrote in message
news:eY%23g28ArEHA.1644@.tk2msftngp13.phx.gbl...
Does the client PC list the sqlserver when you try to register it or you
type it in?
"Dean J Garrett" <info@.amuletc.com> wrote in message
news:e1vxB2#qEHA.1644@.tk2msftngp13.phx.gbl...
Rick,
The SQL Server is Windows 2003 Server, the desktop is XP Pro (not
SP2).
There is no firewall on the SQL server (not supposed to be). The
server and
desktop PC are not in the same domain. Any clues?
Thanks!
"Rick Sawtell" <ricksawtell@.hotmail.com> wrote in message
news:ushY2w#qEHA.2340@.TK2MSFTNGP11.phx.gbl...
> What Network Operating System (NOS) are you running?
> What service packs have been applied?
> Are both servers in the same domain?
> Do you have to go through a firewall?
>
> More information would be helpful.
>
> Rick Sawtell
> MCT, MCSD, MCDBA
>
>
>
> "Dean J Garrett" <info@.amuletc.com> wrote in message
> news:u14$po%23qEHA.2588@.TK2MSFTNGP12.phx.gbl...
> > Hello,
> >
> > We just installed SQL 2000 on a remote server. We can't connect to
SQL
> > remotely from a desktop PC. When we try to register the SQL server
in
> > Enterprise Mgr. we get the error:
> >
> > "Client unable to establish connection. Named Pipes Provider: The
network
> > path was not found. Timeout expired."
> >
> > I checked the protocols on the SQL server and there is: TCP/IP and
Named
> > Pipes (the default), so I disabled Named Pipes, but the error
still
> occurs.
> > Anyone know what might be the problem?
> >
> > Thanks!
> >
> >
>
>|||This is the strange thing, I've checked both the Client and Server Network
utils and both show Name Pipes disabled. I've rebooted the server twice.
Maybe I'll have to remove the Name Pipes protocol from the server (not sure
of the ramifications of doing that).
"Jeff Dillon" <jeff@.removeemergencyreporting.com> wrote in message
news:#tXe5#KrEHA.2724@.TK2MSFTNGP14.phx.gbl...
> You're still trying to use Named Pipes. Use both Client and Server Network
> Utilities to ensure TCP/IP
> Jeff
> "Dean J Garrett" <info@.amuletc.com> wrote in message
> news:#co#$xJrEHA.452@.TK2MSFTNGP09.phx.gbl...
> Hello, the SQL Server 2000 installation uses Mixed authentication, SQL and
> Windows. When I try to register the SQL Server remotely from my desktop, I
> enter SQL username/password. This always worked in the past with other SQL
> servers.
> I don't know if I'm trying to use named pipes, in fact I'd rather use only
> TCP/IP. As a suggestion by another newsgroup member, I disabled Name Pipes
> completely on the remote SQL server, but I still get the error message
> below:
> "Client unable to establish connection. Named pipes provider: The network
> path was not found. Timeout expired."
> Any clues?
> "Rick Sawtell" <r_sawtell@.hotmail.com> wrote in message
> news:#3KkuSBrEHA.332@.TK2MSFTNGP14.phx.gbl...
> Sounds like a security issue to me.
> Are you using SQL validation or Windows validation? If Windows
> validation, then you need to ensure that your workstation is trusted by
the
> W2k3 server's DC.
> If you are trying to connect through a named pipe, then umm. (I'm a bit
> out of my element on this one), but you may need to set up some type of
> Share on the W2k3 server so that the pipe is able to connect to the
server.
> Hope this helps, maybe someone with some additional insight can be of
> service on this one.
> Rick
> "TJ" <tunj@.hotmail.com> wrote in message
> news:eY%23g28ArEHA.1644@.tk2msftngp13.phx.gbl...
> Does the client PC list the sqlserver when you try to register it or
you
> type it in?
> "Dean J Garrett" <info@.amuletc.com> wrote in message
> news:e1vxB2#qEHA.1644@.tk2msftngp13.phx.gbl...
> Rick,
> The SQL Server is Windows 2003 Server, the desktop is XP Pro (not
> SP2).
> There is no firewall on the SQL server (not supposed to be). The
> server and
> desktop PC are not in the same domain. Any clues?
> Thanks!
>
> "Rick Sawtell" <ricksawtell@.hotmail.com> wrote in message
> news:ushY2w#qEHA.2340@.TK2MSFTNGP11.phx.gbl...
> > What Network Operating System (NOS) are you running?
> > What service packs have been applied?
> > Are both servers in the same domain?
> > Do you have to go through a firewall?
> >
> > More information would be helpful.
> >
> > Rick Sawtell
> > MCT, MCSD, MCDBA
> >
> >
> >
> > "Dean J Garrett" <info@.amuletc.com> wrote in message
> > news:u14$po%23qEHA.2588@.TK2MSFTNGP12.phx.gbl...
> > > Hello,
> > >
> > > We just installed SQL 2000 on a remote server. We can't connect
to
> SQL
> > > remotely from a desktop PC. When we try to register the SQL
server
> in
> > > Enterprise Mgr. we get the error:
> > >
> > > "Client unable to establish connection. Named Pipes Provider:
The
> network
> > > path was not found. Timeout expired."
> > >
> > > I checked the protocols on the SQL server and there is: TCP/IP
and
> Named
> > > Pipes (the default), so I disabled Named Pipes, but the error
> still
> > occurs.
> > > Anyone know what might be the problem?
> > >
> > > Thanks!
> > >
> > >
> >
> >
>
>

Can't connect to server using server management studio

Hi,
For some reason I can't connect to a (remote) SQL server using SQL server
management studio (2005) from my local SQL 2005 Server. I can connect from
numerous other PCs/Servers in my site except this one. The local SQL Server
is running Windows 2003 R2.
It will accept the username (sa) and password and just hang there. It then
pops up the error:
"is Busy
Microsoft SQL Server Management Studio is waiting for an internal operation
to complete."
Then after a while it will fail with the error:
"An exception occurred while executing a transact-sql statement or batch.
Additional information:-
A transport level error has occured when receiving results from the server"
I have checked the network setup and there are definately no firewall or
routing issues (after all you can log on - if you get the password wrong it
tells you), plus several other PCs/Servers at this site can access the
server with no problems at all. There is no firewall on the local server.
Can anyone shed any light on this? Any help much appreciated.
Thanks in advance,
-H
Can you connect to the SQL instance from that client machine at all, I mean,
if you try a different tool such as osql.exe? That should help narrow the
scope of the problem.
Linchi
"Hooopla" wrote:

> Hi,
> For some reason I can't connect to a (remote) SQL server using SQL server
> management studio (2005) from my local SQL 2005 Server. I can connect from
> numerous other PCs/Servers in my site except this one. The local SQL Server
> is running Windows 2003 R2.
> It will accept the username (sa) and password and just hang there. It then
> pops up the error:
> "is Busy
> Microsoft SQL Server Management Studio is waiting for an internal operation
> to complete."
> Then after a while it will fail with the error:
> "An exception occurred while executing a transact-sql statement or batch.
> Additional information:-
> A transport level error has occured when receiving results from the server"
> I have checked the network setup and there are definately no firewall or
> routing issues (after all you can log on - if you get the password wrong it
> tells you), plus several other PCs/Servers at this site can access the
> server with no problems at all. There is no firewall on the local server.
> Can anyone shed any light on this? Any help much appreciated.
> Thanks in advance,
> -H
>
>
|||I'm afraid osql times out aswell. I'm also trying to use a third party
package and that has the same problem
-H
"Linchi Shea" <LinchiShea@.discussions.microsoft.com> wrote in message
news:A8EC5A0C-2158-480C-8D38-3D38145577A7@.microsoft.com...[vbcol=seagreen]
> Can you connect to the SQL instance from that client machine at all, I
> mean,
> if you try a different tool such as osql.exe? That should help narrow the
> scope of the problem.
> Linchi
> "Hooopla" wrote:
|||FYI I can remote desktop successfully to the remote server.
"Linchi Shea" <LinchiShea@.discussions.microsoft.com> wrote in message
news:A8EC5A0C-2158-480C-8D38-3D38145577A7@.microsoft.com...[vbcol=seagreen]
> Can you connect to the SQL instance from that client machine at all, I
> mean,
> if you try a different tool such as osql.exe? That should help narrow the
> scope of the problem.
> Linchi
> "Hooopla" wrote:

Can't connect to server using server management studio

Hi,
For some reason I can't connect to a (remote) SQL server using SQL server
management studio (2005) from my local SQL 2005 Server. I can connect from
numerous other PCs/Servers in my site except this one. The local SQL Server
is running Windows 2003 R2.
It will accept the username (sa) and password and just hang there. It then
pops up the error:
"is Busy
Microsoft SQL Server Management Studio is waiting for an internal operation
to complete."
Then after a while it will fail with the error:
"An exception occurred while executing a transact-sql statement or batch.
Additional information:-
A transport level error has occured when receiving results from the server"
I have checked the network setup and there are definately no firewall or
routing issues (after all you can log on - if you get the password wrong it
tells you), plus several other PCs/Servers at this site can access the
server with no problems at all. There is no firewall on the local server.
Can anyone shed any light on this? Any help much appreciated.
Thanks in advance,
-HCan you connect to the SQL instance from that client machine at all, I mean,
if you try a different tool such as osql.exe? That should help narrow the
scope of the problem.
Linchi
"Hooopla" wrote:

> Hi,
> For some reason I can't connect to a (remote) SQL server using SQL server
> management studio (2005) from my local SQL 2005 Server. I can connect from
> numerous other PCs/Servers in my site except this one. The local SQL Serve
r
> is running Windows 2003 R2.
> It will accept the username (sa) and password and just hang there. It then
> pops up the error:
> "is Busy
> Microsoft SQL Server Management Studio is waiting for an internal operatio
n
> to complete."
> Then after a while it will fail with the error:
> "An exception occurred while executing a transact-sql statement or batch.
> Additional information:-
> A transport level error has occured when receiving results from the server
"
> I have checked the network setup and there are definately no firewall or
> routing issues (after all you can log on - if you get the password wrong i
t
> tells you), plus several other PCs/Servers at this site can access the
> server with no problems at all. There is no firewall on the local server.
> Can anyone shed any light on this? Any help much appreciated.
> Thanks in advance,
> -H
>
>|||I'm afraid osql times out aswell. I'm also trying to use a third party
package and that has the same problem
-H
"Linchi Shea" <LinchiShea@.discussions.microsoft.com> wrote in message
news:A8EC5A0C-2158-480C-8D38-3D38145577A7@.microsoft.com...[vbcol=seagreen]
> Can you connect to the SQL instance from that client machine at all, I
> mean,
> if you try a different tool such as osql.exe? That should help narrow the
> scope of the problem.
> Linchi
> "Hooopla" wrote:
>|||FYI I can remote desktop successfully to the remote server.
"Linchi Shea" <LinchiShea@.discussions.microsoft.com> wrote in message
news:A8EC5A0C-2158-480C-8D38-3D38145577A7@.microsoft.com...[vbcol=seagreen]
> Can you connect to the SQL instance from that client machine at all, I
> mean,
> if you try a different tool such as osql.exe? That should help narrow the
> scope of the problem.
> Linchi
> "Hooopla" wrote:
>