Re: Error accessing MSDE by network (no locally) when instance created after installing Visual Studio 2005
- From: "Josep" <jmartinez@xxxxxxxx>
- Date: Mon, 23 Apr 2007 13:12:27 +0200
You were right. Thank you very much !
SQL Server Browser it's the responsible of it. I didn't know of its
existence :-(
At http://support.microsoft.com/?scid=kb%3Ben-us%3B905618&x=19&y=12 there is
good explanation how to solve it.
Josep.
"Rick Byham, (MSFT)" <rickbyh@xxxxxxxxxxxxxxxxxxxxxxxxxx> escribió en el
mensaje news:C87951E8-1823-4BD7-BC82-BB5209F4598B@xxxxxxxxxxxxxxxx
I'm not quite sure of your situation, but if SQL Server 2005 Express
Edition was installed with Visual Studio 2005, then perhaps you need to
start the SQL Server Browser service. It replaces the SQL Server 2000
system of identifying the instances on a computer.
--
Rick Byham (MSFT)
This posting is provided "AS IS" with no warranties, and confers no
rights.
"Josep" <jmartinez@xxxxxxxx> wrote in message
news:el37se1gHHA.4032@xxxxxxxxxxxxxxxxxxxxxxx
Hi,
a weird thing is happening in all development PC in the company. The
developers have some MSDE instances created in their machine, used for
different purposes. When someone create a new instance after installing
Visual Studio 2005 (some with and some without SQL Server 2005 Express
Edition) this new instance cannot be accessed by other computers while
the other instances created before (with the same configuration, where
DISABLENETWORKPROTOCOLS=0, just the instance name is different) have no
problem.
If I do a telnet on MSDE port it goes OK (don't reject the connection).
Has that happened to someone?
Thank you in advance,
Josep.
.
- References:
- Prev by Date: Re: Cannot connect to SQL express database ????
- Next by Date: Re: SQL2005 Man Studio cannot see SQL2000 Dev Ed
- Previous by thread: Re: Error accessing MSDE by network (no locally) when instance created after installing Visual Studio 2005
- Next by thread: Re: SQL2005 Man Studio cannot see SQL2000 Dev Ed
- Index(es):
Relevant Pages
|
