SQL 2005 Default instance does not show up in server lists

MS SQL SERVER

    Sponsored Links

    Next

  • 1. Installing SQL on a remote web server
    I need to install sql 2k on a 2003 Server hosted remotely. I connect through Remote Desktop to the server and share my cd, I've had trouble install SQL in this manner before, what can I do to insure the SQL Server install properly? The Server is NOT on my network.
  • 2. New To SQL, not ACCESS
    Trying to learn how to use SQL server. When I import my ACCESS queries they turn into tables. When I write them in view, I can not save them. I need them saved so I can run them AFTER data has been added or changed in a "table". How do I do that in SQL server (2000) Thanks.
  • 3. SQL Profiler monitor only one Table
    Hi Everyone I need to configure SQL Profiler to only monitor one table. I can only configure it at the moment to monitor the whole database. Any help would be much appreciated. Thanks B
  • 4. SP4 install fails with sp_vupgrade_replication-error
    Hello, I finally have managed to install SP4 to SQL Server 2000 on Windows Server 2003 after I first installed SP1 for the server. My named instance went OK, but the default instance still fails at the end with "Error running script: sp_vupgrade_replication (1)". It is running command osql.exe -Slpc:KUVASTIN -t1200 -b -n -d master -o "H:\Program Files\Microsoft SQL Server\MSSQL\install\sp_vupgrade_replication.out" -Q "EXEC sp_vupgrade_replication @security_mode=1,@ver_old=194" -E It is failing with the last table in the database with errors like Msg 207, Level 16, State 3, Server KUVASTIN, Procedure sysmergeextendedarticlesview, Line 3 Invalid column name 'excluded_cols'. All other tables are OK, just the last one is failing. As background, the original installation of SP4 failed with timeouts. I had SP3 and some post-SP3 hotfixes already installed, and the reported version was 8.00.818. I think the failed install reset something, as the command line above refers to version 194. Anyway, as I mentioned earlier, the named instance had no problems after I had first applied SP1 for the server itself. Anyone have ideas how I can get the default instance to complete the install also ? Or is it necessary ? Thanks

SQL 2005 Default instance does not show up in server lists

Postby Brian Henry » Fri, 06 Jan 2006 23:51:51 GMT

Have a slight problem, When I view the lists of servers on our network in 
managment studio, our SQL Server 2005 default instance does not show up in 
hte list... we have two instances running... default instance and one named 
SQL2005 the SQL2005 one shows up fine with a version of 9.0, all our 8.0 
servers show up, its just the darn SQL Server 2005 default instance that 
does not show up... what do I need to change to get this to work? I already 
have it set up to accept remote connections over TCP/IP and named pipes.... 
thanks! 



RE: SQL 2005 Default instance does not show up in server lists

Postby S2VpdGggRG9ya2Vu » Sat, 07 Jan 2006 00:03:04 GMT

See  http://www.**--****.com/ 
possible reason plus the following (exerpted from another blog note I found - 
author forgotten I apologize)

Why is the local SQL Express missing? 

The answer turned out to be Windows firewall. 

The EnumAvailableSqlServers() method relies on a UDP broadcast to port 1434, 
and the UDP broadcast packet gets dropped if the Firewall is turned on.  If 
your security needs allow it you can grant a Firewall exception to the SQL 
Browser program and/or UDP port 1434.  You can change the scope of the 
exception to restrict it to the IP address of the computer itself. 

This story made me think that it may be worth summarizing the impact of 
Windows firewall on the various API for SQL Server enumeration. 

- To see a remote SQL Server the Firewall on the remote machine must not 
block the UDP packet to SQL Browser UDP port 1434. 

- To see a local SQL Server in the result of a network enumeration API the 
Firewall on the local machine must not block the UDP packet.  This applies to 
API calls like SMO EnumAvailableSqlServers, SqlDataSourceEnumerator 
GetDataSources, the default behavior of ODBC SQLBrowseConnect, or the 
SQL-DMO ListAvailableSQLServers. 

- Seeing a local server in the result of an API explicitly requesting only 
the instances from the local machine does not depend on an exception in the 
Firewall.  This applies to calls like ODBC SQLBrowseConnect combined with a 
preceding call to SQLSetConnectAttr() SQLBrowseConnect setting the 
SQL_COPT_SS_BROWSE_SERVER attribute to the local machine in order to restrict 
the enumeration to the local machine, or SQL-DMO ListInstalledInstances.







Re: SQL 2005 Default instance does not show up in server lists

Postby Brian Henry » Sat, 07 Jan 2006 06:45:43 GMT

unfortinuatly firewall is not the issue we are on a domain with the firewall 
disabled domain wide... and the change hidden property of the instance was 
already set to hide = no... so i dont know what the problem is

This is SQL Server 2005 Enterprise too btw...











Re: SQL 2005 Default instance does not show up in server lists

Postby Rick Byham [MS] » Sat, 07 Jan 2006 07:34:04 GMT

he browse list is provided by the SQL Server Browser Service. Is it running
on the computer with your default instance?
--
Rick Byham
MCDBA, MCSE, MCSA
Lead Technical Writer,
Microsoft, SQL Server Books Online
This posting is provided "as is" with
no warranties, and confers no rights.

"Brian Henry" < XXXX@XXXXX.COM > wrote in message
news: XXXX@XXXXX.COM ...



Re: SQL 2005 Default instance does not show up in server lists

Postby Brian Henry » Sat, 07 Jan 2006 14:23:36 GMT

ll services are running


"Rick Byham [MS]" < XXXX@XXXXX.COM > wrote in message
news:% XXXX@XXXXX.COM ...



RE: SQL 2005 Default instance does not show up in server lists

Postby UnlhbiBSaWVobGU » Wed, 25 Jan 2006 09:07:02 GMT

ood info... but when I opened up my UDP 1434, I only received the local
server instance in my enumeration. With the firewall off I received a list of
all servers on the network. When I scanned the ports and it during a
successful enumeration, I saw that this data was being received on random UDP
ports (the ports I saw opened were between 2700 and 2800.

I am using the built-in Windows firewall that comes with XP SP2. This is
from the firewall's error log upon blocking the inbound packets:

#Version: 1.5
#Software: Microsoft Windows Firewall
#Time Format: Local
#Fields: date time action protocol src-ip dst-ip src-port dst-port size
tcpflags tcpsyn tcpack tcpwin icmptype icmpcode info path

2006-01-23 18:49:10 DROP UDP 192.168.1.2 192.168.1.172 1434 2789 157 - - - -
- - - RECEIVE
2006-01-23 18:49:10 DROP UDP 192.168.1.4 192.168.1.172 1434 2789 145 - - - -
- - - RECEIVE

I'm not sure what the solution is, but if anyone knows how to enumerate
these servers with the XP firewall on please let me know so I can handle it.

"Keith Dorken" wrote:




Return to MS SQL SERVER

 

Who is online

Users browsing this forum: No registered users and 61 guest