Error executing extended stored procedure: Invalid Parameter

When I try to connect to sql server instance I received this error:
TITLE: Microsoft SQL Server Management Studio
--
An exception occurred while executing a Transact-SQL statement or batch.
(Microsoft.SqlServer.ConnectionInfo)
--
ADDITIONAL INFORMATION:
Error executing extended stored procedure: Invalid Parameter
Error executing extended stored procedure: Invalid Parameter (Microsoft SQL
Server, Error: 22001)
when i click refresh button i am able to see my schema, but i can't see the
properties of my base and any table properties. I receive error:
TITLE: Microsoft SQL Server Management Studio
--
Cannot show requested dialog.
--
ADDITIONAL INFORMATION:
Cannot show requested dialog. (SqlMgmt)
--
An exception occurred while executing a Transact-SQL statement or batch.
(Microsoft.SqlServer.ConnectionInfo)
--
Error executing extended stored procedure: Invalid Parameter
Error executing extended stored procedure: Invalid Parameter (Microsoft SQL
Server, Error: 22001)
--
BUTTONS:
OK
--
also the registry key
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\Instance Names is
locked and can not be opened.
After a reboot the key is now readable and the 2005 instance can be
connected to without these messages.
But after a while it does it again.
does anyone have any idea what is going wrong?Hi
My guess is that you have some group policy or Anti-virus/ISD system that is
locking down this registry key.
John
"nikolakg" wrote:
> When I try to connect to sql server instance I received this error:
> TITLE: Microsoft SQL Server Management Studio
> --
> An exception occurred while executing a Transact-SQL statement or batch.
> (Microsoft.SqlServer.ConnectionInfo)
> --
> ADDITIONAL INFORMATION:
> Error executing extended stored procedure: Invalid Parameter
> Error executing extended stored procedure: Invalid Parameter (Microsoft SQL
> Server, Error: 22001)
>
> when i click refresh button i am able to see my schema, but i can't see the
> properties of my base and any table properties. I receive error:
> TITLE: Microsoft SQL Server Management Studio
> --
> Cannot show requested dialog.
> --
> ADDITIONAL INFORMATION:
> Cannot show requested dialog. (SqlMgmt)
> --
> An exception occurred while executing a Transact-SQL statement or batch.
> (Microsoft.SqlServer.ConnectionInfo)
> --
> Error executing extended stored procedure: Invalid Parameter
> Error executing extended stored procedure: Invalid Parameter (Microsoft SQL
> Server, Error: 22001)
>
> --
> BUTTONS:
> OK
> --
>
> also the registry key
> HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\Instance Names is
> locked and can not be opened.
> After a reboot the key is now readable and the 2005 instance can be
> connected to without these messages.
> But after a while it does it again.
> does anyone have any idea what is going wrong?

Error creating Database Diagrams

I'm using MS SQL Server Management Studio 2005 to manage both SQL 2000 and SQL 2005 server. When I connect to SQL 2000 Server database and try to do a Database Diagram, I got the following error:

SQL Server 2005 database diagrams and SQL Server 2000 database diagrams are created and rendered differently. Because of these differences, SQL Server Management Studio cannot work with SQL Server 2000 diagrams. Use SQL Server 2000 Enterprise Manager.

When a database containing diagrams is upgraded to SQL Server 2005, the diagrams will be upgraded the first time that the diagrams folder is opened.

You must be a member of the db_owner database role to upgrade database diagrams.

Any idea how to resolve this? I do not have admin rights to the SQL Server 2000.

Use SQL Server 2000 to administer the on the SQL Server 2000 Server stored diagrams.

Jens K. Suessmeyer.

http://www.sqlserver2005.de

Error connectiong to database

Hi,
I am designing a webpage with the DbNetGrid control on it. I am folloing
its documentation and using the following connection string to connect the
grid control to a database:
'Provider=SQLOLEDB;Driver={SQL
Server};Server=(local);Database=pubs;Tru
sted_Connection=yes;'
But DbNetGrid keeps giving me the following error. I have tried different
variations of this connection string but nothing seems to work.
[Microsoft][ODBC Driver Manager] Data source name not found and no default
driver specified (-2147467259)
Thanks.helpful sql wrote:
> Hi,
> I am designing a webpage with the DbNetGrid control on it. I am folloin
g
> its documentation and using the following connection string to connect the
> grid control to a database:
> 'Provider=SQLOLEDB;Driver={SQL
> Server};Server=(local);Database=pubs;Tru
sted_Connection=yes;'
> But DbNetGrid keeps giving me the following error. I have tried different
> variations of this connection string but nothing seems to work.
> [Microsoft][ODBC Driver Manager] Data source name not found and no default
> driver specified (-2147467259)
You have to create ODBC Data Source object as the message states.
Look for Data Sources icon in the Control Panel/Administrative Tools.
Then use its name in the connection string.|||Not neccessarily.
http://www.connectionstrings.com
And no need really to cross-post so much!
Jeff
"Sericinus hunter" <serhunt@.flash.net> wrote in message
news:a2P_f.23982$NS6.16336@.newssvr30.news.prodigy.com...
> helpful sql wrote:
> You have to create ODBC Data Source object as the message states.
> Look for Data Sources icon in the Control Panel/Administrative Tools.
> Then use its name in the connection string.|||Jeff Dillon wrote:
> Not neccessarily.
> http://www.connectionstrings.com
Thanks, I did not know that.

> And no need really to cross-post so much!
I hope your intention was to say that to the original poster.

> Jeff
> "Sericinus hunter" <serhunt@.flash.net> wrote in message
> news:a2P_f.23982$NS6.16336@.newssvr30.news.prodigy.com...
>|||No, I had already tried this website and all their examples for Sql Server
2000 connection strings. They did work from my test application but they did
not work with DbNetGrid. I had to create an ODBC Data Source in
Administrative Tools. Then it worked fine.
Thanks all for help.
"Sericinus hunter" <serhunt@.flash.net> wrote in message
news:ACR_f.3328$mu2.302@.newssvr24.news.prodigy.net...
> Jeff Dillon wrote:
> Thanks, I did not know that.
>
> I hope your intention was to say that to the original poster.
>

Error connection to SSRS via SSMS; SQL Server 2005

I am trying to connect to SQL Server Reporting Services through the
SQL Server Management Studio, however I get an error; "Cannot connect
to <<Server>>". In addition there is an HTTP status 404 error.
I am running this in a VPC with Windows 2003 Standard and SQL Server
Enterprise.
Within the VPC, I can connect to the Report Manager and view my
reports, I can access the report through web services and Visual
Studio and the ReportServer database exists in the SQL Server; I just
cannot connect to SSRS via SSMS.
Any Thoughts?
PaulWhen you connect to Report Manager via MSIE, what is the server name within
the URL?
http://servername/reports
Are you using that same name when you try to connect to SSRS via SSMS? Did
you try localhost?
--
Alain Quesnel
alainsansspam@.logiquel.com
www.logiquel.com
"Paul" <blackwell_paul@.hotmail.com> wrote in message
news:3fbe13c7-b839-45e7-8785-2657f2081c96@.e25g2000prg.googlegroups.com...
>I am trying to connect to SQL Server Reporting Services through the
> SQL Server Management Studio, however I get an error; "Cannot connect
> to <<Server>>". In addition there is an HTTP status 404 error.
> I am running this in a VPC with Windows 2003 Standard and SQL Server
> Enterprise.
> Within the VPC, I can connect to the Report Manager and view my
> reports, I can access the report through web services and Visual
> Studio and the ReportServer database exists in the SQL Server; I just
> cannot connect to SSRS via SSMS.
> Any Thoughts?
> Paul|||On Nov 19, 9:25 am, "Alain Quesnel" <alainsanss...@.logiquel.com>
wrote:
> When you connect to Report Manager via MSIE, what is the server name within
> the URL?http://servername/reports
> Are you using that same name when you try to connect to SSRS via SSMS? Did
> you try localhost?
> --
> Alain Quesnel
> alainsanss...@.logiquel.com
> www.logiquel.com
> "Paul" <blackwell_p...@.hotmail.com> wrote in message
> news:3fbe13c7-b839-45e7-8785-2657f2081c96@.e25g2000prg.googlegroups.com...
>
> >I am trying to connect to SQL Server Reporting Services through the
> > SQL Server Management Studio, however I get an error; "Cannot connect
> > to <<Server>>". In addition there is an HTTP status 404 error.
> > I am running this in a VPC with Windows 2003 Standard and SQL Server
> > Enterprise.
> > Within the VPC, I can connect to the Report Manager and view my
> > reports, I can access the report through web services and Visual
> > Studio and the ReportServer database exists in the SQL Server; I just
> > cannot connect to SSRS via SSMS.
> > Any Thoughts?
> > Paul- Hide quoted text -
> - Show quoted text -
I am using http://labs:81/reports/... I am using W2K3 Standard and
have a second website (not localhost). It uses portal 81. The server
name is LABS. Even when I use LABS:81 in the Connect to Server dialog
box of the SSMS, I get the same error.|||Can you switch to port 80 (momentarily) and try again?
--
Alain Quesnel
alainsansspam@.logiquel.com
www.logiquel.com
"Paul" <blackwell_paul@.hotmail.com> wrote in message
news:32c86d58-1ff2-4b7f-9b36-635bf7868a69@.d4g2000prg.googlegroups.com...
> On Nov 19, 9:25 am, "Alain Quesnel" <alainsanss...@.logiquel.com>
> wrote:
>> When you connect to Report Manager via MSIE, what is the server name
>> within
>> the URL?http://servername/reports
>> Are you using that same name when you try to connect to SSRS via SSMS?
>> Did
>> you try localhost?
>> --
>> Alain Quesnel
>> alainsanss...@.logiquel.com
>> www.logiquel.com
>> "Paul" <blackwell_p...@.hotmail.com> wrote in message
>> news:3fbe13c7-b839-45e7-8785-2657f2081c96@.e25g2000prg.googlegroups.com...
>>
>> >I am trying to connect to SQL Server Reporting Services through the
>> > SQL Server Management Studio, however I get an error; "Cannot connect
>> > to <<Server>>". In addition there is an HTTP status 404 error.
>> > I am running this in a VPC with Windows 2003 Standard and SQL Server
>> > Enterprise.
>> > Within the VPC, I can connect to the Report Manager and view my
>> > reports, I can access the report through web services and Visual
>> > Studio and the ReportServer database exists in the SQL Server; I just
>> > cannot connect to SSRS via SSMS.
>> > Any Thoughts?
>> > Paul- Hide quoted text -
>> - Show quoted text -
> I am using http://labs:81/reports/... I am using W2K3 Standard and
> have a second website (not localhost). It uses portal 81. The server
> name is LABS. Even when I use LABS:81 in the Connect to Server dialog
> box of the SSMS, I get the same error.
>|||On Nov 19, 1:44 pm, "Alain Quesnel" <alainsanss...@.logiquel.com>
wrote:
> Can you switch to port 80 (momentarily) and try again?
> --
> Alain Quesnel
> alainsanss...@.logiquel.com
> www.logiquel.com
> "Paul" <blackwell_p...@.hotmail.com> wrote in message
> news:32c86d58-1ff2-4b7f-9b36-635bf7868a69@.d4g2000prg.googlegroups.com...
>
> > On Nov 19, 9:25 am, "Alain Quesnel" <alainsanss...@.logiquel.com>
> > wrote:
> >> When you connect to Report Manager via MSIE, what is the server name
> >> within
> >> the URL?http://servername/reports
> >> Are you using that same name when you try to connect to SSRS via SSMS?
> >> Did
> >> you try localhost?
> >> --
> >> Alain Quesnel
> >> alainsanss...@.logiquel.com
> >>www.logiquel.com
> >> "Paul" <blackwell_p...@.hotmail.com> wrote in message
> >>news:3fbe13c7-b839-45e7-8785-2657f2081c96@.e25g2000prg.googlegroups.com...
> >> >I am trying to connect to SQL Server Reporting Services through the
> >> > SQL Server Management Studio, however I get an error; "Cannot connect
> >> > to <<Server>>". In addition there is an HTTP status 404 error.
> >> > I am running this in a VPC with Windows 2003 Standard and SQL Server
> >> > Enterprise.
> >> > Within the VPC, I can connect to the Report Manager and view my
> >> > reports, I can access the report through web services and Visual
> >> > Studio and the ReportServer database exists in the SQL Server; I just
> >> > cannot connect to SSRS via SSMS.
> >> > Any Thoughts?
> >> > Paul- Hide quoted text -
> >> - Show quoted text -
> > I am usinghttp://labs:81/reports/... I am using W2K3 Standard and
> > have a second website (not localhost). It uses portal 81. The server
> > name is LABS. Even when I use LABS:81 in the Connect to Server dialog
> > box of the SSMS, I get the same error.- Hide quoted text -
> - Show quoted text -
Problem solved!
The account that ReportServer was running under did not have the
appropriate access. In addition, the url in the config file was
incorrect; Alain, you nailed it or at least would have if I hand not
already discovered it, thanks for your expertise anyways.
Unfortunately both items I noticed early on, but "didn't think" they
were issues. I just wonder if this is the answer to many blogs that I
have seen regarding this, all resulting with no solution.

Error Connection to MSDE with SQL JDBC Driver

Connecting to SQL Server with SQL Server Driver for JDBC is OK. Trying to connect to same database, installed under MSDE, i get error "Error establishing socket".
It looks like the JDBC Driver only supports full SQL Server 2000 and not MSDE?D, What JDBC driver are you using?
If the driver you are using supported only TCP connection, make sure that TCP is enabled on the server side for MSDE.

Error connecting to SQL Server 2005 Express from Access

I am trying to connect to SQL Server 2005 Express from Access using a
DSN-less connection string, but I keep encountering errors. What happens is
that I have a login form with 2 text boxes for users to enter their username
and password. When they have entered them, they click OK and Access tries to
connect using the connection string below.
After waiting a while I get an error, however the SQL Server Login box
appears and I am able to login using my sa login. So, since I know I can
connect to SQL Server, I think the problem must be with my connection string:
stConnect = "ODBC;DRIVER={SQL Native Client}" _
& ";Trusted_Connection=no" _
& ";SERVER=CHRIS\SQLEXPRESS" _
& ";Address=10.0.0.17,1433" _
& ";Network=DBMSSOCN" _
& ";DATABASE=authorDB 2005_11_11SQL" _
& ";UID=" & stUID _
& ";PWD=" & stPWD & ";"
These are the error messages I get when I try to connect:
Connection failed:
SQLState: '08001'
SQL Server Error: 10061
[Microsoft][SQL Native Client]TCP Provider: No connection could be made
because the target machine actively refused it.
Connection failed:
SQLState: '08001'
SQL Server Error: 10061
[Microsoft][SQL Native Client]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.
Connection failed:
SQLState: 'S1T00'
SQL Server Error: 0
[Microsoft][SQL Native Client]Login timeout expired
I should mention that I was able to use a similar connection string to
connect to an MSDE instance with no problems, so if need be I can just use
MSDE. Still, I would prefer to use SQL Server Express since it doesn't have
a workload governor. Also, this is on my local machine, so there shouldn't
be any network issues.
I would appreciate any assistance that anyone can offer.
Thanks,
Chris
By default SQL Express does not accept remote connections over TCP or Named
Pipes, you need to enable that explicitly.
GertD@.SQLDev.Net
Please reply only to the newsgroups.
This posting is provided "AS IS" with no warranties, and confers no rights.
You assume all risk for your use.
Copyright SQLDev.Net 1991-2005 All rights reserved.
"Chris Burnette" <ChrisBurnette@.discussions.microsoft.com> wrote in message
news:4FAF0093-8C11-4030-8E4C-8621DE179732@.microsoft.com...
>I am trying to connect to SQL Server 2005 Express from Access using a
> DSN-less connection string, but I keep encountering errors. What happens
> is
> that I have a login form with 2 text boxes for users to enter their
> username
> and password. When they have entered them, they click OK and Access tries
> to
> connect using the connection string below.
> After waiting a while I get an error, however the SQL Server Login box
> appears and I am able to login using my sa login. So, since I know I can
> connect to SQL Server, I think the problem must be with my connection
> string:
> stConnect = "ODBC;DRIVER={SQL Native Client}" _
> & ";Trusted_Connection=no" _
> & ";SERVER=CHRIS\SQLEXPRESS" _
> & ";Address=10.0.0.17,1433" _
> & ";Network=DBMSSOCN" _
> & ";DATABASE=authorDB 2005_11_11SQL" _
> & ";UID=" & stUID _
> & ";PWD=" & stPWD & ";"
> These are the error messages I get when I try to connect:
> Connection failed:
> SQLState: '08001'
> SQL Server Error: 10061
> [Microsoft][SQL Native Client]TCP Provider: No connection could be made
> because the target machine actively refused it.
> Connection failed:
> SQLState: '08001'
> SQL Server Error: 10061
> [Microsoft][SQL Native Client]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.
> Connection failed:
> SQLState: 'S1T00'
> SQL Server Error: 0
> [Microsoft][SQL Native Client]Login timeout expired
>
> I should mention that I was able to use a similar connection string to
> connect to an MSDE instance with no problems, so if need be I can just use
> MSDE. Still, I would prefer to use SQL Server Express since it doesn't
> have
> a workload governor. Also, this is on my local machine, so there
> shouldn't
> be any network issues.
> I would appreciate any assistance that anyone can offer.
> Thanks,
> Chris
|||Gert, I know that. I started the Browser and enabled TCP/IP. Like I said, I
can connect using the sa login, and techinically it's not a remote connection
as it's on a local machine. Thanks for the response, but I already checked
and that isn't the problem.
-Chris
"Gert E.R. Drapers" wrote:

> By default SQL Express does not accept remote connections over TCP or Named
> Pipes, you need to enable that explicitly.
> GertD@.SQLDev.Net
> Please reply only to the newsgroups.
> This posting is provided "AS IS" with no warranties, and confers no rights.
> You assume all risk for your use.
> Copyright ? SQLDev.Net 1991-2005 All rights reserved.
> "Chris Burnette" <ChrisBurnette@.discussions.microsoft.com> wrote in message
> news:4FAF0093-8C11-4030-8E4C-8621DE179732@.microsoft.com...
>
>
|||I figured it out. I just needed to change the default port for TCP/IP since
MSDE was using port 1433.
-Chris
"Chris Burnette" <ChrisBurnette@.discussions.microsoft.com> wrote in message
news:BD09DFBD-66E6-411D-AA16-2A89D9672C1B@.microsoft.com...[vbcol=seagreen]
> Gert, I know that. I started the Browser and enabled TCP/IP. Like I
> said, I
> can connect using the sa login, and techinically it's not a remote
> connection
> as it's on a local machine. Thanks for the response, but I already
> checked
> and that isn't the problem.
> -Chris
> "Gert E.R. Drapers" wrote:

Error connecting to SQL Server 2005 Express from Access

I am trying to connect to SQL Server 2005 Express from Access using a
DSN-less connection string, but I keep encountering errors. What happens is
that I have a login form with 2 text boxes for users to enter their username
and password. When they have entered them, they click OK and Access tries to
connect using the connection string below.
After waiting a while I get an error, however the SQL Server Login box
appears and I am able to login using my sa login. So, since I know I can
connect to SQL Server, I think the problem must be with my connection string:
stConnect = "ODBC;DRIVER={SQL Native Client}" _
& ";Trusted_Connection=no" _
& ";SERVER=CHRIS\SQLEXPRESS" _
& ";Address=10.0.0.17,1433" _
& ";Network=DBMSSOCN" _
& ";DATABASE=authorDB 2005_11_11SQL" _
& ";UID=" & stUID _
& ";PWD=" & stPWD & ";"
These are the error messages I get when I try to connect:
Connection failed:
SQLState: '08001'
SQL Server Error: 10061
[Microsoft][SQL Native Client]TCP Provider: No connection could be made
because the target machine actively refused it.
Connection failed:
SQLState: '08001'
SQL Server Error: 10061
[Microsoft][SQL Native Client]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.
Connection failed:
SQLState: 'S1T00'
SQL Server Error: 0
[Microsoft][SQL Native Client]Login timeout expired
I should mention that I was able to use a similar connection string to
connect to an MSDE instance with no problems, so if need be I can just use
MSDE. Still, I would prefer to use SQL Server Express since it doesn't have
a workload governor. Also, this is on my local machine, so there shouldn't
be any network issues.
I would appreciate any assistance that anyone can offer.
Thanks,
Chris
By default SQL Express does not accept remote connections over TCP or Named
Pipes, you need to enable that explicitly.
GertD@.SQLDev.Net
Please reply only to the newsgroups.
This posting is provided "AS IS" with no warranties, and confers no rights.
You assume all risk for your use.
Copyright SQLDev.Net 1991-2005 All rights reserved.
"Chris Burnette" <ChrisBurnette@.discussions.microsoft.com> wrote in message
news:4FAF0093-8C11-4030-8E4C-8621DE179732@.microsoft.com...
>I am trying to connect to SQL Server 2005 Express from Access using a
> DSN-less connection string, but I keep encountering errors. What happens
> is
> that I have a login form with 2 text boxes for users to enter their
> username
> and password. When they have entered them, they click OK and Access tries
> to
> connect using the connection string below.
> After waiting a while I get an error, however the SQL Server Login box
> appears and I am able to login using my sa login. So, since I know I can
> connect to SQL Server, I think the problem must be with my connection
> string:
> stConnect = "ODBC;DRIVER={SQL Native Client}" _
> & ";Trusted_Connection=no" _
> & ";SERVER=CHRIS\SQLEXPRESS" _
> & ";Address=10.0.0.17,1433" _
> & ";Network=DBMSSOCN" _
> & ";DATABASE=authorDB 2005_11_11SQL" _
> & ";UID=" & stUID _
> & ";PWD=" & stPWD & ";"
> These are the error messages I get when I try to connect:
> Connection failed:
> SQLState: '08001'
> SQL Server Error: 10061
> [Microsoft][SQL Native Client]TCP Provider: No connection could be made
> because the target machine actively refused it.
> Connection failed:
> SQLState: '08001'
> SQL Server Error: 10061
> [Microsoft][SQL Native Client]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.
> Connection failed:
> SQLState: 'S1T00'
> SQL Server Error: 0
> [Microsoft][SQL Native Client]Login timeout expired
>
> I should mention that I was able to use a similar connection string to
> connect to an MSDE instance with no problems, so if need be I can just use
> MSDE. Still, I would prefer to use SQL Server Express since it doesn't
> have
> a workload governor. Also, this is on my local machine, so there
> shouldn't
> be any network issues.
> I would appreciate any assistance that anyone can offer.
> Thanks,
> Chris
|||Gert, I know that. I started the Browser and enabled TCP/IP. Like I said, I
can connect using the sa login, and techinically it's not a remote connection
as it's on a local machine. Thanks for the response, but I already checked
and that isn't the problem.
-Chris
"Gert E.R. Drapers" wrote:

> By default SQL Express does not accept remote connections over TCP or Named
> Pipes, you need to enable that explicitly.
> GertD@.SQLDev.Net
> Please reply only to the newsgroups.
> This posting is provided "AS IS" with no warranties, and confers no rights.
> You assume all risk for your use.
> Copyright ? SQLDev.Net 1991-2005 All rights reserved.
> "Chris Burnette" <ChrisBurnette@.discussions.microsoft.com> wrote in message
> news:4FAF0093-8C11-4030-8E4C-8621DE179732@.microsoft.com...
>
>
|||I figured it out. I just needed to change the default port for TCP/IP since
MSDE was using port 1433.
-Chris
"Chris Burnette" <ChrisBurnette@.discussions.microsoft.com> wrote in message
news:BD09DFBD-66E6-411D-AA16-2A89D9672C1B@.microsoft.com...[vbcol=seagreen]
> Gert, I know that. I started the Browser and enabled TCP/IP. Like I
> said, I
> can connect using the sa login, and techinically it's not a remote
> connection
> as it's on a local machine. Thanks for the response, but I already
> checked
> and that isn't the problem.
> -Chris
> "Gert E.R. Drapers" wrote:

Error connecting to SQL Server 2005 Express from Access

I am trying to connect to SQL Server 2005 Express from Access using a
DSN-less connection string, but I keep encountering errors. What happens is
that I have a login form with 2 text boxes for users to enter their username
and password. When they have entered them, they click OK and Access tries t
o
connect using the connection string below.
After waiting a while I get an error, however the SQL Server Login box
appears and I am able to login using my sa login. So, since I know I can
connect to SQL Server, I think the problem must be with my connection string
:
stConnect = "ODBC;DRIVER={SQL Native Client}" _
& ";Trusted_Connection=no" _
& ";SERVER=CHRIS\SQLEXPRESS" _
& ";Address=10.0.0.17,1433" _
& ";Network=DBMSSOCN" _
& ";DATABASE=authorDB 2005_11_11SQL" _
& ";UID=" & stUID _
& ";PWD=" & stPWD & ";"
These are the error messages I get when I try to connect:
Connection failed:
SQLState: '08001'
SQL Server Error: 10061
[Microsoft][SQL Native Client]TCP Provider: No connection could be m
ade
because the target machine actively refused it.
Connection failed:
SQLState: '08001'
SQL Server Error: 10061
[Microsoft][SQL Native Client]An error has occurred while establishi
ng 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.
Connection failed:
SQLState: 'S1T00'
SQL Server Error: 0
[Microsoft][SQL Native Client]Login timeout expired
I should mention that I was able to use a similar connection string to
connect to an MSDE instance with no problems, so if need be I can just use
MSDE. Still, I would prefer to use SQL Server Express since it doesn't have
a workload governor. Also, this is on my local machine, so there shouldn't
be any network issues.
I would appreciate any assistance that anyone can offer.
Thanks,
ChrisBy default SQL Express does not accept remote connections over TCP or Named
Pipes, you need to enable that explicitly.
GertD@.SQLDev.Net
Please reply only to the newsgroups.
This posting is provided "AS IS" with no warranties, and confers no rights.
You assume all risk for your use.
Copyright SQLDev.Net 1991-2005 All rights reserved.
"Chris Burnette" <ChrisBurnette@.discussions.microsoft.com> wrote in message
news:4FAF0093-8C11-4030-8E4C-8621DE179732@.microsoft.com...
>I am trying to connect to SQL Server 2005 Express from Access using a
> DSN-less connection string, but I keep encountering errors. What happens
> is
> that I have a login form with 2 text boxes for users to enter their
> username
> and password. When they have entered them, they click OK and Access tries
> to
> connect using the connection string below.
> After waiting a while I get an error, however the SQL Server Login box
> appears and I am able to login using my sa login. So, since I know I can
> connect to SQL Server, I think the problem must be with my connection
> string:
> stConnect = "ODBC;DRIVER={SQL Native Client}" _
> & ";Trusted_Connection=no" _
> & ";SERVER=CHRIS\SQLEXPRESS" _
> & ";Address=10.0.0.17,1433" _
> & ";Network=DBMSSOCN" _
> & ";DATABASE=authorDB 2005_11_11SQL" _
> & ";UID=" & stUID _
> & ";PWD=" & stPWD & ";"
> These are the error messages I get when I try to connect:
> Connection failed:
> SQLState: '08001'
> SQL Server Error: 10061
> [Microsoft][SQL Native Client]TCP Provider: No connection could be
made
> because the target machine actively refused it.
> Connection failed:
> SQLState: '08001'
> SQL Server Error: 10061
> [Microsoft][SQL Native Client]An error has occurred while establis
hing 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.
> Connection failed:
> SQLState: 'S1T00'
> SQL Server Error: 0
> [Microsoft][SQL Native Client]Login timeout expired
>
> I should mention that I was able to use a similar connection string to
> connect to an MSDE instance with no problems, so if need be I can just use
> MSDE. Still, I would prefer to use SQL Server Express since it doesn't
> have
> a workload governor. Also, this is on my local machine, so there
> shouldn't
> be any network issues.
> I would appreciate any assistance that anyone can offer.
> Thanks,
> Chris|||Gert, I know that. I started the Browser and enabled TCP/IP. Like I said,
I
can connect using the sa login, and techinically it's not a remote connectio
n
as it's on a local machine. Thanks for the response, but I already checked
and that isn't the problem.
-Chris
"Gert E.R. Drapers" wrote:

> By default SQL Express does not accept remote connections over TCP or Name
d
> Pipes, you need to enable that explicitly.
> GertD@.SQLDev.Net
> Please reply only to the newsgroups.
> This posting is provided "AS IS" with no warranties, and confers no rights
.
> You assume all risk for your use.
> Copyright ? SQLDev.Net 1991-2005 All rights reserved.
> "Chris Burnette" <ChrisBurnette@.discussions.microsoft.com> wrote in messag
e
> news:4FAF0093-8C11-4030-8E4C-8621DE179732@.microsoft.com...
>
>|||I figured it out. I just needed to change the default port for TCP/IP since
MSDE was using port 1433.
-Chris
"Chris Burnette" <ChrisBurnette@.discussions.microsoft.com> wrote in message
news:BD09DFBD-66E6-411D-AA16-2A89D9672C1B@.microsoft.com...[vbcol=seagreen]
> Gert, I know that. I started the Browser and enabled TCP/IP. Like I
> said, I
> can connect using the sa login, and techinically it's not a remote
> connection
> as it's on a local machine. Thanks for the response, but I already
> checked
> and that isn't the problem.
> -Chris
> "Gert E.R. Drapers" wrote:
>

Error connecting to sql server 2005 express

Just manged to install sql server 2005 express after two days. I have a problem now! When i try to connect to it via my browser (local database), i get the following error:

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)

I have opened the surface area configuration manager and set the connections to remote and local but it still doesnt work

Any ideas would be great

Paul

I experienced the same problem when I tried to connect to the database via "Add new connection",
but when I entered the path as localhost\sqlexpress, it worked. So you could try the same.

Hope that helps.|||

You are right. thanks a lot

Cheers

Error connecting to SQL Server 2005 - ... does not allow remote connections?

I have an ASP.NET 2.0 Website that in the connection string does not connect
to the local SQL Server but tries to connect to another SQL Server 2005
Server in another State. When I run the application from Visual Studio 2005
it connects just fine. When I published the website to the Live Server I
receive the below error:
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.
Any ideas?
Peace in Christ
Marco Napoli
http://www.ourlovingmother.orgCheck this url for troubleshooting:
http://blogs.msdn.com/sql_protocols.../22/506607.aspx
Jack Vamvas
___________________________________
Receive free SQL tips - www.ciquery.com/sqlserver.htm
___________________________________
"Marco Napoli" <marco@.avantitecnospam.com> wrote in message
news:#14p4JoaGHA.5004@.TK2MSFTNGP02.phx.gbl...
> I have an ASP.NET 2.0 Website that in the connection string does not
connect
> to the local SQL Server but tries to connect to another SQL Server 2005
> Server in another State. When I run the application from Visual Studio
2005
> it connects just fine. When I published the website to the Live Server I
> receive the below error:
> 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.
> Any ideas?
> --
> Peace in Christ
> Marco Napoli
> http://www.ourlovingmother.org
>
>|||Thank you.
Marco
"Jack Vamvas" <delete_this_bit_jack@.ciquery.com_delete> wrote in message
news:euqdnWInVNe2O8zZRVnyjg@.bt.com...
> Check this url for troubleshooting:
> http://blogs.msdn.com/sql_protocols.../22/506607.aspx
> --
> Jack Vamvas
> ___________________________________
> Receive free SQL tips - www.ciquery.com/sqlserver.htm
> ___________________________________
>
> "Marco Napoli" <marco@.avantitecnospam.com> wrote in message
> news:#14p4JoaGHA.5004@.TK2MSFTNGP02.phx.gbl...
> connect
> 2005
>

Error connecting to sql db on another computer

When I try to connect to an sql express db on another machine, I get this
message
TITLE: Connect to Server
--
Cannot connect to REIDARNOTEBOOK\SQLEXPRESS.
ADDITIONAL INFORMATION:
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) (Microsoft SQL Server, Error: -1)
For help, click:
http://go.microsoft.com/fwlink?Prod...-1&LinkId=20476
BUTTONS:
OK
The connection between the 2 machines are OK, I can connect to a SQL2000 db,
but not an sql express db
reidarTAnd do you allow "remote connections" as the error message said, don't you?
"reidarT" <reidar@.eivon.no> wrote in message
news:O%23iA%230tuGHA.4888@.TK2MSFTNGP05.phx.gbl...
> When I try to connect to an sql express db on another machine, I get this
> message
> TITLE: Connect to Server
> --
> Cannot connect to REIDARNOTEBOOK\SQLEXPRESS.
> --
> ADDITIONAL INFORMATION:
> 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) (Microsoft SQL Server, Error: -1)
> For help, click:
> http://go.microsoft.com/fwlink?Prod...-1&LinkId=20476
> --
> BUTTONS:
> OK
> The connection between the 2 machines are OK, I can connect to a SQL2000
> db,
> but not an sql express db
> reidarT
>|||reidarT wrote:
> When I try to connect to an sql express db on another machine, I get this
> message
> TITLE: Connect to Server
> --
> Cannot connect to REIDARNOTEBOOK\SQLEXPRESS.
> --
> ADDITIONAL INFORMATION:
> 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) (Microsoft SQL Server, Error: -1)
> For help, click:
> http://go.microsoft.com/fwlink?Prod...-1&LinkId=20476
> --
> BUTTONS:
> OK
> The connection between the 2 machines are OK, I can connect to a SQL2000 d
b,
> but not an sql express db
> reidarT
>
Use the Surface Area Configuration Tool to allow remote connections.
They are disabled by default.
Tracy McKibben
MCDBA
http://www.realsqlguy.com

Error connecting to sql db on another computer

When I try to connect to an sql express db on another machine, I get this
message
TITLE: Connect to Server
--
Cannot connect to REIDARNOTEBOOK\SQLEXPRESS.
--
ADDITIONAL INFORMATION:
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) (Microsoft SQL Server, Error: -1)
For help, click:
http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&EvtSrc=MSSQLServer&EvtID=-1&LinkId=20476
--
BUTTONS:
OK
The connection between the 2 machines are OK, I can connect to a SQL2000 db,
but not an sql express db
reidarTAnd do you allow "remote connections" as the error message said, don't you?
"reidarT" <reidar@.eivon.no> wrote in message
news:O%23iA%230tuGHA.4888@.TK2MSFTNGP05.phx.gbl...
> When I try to connect to an sql express db on another machine, I get this
> message
> TITLE: Connect to Server
> --
> Cannot connect to REIDARNOTEBOOK\SQLEXPRESS.
> --
> ADDITIONAL INFORMATION:
> 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) (Microsoft SQL Server, Error: -1)
> For help, click:
> http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&EvtSrc=MSSQLServer&EvtID=-1&LinkId=20476
> --
> BUTTONS:
> OK
> The connection between the 2 machines are OK, I can connect to a SQL2000
> db,
> but not an sql express db
> reidarT
>|||reidarT wrote:
> When I try to connect to an sql express db on another machine, I get this
> message
> TITLE: Connect to Server
> --
> Cannot connect to REIDARNOTEBOOK\SQLEXPRESS.
> --
> ADDITIONAL INFORMATION:
> 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) (Microsoft SQL Server, Error: -1)
> For help, click:
> http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&EvtSrc=MSSQLServer&EvtID=-1&LinkId=20476
> --
> BUTTONS:
> OK
> The connection between the 2 machines are OK, I can connect to a SQL2000 db,
> but not an sql express db
> reidarT
>
Use the Surface Area Configuration Tool to allow remote connections.
They are disabled by default.
Tracy McKibben
MCDBA
http://www.realsqlguy.com

error connecting to sql 2k from an app

Hi,
I rec'd this error.
open dbtables error: General error: Unable to write to file buffer dbtest.
when I connect to a sql 2k db from an test app.
Any ideas?
thanksCan you show the code that is trying to connect? This doesn't look like a
SQL Server error as far as I can tell.
"mecn" <mecn2002@.yahoo.com> wrote in message
news:OMglZPIPGHA.1676@.TK2MSFTNGP09.phx.gbl...
> Hi,
> I rec'd this error.
> open dbtables error: General error: Unable to write to file buffer dbtest.
> when I connect to a sql 2k db from an test app.
> Any ideas?
> thanks
>|||I don't really have the source code.
I think the same as you--windows' problem.
Everytime the app runs it generated a temp file > 2GB.
I have no idea why the temp file gets generated when the app sends a query
statment.
That is the problem
Thanks,
"Aaron Bertrand [SQL Server MVP]" <ten.xoc@.dnartreb.noraa> wrote in message
news:uwrjxcIPGHA.344@.TK2MSFTNGP11.phx.gbl...
> Can you show the code that is trying to connect? This doesn't look like a
> SQL Server error as far as I can tell.
>
>
> "mecn" <mecn2002@.yahoo.com> wrote in message
> news:OMglZPIPGHA.1676@.TK2MSFTNGP09.phx.gbl...
>

Error Connecting To SQL 2005 through Webservice using SQL Authentication

Running a SQL 2005 Database under a Default instance. i.e. (SERVERNAME) and not (SERVERNAME/SQL2005)

I have a SQL Login sa password.

When I connect to SQL 2005 from anywhere other then the webservice it works fine.

In my webservice i am using System.Data.SqlClient.

SqlConnection, SqlCommand, SqlDataAdapter are being used to called a stored procedure and return the data into a System.Data.DataSet.

I get the following error when calling DataAdapter.Fill(dataSet);

{"TCP Provider: An existing connection was forcibly closed by the remote host.\r\n\r\nLogin failed for user 'sa'."}

I have no resolutions as of yet. Any help would be greatly appreciated.

Did you mean you can connect to the SQL2005 from anywhere with 'sa' login, except webservice? You can check the status of 'sa' login in management studio under Security->Logins, also make sure the Authentication Mode is SQL Server and Windows.|||

I have checked the status of the login for user "sa" and it has access rights and grant levels to everything it needs to.

I have also created a new account specifically for that database which does not work either. Same error.

And yes my SQL 2005 Instance is configured to use both SQL Authentication and Windows Authentication. (Mixed Mode).

Any Ideas?

|||

If you encountered this issue when you're trying to establish encrypted connection , you may take a look at this article:

http://blogs.msdn.com/sql_protocols/archive/2006/07/26/678596.aspx

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 to SQL 2000 from 2005 SSMS

I can connect to all but one of my SQL 2000 SP 4 servers with SQL 2005 SP2 SSMS on my workstation. I get the following error for the one:

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) (Microsoft SQL Server, Error: 53)

I can connect to this server with the SQL 2000 Enterprise Manager from the same workstation I'm running SQL 2005 SSMS. I've also verified that tcp and named pipes are set up on the 2000 server. Can also telnet to the box with the default port #.

I'd appreciate any help you could give..

Thanks,

Dan

check the sql server 2005 is enabled for remote connection. check for firewall

http://blogs.msdn.com/sql_protocols/archive/2006/09/30/SQL-Server-2005-Remote-Connectivity-Issue-TroubleShooting.aspx

Madhu

Error connecting to SQL 2000 db "The entry MCLConnectionString has already been added"

When I try to run my application using VWD from the file system I can connect and run the application and it connects to the remote SQL 2000 server with no problem.

However, when I publish to my web server I get the folloiwng error message:

Anyone got any ideas??

Configuration Error

Description:An error occurred during the processing of a configuration file required to service this request. Please review the specific error details below and modify your configuration file appropriately.

Parser Error Message:The entry 'MCLConnectionString' has already been added.

Source Error:

Line 11: <appSettings/>Line 12: <connectionStrings>Line 13: <add name="MCLConnectionString" connectionString="Data Source=GEACO1INTR1;Initial Catalog=MCL;Persist Security Info=True;User ID=ASPNET;Password=PAUL0001" providerName="System.Data.SqlClient"/>Line 14: </connectionStrings>Line 15: <system.web>

Source File:c:\inetpub\wwwroot\mcltest\web.config Line:13

I also notice that it works if I put the connection string in each form, but as soon as I try to add it to the web.config file I get the above error.

Thanks

Paul

|||

My guess is that you have a ConnectionString with the same name on a Parent Web Application, my advise would be either to change the name of the ConnectionString, or do this:

<connectionString>
<clear/>
<add name="MCLConnectionString" connectionString="..." />
</connectionStrings
Hope this Helps,

Roberto Hernandez-Pou
http://www.rhpconsulting.net

IMPORTANT: If you use the <clear/> to clean all connectionString keys, you would also be removing the ones for the SqlAuthenticationProvider and SqlRoleProvider.

|||

To add onto Roberto's reply...

If the MCLConnectionString does already exist higher in the configuration hierarchy, you don't have to add it again to use at this level. Remove it at this level's web.config and read the connection string as normal, and the configuration API will pick it up.

Don

|||

Thanks, that sorted it. I had a copy of the web.config file left in the root directory of the web server.

Thanks again for your help

Paul

Error connecting to server

Hi all,

I am trying to connect to the server and i got this error:

TITLE: Connect to Server

Cannot connect to HST\SQLEXPRESS.

ADDITIONAL INFORMATION:

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) (Microsoft SQL Server, Error: -1)

BUT when i tried to connect to the server using the name instance (local) or my computer name directly it works.

I have to use this format in the name instance while i am connecting to the server :

computerName/SQLEXPRESS

what is the problem and how can i fix it?

thanks in advance!

hi,

Reta wrote:

TITLE: Connect to Server

Cannot connect to HST\SQLEXPRESS.

BUT when i tried to connect to the server using the name instance (local) or my computer name directly it works.

if you mean, by that, that you can connect to ComputerName or (Local) and not to ComputerName\InstanceName or (Local)\InstanceName, that means you installed a default instance and not a named instance.. is that correct?

regards

|||

what does that mean?

yes, i installed a default instance....

but i did the same installation with another pc which is work fine using local/SQLEXPRESS

Anyway, if i reinstall it with a name instance, will this fix the problem?

and what about the instance name, what should it be?

Thanks

|||

hi,

that means you are trying to connect to an istance that does not exists, the "named instance" ComputerName\SQLExpress.. so just connect to the default instance and use it..

you do not have to uninstall it and reinstall as a default instance to "fix", as there's nothing to fix.. just use the default instance as it is on that machine..

regards

|||

Thanks Andrea... I know that there is nothing to fix

But.. what why i want to use a name instance is that i wrote an SQL program that use a name instance " computerName\SQLEXPREES " in the connection string.. and the program works fine in all pc's that use it except one.. which has the error mentioned here

|||

hi,

on that "failing" pc, you have to modify the connection string to point to the default instance..

as connection string usually are not hard coded, but built on local settings collected from settings files, you usually do not have to modify the application nor to install a new named instance..

regards