Error connecting to SQL 2000 remotely

We are trying to connect to a specific database on an instance of SQL 2000
(there are two instances on this server) running on W2K.
However when we try and login (the username and password are correct) we
receive the following error:
Server Error in '/SimplyWeb' Application.
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: SQL Network Interfaces, error: 26 - Error Locating Server/Instance
Specified)
Description: An unhandled exception occurred during the execution of the
current web request. Please review the stack trace for more information about
the error and where it originated in the code.
Exception Details: System.Data.SqlClient.SqlException: 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: SQL Network
Interfaces, error: 26 - Error Locating Server/Instance Specified)
Source Error:
An unhandled exception was generated during the execution of the current web
request. Information regarding the origin and location of the exception can
be identified using the exception stack trace below.
Stack Trace:
[SqlException (0x80131904): 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: SQL Network Interfaces, error: 26 -
Error Locating Server/Instance Specified)]
BusinessRules.IUsers.clsIUsers..ctor(String InUserName) +54
SimplyWebPersonnel.Login.Login.LoginClick(Object sender, ButtonEventArgs
e) +517
Infragistics.WebUI.WebDataInput.WebImageButton.OnC lick(Int32 action) +91
Infragistics.WebUI.WebControls.Buttons.WebButtonBa se.System.Web.UI.IPostBackDataHandler.RaisePostDat aChangedEvent() +18
System.Web.UI.Page.RaiseChangedEvents() +137
System.Web.UI.Page.ProcessRequestMain(Boolean
includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) +4778
Version Information: Microsoft .NET Framework Version:2.0.50727.832; ASP.NET
Version:2.0.50727.832
Any ideas or hints to allow remote connections to a SQL 2000 server?
The hint would be simple: a bit more study on SQL Server configuration. Look
into these:
1. Does the SQL Server instance allow remote connection (from other
computer?)
2. Does the SQL Server use SQL Server security - mixed security mode -
(using username/password in connectionString)?
If you can clearly answer these two questions, and still have problem, then
you have to show some code, especially the ConnectionString, and describe
more details.
"Simon" <Simon@.discussions.microsoft.com> wrote in message
news:EFC3F694-126C-473B-AD0B-AA59ACCF0411@.microsoft.com...
> We are trying to connect to a specific database on an instance of SQL 2000
> (there are two instances on this server) running on W2K.
> However when we try and login (the username and password are correct) we
> receive the following error:
> Server Error in '/SimplyWeb' Application.
> ----
> 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: SQL Network Interfaces, error: 26 - Error Locating
> Server/Instance
> Specified)
> Description: An unhandled exception occurred during the execution of the
> current web request. Please review the stack trace for more information
> about
> the error and where it originated in the code.
> Exception Details: System.Data.SqlClient.SqlException: 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: SQL Network
> Interfaces, error: 26 - Error Locating Server/Instance Specified)
> Source Error:
> An unhandled exception was generated during the execution of the current
> web
> request. Information regarding the origin and location of the exception
> can
> be identified using the exception stack trace below.
> Stack Trace:
>
> [SqlException (0x80131904): 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: SQL Network Interfaces, error: 26 -
> Error Locating Server/Instance Specified)]
> BusinessRules.IUsers.clsIUsers..ctor(String InUserName) +54
> SimplyWebPersonnel.Login.Login.LoginClick(Object sender, ButtonEventArgs
> e) +517
> Infragistics.WebUI.WebDataInput.WebImageButton.OnC lick(Int32 action) +91
> Infragistics.WebUI.WebControls.Buttons.WebButtonBa se.System.Web.UI.IPostBackDataHandler.RaisePostDat aChangedEvent()
> +18
> System.Web.UI.Page.RaiseChangedEvents() +137
> System.Web.UI.Page.ProcessRequestMain(Boolean
> includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) +4778
>
>
> ----
> Version Information: Microsoft .NET Framework Version:2.0.50727.832;
> ASP.NET
> Version:2.0.50727.832
>
> Any ideas or hints to allow remote connections to a SQL 2000 server?
|||Found out I had brackets around the server name. Now getting a different
error, this time:
(provider: Named Pipes Provider, error: 40 - Could not open a connection to
SQL Server)
SqlException (0x80131904): An error has occurred while establishing a
connection to the server.
I have checked that named pipes and TCP/IP are allowed. What should the
named pipes string look like for connecting to a local database?
"Norman Yuan" wrote:

> The hint would be simple: a bit more study on SQL Server configuration. Look
> into these:
> 1. Does the SQL Server instance allow remote connection (from other
> computer?)
> 2. Does the SQL Server use SQL Server security - mixed security mode -
> (using username/password in connectionString)?
> If you can clearly answer these two questions, and still have problem, then
> you have to show some code, especially the ConnectionString, and describe
> more details.
>
> "Simon" <Simon@.discussions.microsoft.com> wrote in message
> news:EFC3F694-126C-473B-AD0B-AA59ACCF0411@.microsoft.com...
>

Error connecting to SQL 2000 remotely

We are trying to connect to a specific database on an instance of SQL 2000
(there are two instances on this server) running on W2K.
However when we try and login (the username and password are correct) we
receive the following error:
Server Error in '/SimplyWeb' Application.
----
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: SQL Network Interfaces, error: 26 - Error Locating Server/Instance
Specified)
Description: An unhandled exception occurred during the execution of the
current web request. Please review the stack trace for more information about
the error and where it originated in the code.
Exception Details: System.Data.SqlClient.SqlException: 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: SQL Network
Interfaces, error: 26 - Error Locating Server/Instance Specified)
Source Error:
An unhandled exception was generated during the execution of the current web
request. Information regarding the origin and location of the exception can
be identified using the exception stack trace below.
Stack Trace:
[SqlException (0x80131904): 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: SQL Network Interfaces, error: 26 -
Error Locating Server/Instance Specified)]
BusinessRules.IUsers.clsIUsers..ctor(String InUserName) +54
SimplyWebPersonnel.Login.Login.LoginClick(Object sender, ButtonEventArgs
e) +517
Infragistics.WebUI.WebDataInput.WebImageButton.OnClick(Int32 action) +91
Infragistics.WebUI.WebControls.Buttons.WebButtonBase.System.Web.UI.IPostBackDataHandler.RaisePostDataChangedEvent() +18
System.Web.UI.Page.RaiseChangedEvents() +137
System.Web.UI.Page.ProcessRequestMain(Boolean
includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) +4778
----
Version Information: Microsoft .NET Framework Version:2.0.50727.832; ASP.NET
Version:2.0.50727.832
Any ideas or hints to allow remote connections to a SQL 2000 server?The hint would be simple: a bit more study on SQL Server configuration. Look
into these:
1. Does the SQL Server instance allow remote connection (from other
computer?)
2. Does the SQL Server use SQL Server security - mixed security mode -
(using username/password in connectionString)?
If you can clearly answer these two questions, and still have problem, then
you have to show some code, especially the ConnectionString, and describe
more details.
"Simon" <Simon@.discussions.microsoft.com> wrote in message
news:EFC3F694-126C-473B-AD0B-AA59ACCF0411@.microsoft.com...
> We are trying to connect to a specific database on an instance of SQL 2000
> (there are two instances on this server) running on W2K.
> However when we try and login (the username and password are correct) we
> receive the following error:
> Server Error in '/SimplyWeb' Application.
> ----
> 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: SQL Network Interfaces, error: 26 - Error Locating
> Server/Instance
> Specified)
> Description: An unhandled exception occurred during the execution of the
> current web request. Please review the stack trace for more information
> about
> the error and where it originated in the code.
> Exception Details: System.Data.SqlClient.SqlException: 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: SQL Network
> Interfaces, error: 26 - Error Locating Server/Instance Specified)
> Source Error:
> An unhandled exception was generated during the execution of the current
> web
> request. Information regarding the origin and location of the exception
> can
> be identified using the exception stack trace below.
> Stack Trace:
>
> [SqlException (0x80131904): 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: SQL Network Interfaces, error: 26 -
> Error Locating Server/Instance Specified)]
> BusinessRules.IUsers.clsIUsers..ctor(String InUserName) +54
> SimplyWebPersonnel.Login.Login.LoginClick(Object sender, ButtonEventArgs
> e) +517
> Infragistics.WebUI.WebDataInput.WebImageButton.OnClick(Int32 action) +91
> Infragistics.WebUI.WebControls.Buttons.WebButtonBase.System.Web.UI.IPostBackDataHandler.RaisePostDataChangedEvent()
> +18
> System.Web.UI.Page.RaiseChangedEvents() +137
> System.Web.UI.Page.ProcessRequestMain(Boolean
> includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) +4778
>
>
> ----
> Version Information: Microsoft .NET Framework Version:2.0.50727.832;
> ASP.NET
> Version:2.0.50727.832
>
> Any ideas or hints to allow remote connections to a SQL 2000 server?|||Found out I had brackets around the server name. Now getting a different
error, this time:
(provider: Named Pipes Provider, error: 40 - Could not open a connection to
SQL Server)
SqlException (0x80131904): An error has occurred while establishing a
connection to the server.
I have checked that named pipes and TCP/IP are allowed. What should the
named pipes string look like for connecting to a local database?
"Norman Yuan" wrote:
> The hint would be simple: a bit more study on SQL Server configuration. Look
> into these:
> 1. Does the SQL Server instance allow remote connection (from other
> computer?)
> 2. Does the SQL Server use SQL Server security - mixed security mode -
> (using username/password in connectionString)?
> If you can clearly answer these two questions, and still have problem, then
> you have to show some code, especially the ConnectionString, and describe
> more details.
>
> "Simon" <Simon@.discussions.microsoft.com> wrote in message
> news:EFC3F694-126C-473B-AD0B-AA59ACCF0411@.microsoft.com...
> > We are trying to connect to a specific database on an instance of SQL 2000
> > (there are two instances on this server) running on W2K.
> >
> > However when we try and login (the username and password are correct) we
> > receive the following error:
> >
> > Server Error in '/SimplyWeb' Application.
> > ----
> >
> > 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: SQL Network Interfaces, error: 26 - Error Locating
> > Server/Instance
> > Specified)
> > Description: An unhandled exception occurred during the execution of the
> > current web request. Please review the stack trace for more information
> > about
> > the error and where it originated in the code.
> >
> > Exception Details: System.Data.SqlClient.SqlException: 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: SQL Network
> > Interfaces, error: 26 - Error Locating Server/Instance Specified)
> >
> > Source Error:
> >
> > An unhandled exception was generated during the execution of the current
> > web
> > request. Information regarding the origin and location of the exception
> > can
> > be identified using the exception stack trace below.
> >
> > Stack Trace:
> >
> >
> > [SqlException (0x80131904): 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: SQL Network Interfaces, error: 26 -
> > Error Locating Server/Instance Specified)]
> > BusinessRules.IUsers.clsIUsers..ctor(String InUserName) +54
> > SimplyWebPersonnel.Login.Login.LoginClick(Object sender, ButtonEventArgs
> > e) +517
> > Infragistics.WebUI.WebDataInput.WebImageButton.OnClick(Int32 action) +91
> >
> > Infragistics.WebUI.WebControls.Buttons.WebButtonBase.System.Web.UI.IPostBackDataHandler.RaisePostDataChangedEvent()
> > +18
> > System.Web.UI.Page.RaiseChangedEvents() +137
> > System.Web.UI.Page.ProcessRequestMain(Boolean
> > includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) +4778
> >
> >
> >
> >
> > ----
> > Version Information: Microsoft .NET Framework Version:2.0.50727.832;
> > ASP.NET
> > Version:2.0.50727.832
> >
> >
> > Any ideas or hints to allow remote connections to a SQL 2000 server?
>

Error connecting to SQL 2000 remotely

We are trying to connect to a specific database on an instance of SQL 2000
(there are two instances on this server) running on W2K.
However when we try and login (the username and password are correct) we
receive the following error:
Server Error in '/SimplyWeb' Application.
----
--
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: SQL Network Interfaces, error: 26 - Error Locating Server/Instanc
e
Specified)
Description: An unhandled exception occurred during the execution of the
current web request. Please review the stack trace for more information abou
t
the error and where it originated in the code.
Exception Details: System.Data.SqlClient.SqlException: An error has occurred
while establishing a connection to the server. When connecting to SQL Serve
r
2005, this failure may be caused by the fact that under the default settings
SQL Server does not allow remote connections. (provider: SQL Network
Interfaces, error: 26 - Error Locating Server/Instance Specified)
Source Error:
An unhandled exception was generated during the execution of the current web
request. Information regarding the origin and location of the exception can
be identified using the exception stack trace below.
Stack Trace:
[SqlException (0x80131904): 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 no
t
allow remote connections. (provider: SQL Network Interfaces, error: 26 -
Error Locating Server/Instance Specified)]
BusinessRules.IUsers.clsIUsers..ctor(String InUserName) +54
SimplyWebPersonnel.Login.Login.LoginClick(Object sender, ButtonEventArgs
e) +517
Infragistics.WebUI.WebDataInput.WebImageButton.OnClick(Int32 action) +91
Infragistics.WebUI.WebControls.Buttons.WebButtonBase.System.Web.UI.IPostBack
DataHandler.RaisePostDataChangedEvent() +18
System.Web.UI.Page.RaiseChangedEvents() +137
System.Web.UI.Page.ProcessRequestMain(Boolean
includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) +4778
----
--
Version Information: Microsoft .NET Framework Version:2.0.50727.832; ASP.NET
Version:2.0.50727.832
Any ideas or hints to allow remote connections to a SQL 2000 server?The hint would be simple: a bit more study on SQL Server configuration. Look
into these:
1. Does the SQL Server instance allow remote connection (from other
computer?)
2. Does the SQL Server use SQL Server security - mixed security mode -
(using username/password in connectionString)?
If you can clearly answer these two questions, and still have problem, then
you have to show some code, especially the ConnectionString, and describe
more details.
"Simon" <Simon@.discussions.microsoft.com> wrote in message
news:EFC3F694-126C-473B-AD0B-AA59ACCF0411@.microsoft.com...
> We are trying to connect to a specific database on an instance of SQL 2000
> (there are two instances on this server) running on W2K.
> However when we try and login (the username and password are correct) we
> receive the following error:
> Server Error in '/SimplyWeb' Application.
> ----
--
> 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: SQL Network Interfaces, error: 26 - Error Locating
> Server/Instance
> Specified)
> Description: An unhandled exception occurred during the execution of the
> current web request. Please review the stack trace for more information
> about
> the error and where it originated in the code.
> Exception Details: System.Data.SqlClient.SqlException: 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: SQL Network
> Interfaces, error: 26 - Error Locating Server/Instance Specified)
> Source Error:
> An unhandled exception was generated during the execution of the current
> web
> request. Information regarding the origin and location of the exception
> can
> be identified using the exception stack trace below.
> Stack Trace:
>
> [SqlException (0x80131904): 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: SQL Network Interfaces, error: 26 -
> Error Locating Server/Instance Specified)]
> BusinessRules.IUsers.clsIUsers..ctor(String InUserName) +54
> SimplyWebPersonnel.Login.Login.LoginClick(Object sender, ButtonEventArgs
> e) +517
> Infragistics.WebUI.WebDataInput.WebImageButton.OnClick(Int32 action) +91
> Infragistics.WebUI.WebControls.Buttons.WebButtonBase.System.Web.UI.IPostBa
ckDataHandler.RaisePostDataChangedEvent()
> +18
> System.Web.UI.Page.RaiseChangedEvents() +137
> System.Web.UI.Page.ProcessRequestMain(Boolean
> includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) +4778
>
>
> ----
--
> Version Information: Microsoft .NET Framework Version:2.0.50727.832;
> ASP.NET
> Version:2.0.50727.832
>
> Any ideas or hints to allow remote connections to a SQL 2000 server?|||Found out I had brackets around the server name. Now getting a different
error, this time:
(provider: Named Pipes Provider, error: 40 - Could not open a connection to
SQL Server)
SqlException (0x80131904): An error has occurred while establishing a
connection to the server.
I have checked that named pipes and TCP/IP are allowed. What should the
named pipes string look like for connecting to a local database?
"Norman Yuan" wrote:

> The hint would be simple: a bit more study on SQL Server configuration. Lo
ok
> into these:
> 1. Does the SQL Server instance allow remote connection (from other
> computer?)
> 2. Does the SQL Server use SQL Server security - mixed security mode -
> (using username/password in connectionString)?
> If you can clearly answer these two questions, and still have problem, the
n
> you have to show some code, especially the ConnectionString, and describe
> more details.
>
> "Simon" <Simon@.discussions.microsoft.com> wrote in message
> news:EFC3F694-126C-473B-AD0B-AA59ACCF0411@.microsoft.com...
>

Error connecting SQL instance

We are getting an error when we try to connect to one of our instances
locally. If we connect to the server remotely, we can manage it with no
problem. However, if we try to manage it from the server itself, we get the
following error:
A connection could not be established to SERVER/INSTANCE
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 SERVER/INSTANCE node) and try again.
Our other instance works fine and the instance we are having a problem with
worked fine before, so we don't know what could be causing this. The server
is running Windows Server 2003 Standard.
Are you trying to connect to the local boxes with NT or SQL security?
"DrewB" <DrewB@.discussions.microsoft.com> wrote in message
news:7634F5DF-AB13-4E3C-90D5-E45398E782EE@.microsoft.com...
> We are getting an error when we try to connect to one of our instances
> locally. If we connect to the server remotely, we can manage it with no
> problem. However, if we try to manage it from the server itself, we get
> the
> following error:
> A connection could not be established to SERVER/INSTANCE
> 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 SERVER/INSTANCE node) and try again.
> Our other instance works fine and the instance we are having a problem
> with
> worked fine before, so we don't know what could be causing this. The
> server
> is running Windows Server 2003 Standard.

Error connecting SQL instance

We are getting an error when we try to connect to one of our instances
locally. If we connect to the server remotely, we can manage it with no
problem. However, if we try to manage it from the server itself, we get the
following error:
A connection could not be established to SERVER/INSTANCE
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 SERVER/INSTANCE node) and try again.
Our other instance works fine and the instance we are having a problem with
worked fine before, so we don't know what could be causing this. The server
is running Windows Server 2003 Standard.Are you trying to connect to the local boxes with NT or SQL security?
"DrewB" <DrewB@.discussions.microsoft.com> wrote in message
news:7634F5DF-AB13-4E3C-90D5-E45398E782EE@.microsoft.com...
> We are getting an error when we try to connect to one of our instances
> locally. If we connect to the server remotely, we can manage it with no
> problem. However, if we try to manage it from the server itself, we get
> the
> following error:
> A connection could not be established to SERVER/INSTANCE
> 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 SERVER/INSTANCE node) and try again.
> Our other instance works fine and the instance we are having a problem
> with
> worked fine before, so we don't know what could be causing this. The
> server
> is running Windows Server 2003 Standard.

Error connecting SQL instance

We are getting an error when we try to connect to one of our instances
locally. If we connect to the server remotely, we can manage it with no
problem. However, if we try to manage it from the server itself, we get the
following error:
A connection could not be established to SERVER/INSTANCE
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 SERVER/INSTANCE node) and try again.
Our other instance works fine and the instance we are having a problem with
worked fine before, so we don't know what could be causing this. The server
is running Windows Server 2003 Standard.Are you trying to connect to the local boxes with NT or SQL security?
"DrewB" <DrewB@.discussions.microsoft.com> wrote in message
news:7634F5DF-AB13-4E3C-90D5-E45398E782EE@.microsoft.com...
> We are getting an error when we try to connect to one of our instances
> locally. If we connect to the server remotely, we can manage it with no
> problem. However, if we try to manage it from the server itself, we get
> the
> following error:
> A connection could not be established to SERVER/INSTANCE
> 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 SERVER/INSTANCE node) and try again.
> Our other instance works fine and the instance we are having a problem
> with
> worked fine before, so we don't know what could be causing this. The
> server
> is running Windows Server 2003 Standard.