I assume you are yalking the error message when connecting to a SQL
Server2005/Express fails.

Since SQL Server2005/express is the first version of SQL Server having
default installation disabled remote connection, thus, MS made such "extra
detailed" error message. But you should not limit your thought in that box,
especially when you already know that you have enabled the SQL
Server/Express' remote connection (through "SQL Server Surface Area
Configuration"). That is, unless you haven't enable remote connection, then
do it. I f you have done that (no harm to double-check, though), you need to
look into something else, such as wrong server/database name, or wrong port
number in ConnectionString, current user does not have logging
permission..., just regard that error message as connection falure message
and do your trouble shooting.

That is, disabled remote connection is just one of the reasons you cannot
connect to SQL Server, there are more other reasons you need to learn. That
error message is more useful to users who were familiar to SQL Server2000 to
give them an extra prompt to the new default SQL Server 2005 setting.



"GaryDean" <gdeanblakely@newsgroup.nospam> wrote in message
news:uJO0xQ4jIHA.4076@TK2MSFTNGP05.phx.gbl...
> Aaron:
> I have xp pro and and Server2003 machines running in the same workgroup.
> They can all see each other via folder shares, pings, etc. I'm running
> sql server 2005 on most of them but I always get this message when I try
> to connect using a connection string that works when it's on the local
> machine.
>
> on the xp pro machines the db owner is machinename/aspnet. on server2003
> the db owner is nt authority\network service. I am trying to connect via
> asp.net website code in .net.
>
> It all worked great until I went from sql 2000 to sql 2005.
>
> What else do you need to know?
> Gary
> "Aaron Bertrand [SQL Server MVP]" <ten.xoc@dnartreb.noraa> wrote in
> message news:u72XU33jIHA.536@TK2MSFTNGP06.phx.gbl...
>> We don't have enough information to solve the problem, Gary. You see
>> this post a lot because it is a very generic error message that is
>> appropriate for dozens of different problems.
>>
>>
>>
>>
>>
>> "GaryDean" <gdeanblakely@newsgroup.nospam> wrote in message
>> news:%23BgKGz3jIHA.6084@TK2MSFTNGP06.phx.gbl...
>>> Using google I find that this is probably the most posted problem on the
>>> internet. The answer is always "check the box to allow connections."
>>> This problem started on my workgroup a year ago when I went to sql
>>> server 2005 and to get around it I just started installing sql server on
>>> all my dev boxes.
>>>
>>> But now I would like to solve the problem. Why am I getting this error
>>> when all of my sql server instances are set to allow remote connections.
>>> This was never a problem with Sql server 2000.
>>> Thanks,
>>> Gary
>>>
>>
>
>