Home All Groups Group Topic Archive Search About

SQL 2005 and ADO.NET 1.1 connectivity problems

Author
19 Jan 2006 4:32 PM
dotnetfan
Is there a configuration trick for getting ADO.NET 1.1 applications to work
with:

2005 Express Server
2005 Standard Server

Enzo

Author
19 Jan 2006 5:52 PM
William (Bill) Vaughn
Ah, not really. The default configurations of these versions of SQL Server
are configured to prevent external access. They can be reconfigured with the
new SQL Server Surface Area Configuration tool. It can enable the protocols
and interfaces needed to see these versions as "servers" on the LAN.

See my blog for more details.

--
____________________________________
William (Bill) Vaughn
Author, Mentor, Consultant
Microsoft MVP
INETA Speaker
www.betav.com/blog/billva
www.betav.com
Please reply only to the newsgroup so that others can benefit.
This posting is provided "AS IS" with no warranties, and confers no rights.
__________________________________

<dotnetfan@newsgroups.nospam> wrote in message
Show quote
news:e50emXRHGHA.3144@TK2MSFTNGP11.phx.gbl...
> Is there a configuration trick for getting ADO.NET 1.1 applications to
> work
> with:
>
> 2005 Express Server
> 2005 Standard Server
>
> Enzo
>
>
Author
19 Jan 2006 6:39 PM
dotnetfan
Bill,

I tried the following per Microsoft:

1. Start >> All Programs >> Microsoft SQL Server 2005 >> Configuration Tools
>> SQL Server Configuration Manager

2. Open Sql Server 2005 Network Configuration >> Protocols for SQL2005

3. By default, only Shared Memory is turned on. You will likely need named
pipes for a local server and TCP/IP for remote

4. If you are accessing remotely, you need to turn on SQL Server Browser, as
well (under SQL Server 2005 Services)

5. Restart SQL Server 2005

.....while I am able to connect, I recieve an error as soon as I attempt a
SELECT

Enzo


Show quote
"William (Bill) Vaughn" <billvaRemoveT***@nwlink.com> wrote in message
news:e2RAAESHGHA.2472@TK2MSFTNGP10.phx.gbl...
> Ah, not really. The default configurations of these versions of SQL Server
> are configured to prevent external access. They can be reconfigured with
the
> new SQL Server Surface Area Configuration tool. It can enable the
protocols
> and interfaces needed to see these versions as "servers" on the LAN.
>
> See my blog for more details.
>
> --
> ____________________________________
> William (Bill) Vaughn
> Author, Mentor, Consultant
> Microsoft MVP
> INETA Speaker
> www.betav.com/blog/billva
> www.betav.com
> Please reply only to the newsgroup so that others can benefit.
> This posting is provided "AS IS" with no warranties, and confers no
rights.
> __________________________________
>
> <dotnetfan@newsgroups.nospam> wrote in message
> news:e50emXRHGHA.3144@TK2MSFTNGP11.phx.gbl...
> > Is there a configuration trick for getting ADO.NET 1.1 applications to
> > work
> > with:
> >
> > 2005 Express Server
> > 2005 Standard Server
> >
> > Enzo
> >
> >
>
>
Author
20 Jan 2006 2:59 AM
Kevin Yu [MSFT]
Hi Enzo,

Please also check if there is any firewall on the server. If an error
message occurs, could you post the exact massage? I can connect to SQL 2005
and run a SELECT successfully.

Kevin Yu
=======
"This posting is provided "AS IS" with no warranties, and confers no
rights."
Author
21 Jan 2006 6:41 PM
William (Bill) Vaughn
Did you walk through the checklist on my blog?

--
____________________________________
William (Bill) Vaughn
Author, Mentor, Consultant
Microsoft MVP
INETA Speaker
www.betav.com/blog/billva
www.betav.com
Please reply only to the newsgroup so that others can benefit.
This posting is provided "AS IS" with no warranties, and confers no rights.
__________________________________

<dotnetfan@newsgroups.nospam> wrote in message
Show quote
news:OUw8veSHGHA.3144@TK2MSFTNGP10.phx.gbl...
> Bill,
>
> I tried the following per Microsoft:
>
> 1. Start >> All Programs >> Microsoft SQL Server 2005 >> Configuration
> Tools
> >> SQL Server Configuration Manager
>
> 2. Open Sql Server 2005 Network Configuration >> Protocols for SQL2005
>
> 3. By default, only Shared Memory is turned on. You will likely need named
> pipes for a local server and TCP/IP for remote
>
> 4. If you are accessing remotely, you need to turn on SQL Server Browser,
> as
> well (under SQL Server 2005 Services)
>
> 5. Restart SQL Server 2005
>
> ....while I am able to connect, I recieve an error as soon as I attempt a
> SELECT
>
> Enzo
>
>
> "William (Bill) Vaughn" <billvaRemoveT***@nwlink.com> wrote in message
> news:e2RAAESHGHA.2472@TK2MSFTNGP10.phx.gbl...
>> Ah, not really. The default configurations of these versions of SQL
>> Server
>> are configured to prevent external access. They can be reconfigured with
> the
>> new SQL Server Surface Area Configuration tool. It can enable the
> protocols
>> and interfaces needed to see these versions as "servers" on the LAN.
>>
>> See my blog for more details.
>>
>> --
>> ____________________________________
>> William (Bill) Vaughn
>> Author, Mentor, Consultant
>> Microsoft MVP
>> INETA Speaker
>> www.betav.com/blog/billva
>> www.betav.com
>> Please reply only to the newsgroup so that others can benefit.
>> This posting is provided "AS IS" with no warranties, and confers no
> rights.
>> __________________________________
>>
>> <dotnetfan@newsgroups.nospam> wrote in message
>> news:e50emXRHGHA.3144@TK2MSFTNGP11.phx.gbl...
>> > Is there a configuration trick for getting ADO.NET 1.1 applications to
>> > work
>> > with:
>> >
>> > 2005 Express Server
>> > 2005 Standard Server
>> >
>> > Enzo
>> >
>> >
>>
>>
>
>

AddThis Social Bookmark Button