|
dev
newsgroups
|
|||||||||||||||||||||||
|
|||||||||||||||||||||||
ssms not seeing local sql serverWindows Server 2003 x64 Enterprise Edition
SQL Server 2005 Developer Edition Why would SSMS run locally not see a local sql server instance , when SSMS run on another box on the network can see this instance and connect to it ? I have never had to do any config for SSMS ... it always works out-of-the-box ... What do you mean "do not see a local instance"? Do you mean when you open up
SSMS, you can't see the instance which you want to connect in the Connect to Server dialog box's Server drop down box? If its name does not appear in this list, did you try to type it yourself and connect to it this way? If you have tried this way and it does not connect, do you see an error message or something? Tell us what happends more detailed if possible. -- Show quoteHide quoteEkrem Önsoy "John A Grandy" <johnagrandy-at-gmail-dot-com> wrote in message news:ukqr24DIJHA.1308@TK2MSFTNGP02.phx.gbl... > Windows Server 2003 x64 Enterprise Edition > > SQL Server 2005 Developer Edition > > Why would SSMS run locally not see a local sql server instance , when SSMS > run on another box on the network can see this instance and connect to it > ? > > I have never had to do any config for SSMS ... it always works > out-of-the-box ... > There is nothing listed in the dropdown and attempting to browse does not
find anything. After I posted, I tried typing in the server name and I was able to connect. But I'm wondering why can't SSMS auto-discover sql servers on the network ? Show quoteHide quote "Ekrem Önsoy" <ek***@compecta.com> wrote in message news:A7AECB3D-8DFC-4D3C-B905-21F1FB79AEC9@microsoft.com... > What do you mean "do not see a local instance"? Do you mean when you open > up SSMS, you can't see the instance which you want to connect in the > Connect to Server dialog box's Server drop down box? > > If its name does not appear in this list, did you try to type it yourself > and connect to it this way? If you have tried this way and it does not > connect, do you see an error message or something? Tell us what happends > more detailed if possible. > > -- > Ekrem Önsoy > > > > > "John A Grandy" <johnagrandy-at-gmail-dot-com> wrote in message > news:ukqr24DIJHA.1308@TK2MSFTNGP02.phx.gbl... >> Windows Server 2003 x64 Enterprise Edition >> >> SQL Server 2005 Developer Edition >> >> Why would SSMS run locally not see a local sql server instance , when >> SSMS run on another box on the network can see this instance and connect >> to it ? >> >> I have never had to do any config for SSMS ... it always works >> out-of-the-box ... >> > Sometimes it happens, I mean you don't see a locally installed instance on
the drop down list. I don't know exactly why it happens, but after typing it manually and connected to that instance successfully, its recorded and can be found on the drop down list. -- Show quoteHide quoteEkrem Önsoy "John A Grandy" <johnagrandy@g-mail-dot-com> wrote in message news:e9q8h2KIJHA.4884@TK2MSFTNGP04.phx.gbl... > There is nothing listed in the dropdown and attempting to browse does not > find anything. > > After I posted, I tried typing in the server name and I was able to > connect. > > But I'm wondering why can't SSMS auto-discover sql servers on the network > ? > > "Ekrem Önsoy" <ek***@compecta.com> wrote in message > news:A7AECB3D-8DFC-4D3C-B905-21F1FB79AEC9@microsoft.com... >> What do you mean "do not see a local instance"? Do you mean when you open >> up SSMS, you can't see the instance which you want to connect in the >> Connect to Server dialog box's Server drop down box? >> >> If its name does not appear in this list, did you try to type it yourself >> and connect to it this way? If you have tried this way and it does not >> connect, do you see an error message or something? Tell us what happends >> more detailed if possible. >> >> -- >> Ekrem Önsoy >> >> >> >> >> "John A Grandy" <johnagrandy-at-gmail-dot-com> wrote in message >> news:ukqr24DIJHA.1308@TK2MSFTNGP02.phx.gbl... >>> Windows Server 2003 x64 Enterprise Edition >>> >>> SQL Server 2005 Developer Edition >>> >>> Why would SSMS run locally not see a local sql server instance , when >>> SSMS run on another box on the network can see this instance and connect >>> to it ? >>> >>> I have never had to do any config for SSMS ... it always works >>> out-of-the-box ... >>> >> > John A Grandy wrote:
Show quoteHide quote > There is nothing listed in the dropdown and attempting to browse does When you browse - the dialog comes up browsing the network. There is> not find anything. > > After I posted, I tried typing in the server name and I was able to > connect. > > But I'm wondering why can't SSMS auto-discover sql servers on the network ? > > "Ekrem Önsoy" <ek***@compecta.com> wrote in message > news:A7AECB3D-8DFC-4D3C-B905-21F1FB79AEC9@microsoft.com... >> What do you mean "do not see a local instance"? Do you mean when you >> open up SSMS, you can't see the instance which you want to connect in >> the Connect to Server dialog box's Server drop down box? >> >> If its name does not appear in this list, did you try to type it >> yourself and connect to it this way? If you have tried this way and it >> does not connect, do you see an error message or something? Tell us >> what happends more detailed if possible. >> >> -- >> Ekrem Önsoy >> >> >> >> >> "John A Grandy" <johnagrandy-at-gmail-dot-com> wrote in message >> news:ukqr24DIJHA.1308@TK2MSFTNGP02.phx.gbl... >>> Windows Server 2003 x64 Enterprise Edition >>> >>> SQL Server 2005 Developer Edition >>> >>> Why would SSMS run locally not see a local sql server instance , when >>> SSMS run on another box on the network can see this instance and >>> connect to it ? >>> >>> I have never had to do any config for SSMS ... it always works >>> out-of-the-box ... >>> >> > another tab in the dialog for local instances where you should see your local instance. Also, it's the SQL Server Browser Service that provides that info. Is the
SQL Server Browser Service on the SQL Server computer running? -- Show quoteHide quoteRick Byham (MSFT), SQL Server Books Online This posting is provided "AS IS" with no warranties, and confers no rights. "Jeffrey Williams" <jeff.williams3***@verizon.ent> wrote in message news:emMmKbLIJHA.4600@TK2MSFTNGP06.phx.gbl... > John A Grandy wrote: >> There is nothing listed in the dropdown and attempting to browse does >> not find anything. >> >> After I posted, I tried typing in the server name and I was able to >> connect. >> >> But I'm wondering why can't SSMS auto-discover sql servers on the network >> ? >> >> "Ekrem Önsoy" <ek***@compecta.com> wrote in message >> news:A7AECB3D-8DFC-4D3C-B905-21F1FB79AEC9@microsoft.com... >>> What do you mean "do not see a local instance"? Do you mean when you >>> open up SSMS, you can't see the instance which you want to connect in >>> the Connect to Server dialog box's Server drop down box? >>> >>> If its name does not appear in this list, did you try to type it >>> yourself and connect to it this way? If you have tried this way and it >>> does not connect, do you see an error message or something? Tell us >>> what happends more detailed if possible. >>> >>> -- >>> Ekrem Önsoy >>> >>> >>> >>> >>> "John A Grandy" <johnagrandy-at-gmail-dot-com> wrote in message >>> news:ukqr24DIJHA.1308@TK2MSFTNGP02.phx.gbl... >>>> Windows Server 2003 x64 Enterprise Edition >>>> >>>> SQL Server 2005 Developer Edition >>>> >>>> Why would SSMS run locally not see a local sql server instance , when >>>> SSMS run on another box on the network can see this instance and >>>> connect to it ? >>>> >>>> I have never had to do any config for SSMS ... it always works >>>> out-of-the-box ... >>>> >>> >> > > When you browse - the dialog comes up browsing the network. There is > another tab in the dialog for local instances where you should see your > local instance. Hi,
Sorry to jump in here. But I'm at my wits' end. I have the same issue - Running SQL Standard 2005 64bit - SP2 on Win2003 64bit R2 SP2. On SSMS, when I click the down arrow on the Server Name and click on <Browse for more...>, under the Local Servers tab, the Database Engine can not be collapsed even though I know there are two local instances running (one default, and one named). Based on some postings here, this can be because SQLBrowser is not running, or a firewall issue. However, windows firewall is not running, and SQLBrowser IS running on this machine. Under the Network Servers tab, everything looks okay. The Database Engine is collapsible and I can see a list of SQL instances from other machines in the domain. I can manually type in the local instance name on the Server Name field, then SSMS will connect. Other side notes: - I installed SQL 2005 Developer on an XP machine to reproduce the above issue and was not able to. On the Local Servers tab, I can see the list of local instances. - This is a big issue for me because I'm using the Outlook 2007 Database Tool to create a database (BCM data base). The second screen of this tool tries to detect local instance, so when it runs on the Windows 2003 server, it simply quits and says "Can not retrieve the list of SQL Server instances. Please make sure SQL Server is running". Of course, SQL server IS running. - On the other hand, the Outlook Database Tool runs just fine on the XP machine with SQL 2005 developer. The tool was able to see the local instance. - I have tried uninstalling and reinstalling The SQL Standard, and I have tried to use administrator as a login account for SQLBrowser, but no joy. Anyone have any insights? Thanks, Immanuel Sibero Show quoteHide quote "Rick Byham, (MSFT)" <rick***@REDMOND.CORP.MICROSOFT.COM> wrote in message news:ED8B0924-BB83-40E0-9B3E-7D623CD99C8D@microsoft.com... > Also, it's the SQL Server Browser Service that provides that info. Is the > SQL Server Browser Service on the SQL Server computer running? > -- > Rick Byham (MSFT), SQL Server Books Online > This posting is provided "AS IS" with no warranties, and confers no rights. > > "Jeffrey Williams" <jeff.williams3***@verizon.ent> wrote in message > news:emMmKbLIJHA.4600@TK2MSFTNGP06.phx.gbl... > > John A Grandy wrote: > >> There is nothing listed in the dropdown and attempting to browse does > >> not find anything. > >> > >> After I posted, I tried typing in the server name and I was able to > >> connect. > >> > >> But I'm wondering why can't SSMS auto-discover sql servers on the network > >> ? > >> > >> "Ekrem Önsoy" <ek***@compecta.com> wrote in message > >> news:A7AECB3D-8DFC-4D3C-B905-21F1FB79AEC9@microsoft.com... > >>> What do you mean "do not see a local instance"? Do you mean when you > >>> open up SSMS, you can't see the instance which you want to connect in > >>> the Connect to Server dialog box's Server drop down box? > >>> > >>> If its name does not appear in this list, did you try to type it > >>> yourself and connect to it this way? If you have tried this way and it > >>> does not connect, do you see an error message or something? Tell us > >>> what happends more detailed if possible. > >>> > >>> -- > >>> Ekrem Önsoy > >>> > >>> > >>> > >>> > >>> "John A Grandy" <johnagrandy-at-gmail-dot-com> wrote in message > >>> news:ukqr24DIJHA.1308@TK2MSFTNGP02.phx.gbl... > >>>> Windows Server 2003 x64 Enterprise Edition > >>>> > >>>> SQL Server 2005 Developer Edition > >>>> > >>>> Why would SSMS run locally not see a local sql server instance , when > >>>> SSMS run on another box on the network can see this instance and > >>>> connect to it ? > >>>> > >>>> I have never had to do any config for SSMS ... it always works > >>>> out-of-the-box ... > >>>> > >>> > >> > > > > When you browse - the dialog comes up browsing the network. There is > > another tab in the dialog for local instances where you should see your > > local instance. > I don't doubt you are seeing this, but I can't reproduce it so I'm not sure
what's going on. However, I think the local servers list is obtained by reading the registry. And the network list, is obtained by the sending out a UDP datagram and asking listening SQL Servers to respond. So I'm guessing that the local server problem is in the registry. Using RegEdit, I go to HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server \Instance Names\SQL and I see both my instances listed. But I'm not positive that's the key that is being queried. And since I don't have an affected computer I can't see the problem. -- Show quoteHide quoteRick Byham (MSFT), SQL Server Books Online This posting is provided "AS IS" with no warranties, and confers no rights. "Guess" <goah***@getlost.com> wrote in message news:uhxqjbYKJHA.5336@TK2MSFTNGP05.phx.gbl... > > Hi, > > Sorry to jump in here. But I'm at my wits' end. I have the same issue - > Running SQL Standard 2005 64bit - SP2 on Win2003 64bit R2 SP2. > > On SSMS, when I click the down arrow on the Server Name and click on > <Browse > for more...>, under the Local Servers tab, the Database Engine can not be > collapsed even though I know there are two local instances running (one > default, and one named). Based on some postings here, this can be because > SQLBrowser is not running, or a firewall issue. However, windows firewall > is not running, and SQLBrowser IS running on this machine. > > Under the Network Servers tab, everything looks okay. The Database Engine > is > collapsible and I can see a list of SQL instances from other machines in > the > domain. > > I can manually type in the local instance name on the Server Name field, > then SSMS will connect. > > > Other side notes: > - I installed SQL 2005 Developer on an XP machine to reproduce the above > issue and was not able to. On the Local Servers tab, I can see the list of > local instances. > > - This is a big issue for me because I'm using the Outlook 2007 Database > Tool to create a database (BCM data base). The second screen of this tool > tries to detect local instance, so when it runs on the Windows 2003 > server, > it simply quits and says "Can not retrieve the list of SQL Server > instances. > Please make sure SQL Server is running". Of course, SQL server IS running. > > - On the other hand, the Outlook Database Tool runs just fine on the XP > machine with SQL 2005 developer. The tool was able to see the local > instance. > > - I have tried uninstalling and reinstalling The SQL Standard, and I have > tried to use administrator as a login account for SQLBrowser, but no joy. > > Anyone have any insights? > > > > Thanks, > Immanuel Sibero > > > > "Rick Byham, (MSFT)" <rick***@REDMOND.CORP.MICROSOFT.COM> wrote in message > news:ED8B0924-BB83-40E0-9B3E-7D623CD99C8D@microsoft.com... >> Also, it's the SQL Server Browser Service that provides that info. Is the >> SQL Server Browser Service on the SQL Server computer running? >> -- >> Rick Byham (MSFT), SQL Server Books Online >> This posting is provided "AS IS" with no warranties, and confers no > rights. >> >> "Jeffrey Williams" <jeff.williams3***@verizon.ent> wrote in message >> news:emMmKbLIJHA.4600@TK2MSFTNGP06.phx.gbl... >> > John A Grandy wrote: >> >> There is nothing listed in the dropdown and attempting to browse does >> >> not find anything. >> >> >> >> After I posted, I tried typing in the server name and I was able to >> >> connect. >> >> >> >> But I'm wondering why can't SSMS auto-discover sql servers on the > network >> >> ? >> >> >> >> "Ekrem Önsoy" <ek***@compecta.com> wrote in message >> >> news:A7AECB3D-8DFC-4D3C-B905-21F1FB79AEC9@microsoft.com... >> >>> What do you mean "do not see a local instance"? Do you mean when you >> >>> open up SSMS, you can't see the instance which you want to connect in >> >>> the Connect to Server dialog box's Server drop down box? >> >>> >> >>> If its name does not appear in this list, did you try to type it >> >>> yourself and connect to it this way? If you have tried this way and >> >>> it >> >>> does not connect, do you see an error message or something? Tell us >> >>> what happends more detailed if possible. >> >>> >> >>> -- >> >>> Ekrem Önsoy >> >>> >> >>> >> >>> >> >>> >> >>> "John A Grandy" <johnagrandy-at-gmail-dot-com> wrote in message >> >>> news:ukqr24DIJHA.1308@TK2MSFTNGP02.phx.gbl... >> >>>> Windows Server 2003 x64 Enterprise Edition >> >>>> >> >>>> SQL Server 2005 Developer Edition >> >>>> >> >>>> Why would SSMS run locally not see a local sql server instance , >> >>>> when >> >>>> SSMS run on another box on the network can see this instance and >> >>>> connect to it ? >> >>>> >> >>>> I have never had to do any config for SSMS ... it always works >> >>>> out-of-the-box ... >> >>>> >> >>> >> >> >> > >> > When you browse - the dialog comes up browsing the network. There is >> > another tab in the dialog for local instances where you should see your >> > local instance. >> > > That is the right key. I just changed a value and the new (bogus) name
appeared in the SSMS list. -- Show quoteHide quoteRick Byham (MSFT), SQL Server Books Online This posting is provided "AS IS" with no warranties, and confers no rights. -- I don't doubt you are seeing this, but I can't reproduce it so I'm not sure what's going on. However, I think the local servers list is obtained by reading the registry. And the network list, is obtained by the sending out a UDP datagram and asking listening SQL Servers to respond. So I'm guessing that the local server problem is in the registry. Using RegEdit, I go to HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server \Instance Names\SQL and I see both my instances listed. But I'm not positive that's the key that is being queried. And since I don't have an affected computer I can't see the problem. -- Rick Byham (MSFT), SQL Server Books Online This posting is provided "AS IS" with no warranties, and confers no rights. -- Rick Byham (MSFT), SQL Server Books Online This posting is provided "AS IS" with no warranties, and confers no rights. "Guess" <goah***@getlost.com> wrote in message news:uhxqjbYKJHA.5336@TK2MSFTNGP05.phx.gbl... > > Hi, > > Sorry to jump in here. But I'm at my wits' end. I have the same issue - > Running SQL Standard 2005 64bit - SP2 on Win2003 64bit R2 SP2. > > On SSMS, when I click the down arrow on the Server Name and click on > <Browse > for more...>, under the Local Servers tab, the Database Engine can not be > collapsed even though I know there are two local instances running (one > default, and one named). Based on some postings here, this can be because > SQLBrowser is not running, or a firewall issue. However, windows firewall > is not running, and SQLBrowser IS running on this machine. > > Under the Network Servers tab, everything looks okay. The Database Engine > is > collapsible and I can see a list of SQL instances from other machines in > the > domain. > > I can manually type in the local instance name on the Server Name field, > then SSMS will connect. > > > Other side notes: > - I installed SQL 2005 Developer on an XP machine to reproduce the above > issue and was not able to. On the Local Servers tab, I can see the list of > local instances. > > - This is a big issue for me because I'm using the Outlook 2007 Database > Tool to create a database (BCM data base). The second screen of this tool > tries to detect local instance, so when it runs on the Windows 2003 > server, > it simply quits and says "Can not retrieve the list of SQL Server > instances. > Please make sure SQL Server is running". Of course, SQL server IS running. > > - On the other hand, the Outlook Database Tool runs just fine on the XP > machine with SQL 2005 developer. The tool was able to see the local > instance. > > - I have tried uninstalling and reinstalling The SQL Standard, and I have > tried to use administrator as a login account for SQLBrowser, but no joy. > > Anyone have any insights? > > > > Thanks, > Immanuel Sibero > > > > "Rick Byham, (MSFT)" <rick***@REDMOND.CORP.MICROSOFT.COM> wrote in message > news:ED8B0924-BB83-40E0-9B3E-7D623CD99C8D@microsoft.com... >> Also, it's the SQL Server Browser Service that provides that info. Is the >> SQL Server Browser Service on the SQL Server computer running? >> -- >> Rick Byham (MSFT), SQL Server Books Online >> This posting is provided "AS IS" with no warranties, and confers no > rights. >> >> "Jeffrey Williams" <jeff.williams3***@verizon.ent> wrote in message >> news:emMmKbLIJHA.4600@TK2MSFTNGP06.phx.gbl... >> > John A Grandy wrote: >> >> There is nothing listed in the dropdown and attempting to browse does >> >> not find anything. >> >> >> >> After I posted, I tried typing in the server name and I was able to >> >> connect. >> >> >> >> But I'm wondering why can't SSMS auto-discover sql servers on the > network >> >> ? >> >> >> >> "Ekrem Önsoy" <ek***@compecta.com> wrote in message >> >> news:A7AECB3D-8DFC-4D3C-B905-21F1FB79AEC9@microsoft.com... >> >>> What do you mean "do not see a local instance"? Do you mean when you >> >>> open up SSMS, you can't see the instance which you want to connect in >> >>> the Connect to Server dialog box's Server drop down box? >> >>> >> >>> If its name does not appear in this list, did you try to type it >> >>> yourself and connect to it this way? If you have tried this way and >> >>> it >> >>> does not connect, do you see an error message or something? Tell us >> >>> what happends more detailed if possible. >> >>> >> >>> -- >> >>> Ekrem Önsoy >> >>> >> >>> >> >>> >> >>> >> >>> "John A Grandy" <johnagrandy-at-gmail-dot-com> wrote in message >> >>> news:ukqr24DIJHA.1308@TK2MSFTNGP02.phx.gbl... >> >>>> Windows Server 2003 x64 Enterprise Edition >> >>>> >> >>>> SQL Server 2005 Developer Edition >> >>>> >> >>>> Why would SSMS run locally not see a local sql server instance , >> >>>> when >> >>>> SSMS run on another box on the network can see this instance and >> >>>> connect to it ? >> >>>> >> >>>> I have never had to do any config for SSMS ... it always works >> >>>> out-of-the-box ... >> >>>> >> >>> >> >> >> > >> > When you browse - the dialog comes up browsing the network. There is >> > another tab in the dialog for local instances where you should see your >> > local instance. >> > > Rick,
Thank you much for the quick reply. I will try this and report back one way or the other. Again, thanks. Immanuel Sibero Show quoteHide quote "Rick Byham, (MSFT)" <rick***@REDMOND.CORP.MICROSOFT.COM> wrote in message news:B5FDC6F5-0D23-43F7-8400-2DEF1C3172B5@microsoft.com... > That is the right key. I just changed a value and the new (bogus) name > appeared in the SSMS list. > -- > Rick Byham (MSFT), SQL Server Books Online > This posting is provided "AS IS" with no warranties, and confers no rights. > > -- > > I don't doubt you are seeing this, but I can't reproduce it so I'm not sure > what's going on. > However, I think the local servers list is obtained by reading the registry. > And the network list, is obtained by the sending out a UDP datagram and > asking listening SQL Servers to respond. So I'm guessing that the local > server problem is in the registry. > Using RegEdit, I go to HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL > Server \Instance Names\SQL and I see both my instances listed. > But I'm not positive that's the key that is being queried. And since I don't > have an affected computer I can't see the problem. > -- > Rick Byham (MSFT), SQL Server Books Online > This posting is provided "AS IS" with no warranties, and confers no rights. > > > -- > Rick Byham (MSFT), SQL Server Books Online > This posting is provided "AS IS" with no warranties, and confers no rights. > > "Guess" <goah***@getlost.com> wrote in message > news:uhxqjbYKJHA.5336@TK2MSFTNGP05.phx.gbl... > > > > Hi, > > > > Sorry to jump in here. But I'm at my wits' end. I have the same issue - > > Running SQL Standard 2005 64bit - SP2 on Win2003 64bit R2 SP2. > > > > On SSMS, when I click the down arrow on the Server Name and click on > > <Browse > > for more...>, under the Local Servers tab, the Database Engine can not be > > collapsed even though I know there are two local instances running (one > > default, and one named). Based on some postings here, this can be because > > SQLBrowser is not running, or a firewall issue. However, windows firewall > > is not running, and SQLBrowser IS running on this machine. > > > > Under the Network Servers tab, everything looks okay. The Database Engine > > is > > collapsible and I can see a list of SQL instances from other machines in > > the > > domain. > > > > I can manually type in the local instance name on the Server Name field, > > then SSMS will connect. > > > > > > Other side notes: > > - I installed SQL 2005 Developer on an XP machine to reproduce the above > > issue and was not able to. On the Local Servers tab, I can see the list of > > local instances. > > > > - This is a big issue for me because I'm using the Outlook 2007 Database > > Tool to create a database (BCM data base). The second screen of this tool > > tries to detect local instance, so when it runs on the Windows 2003 > > server, > > it simply quits and says "Can not retrieve the list of SQL Server > > instances. > > Please make sure SQL Server is running". Of course, SQL server IS running. > > > > - On the other hand, the Outlook Database Tool runs just fine on the XP > > machine with SQL 2005 developer. The tool was able to see the local > > instance. > > > > - I have tried uninstalling and reinstalling The SQL Standard, and I have > > tried to use administrator as a login account for SQLBrowser, but no joy. > > > > Anyone have any insights? > > > > > > > > Thanks, > > Immanuel Sibero > > > > > > > > "Rick Byham, (MSFT)" <rick***@REDMOND.CORP.MICROSOFT.COM> wrote in message > > news:ED8B0924-BB83-40E0-9B3E-7D623CD99C8D@microsoft.com... > >> Also, it's the SQL Server Browser Service that provides that info. Is the > >> SQL Server Browser Service on the SQL Server computer running? > >> -- > >> Rick Byham (MSFT), SQL Server Books Online > >> This posting is provided "AS IS" with no warranties, and confers no > > rights. > >> > >> "Jeffrey Williams" <jeff.williams3***@verizon.ent> wrote in message > >> news:emMmKbLIJHA.4600@TK2MSFTNGP06.phx.gbl... > >> > John A Grandy wrote: > >> >> There is nothing listed in the dropdown and attempting to browse does > >> >> not find anything. > >> >> > >> >> After I posted, I tried typing in the server name and I was able to > >> >> connect. > >> >> > >> >> But I'm wondering why can't SSMS auto-discover sql servers on the > > network > >> >> ? > >> >> > >> >> "Ekrem Önsoy" <ek***@compecta.com> wrote in message > >> >> news:A7AECB3D-8DFC-4D3C-B905-21F1FB79AEC9@microsoft.com... > >> >>> What do you mean "do not see a local instance"? Do you mean when you > >> >>> open up SSMS, you can't see the instance which you want to connect in > >> >>> the Connect to Server dialog box's Server drop down box? > >> >>> > >> >>> If its name does not appear in this list, did you try to type it > >> >>> yourself and connect to it this way? If you have tried this way and > >> >>> it > >> >>> does not connect, do you see an error message or something? Tell us > >> >>> what happends more detailed if possible. > >> >>> > >> >>> -- > >> >>> Ekrem Önsoy > >> >>> > >> >>> > >> >>> > >> >>> > >> >>> "John A Grandy" <johnagrandy-at-gmail-dot-com> wrote in message > >> >>> news:ukqr24DIJHA.1308@TK2MSFTNGP02.phx.gbl... > >> >>>> Windows Server 2003 x64 Enterprise Edition > >> >>>> > >> >>>> SQL Server 2005 Developer Edition > >> >>>> > >> >>>> Why would SSMS run locally not see a local sql server instance , > >> >>>> when > >> >>>> SSMS run on another box on the network can see this instance and > >> >>>> connect to it ? > >> >>>> > >> >>>> I have never had to do any config for SSMS ... it always works > >> >>>> out-of-the-box ... > >> >>>> > >> >>> > >> >> > >> > > >> > When you browse - the dialog comes up browsing the network. There is > >> > another tab in the dialog for local instances where you should see your > >> > local instance. > >> > > > > > Rick,
I'm reporting back on this issue. I played around with the registry key you mentioned. I observed the same behavior as you did on the SQL 2005 Developer installed on an XP machine. But strangely enough, I could not reproduce this with the SQL 2005 Standard 64-bit, running on Win2003 R2 64-bit. On this server machine, the instance list is actually on the registry but apparently is ignored on the SSMS list (so it doesnt matter whether or not I change them, it simply doesnt show on the SSMS list). Here's something more: - Since my Win2003 R2 64-bit installation is a new one and had some time on my hand, I blew it away, reinstalled from scratch down to the partitions, and then installed SQL 2005 32bit Developer version. To my surprise, the instance list now shows up. - And... regarding the big issue I had with Outlook 2007 Database Tool to create a database (BCM data base)... Well, this tool can now detect the local instance and can proceed to do what it needs to do, thus solves my problem. The issue of the instance list does not show in SSMS is not my big problem, especially since I can just type in the instance name and things would work (i.e the original subject of this thread). My big problem is with the Outlook Database Tool that apparently can not detect the local instance when running on the 64bit SQL Edition. I'm now installing the SQL Standard 2005 32bit and see if it works for me (i.e. since the Developer edition seems to be working). One quick question for you though: IS it okay to run SQL Standard 32bit on Windows 2003 R2 64bit?? The installation runs just fine, so I assume there should be no issue. Thanks for your time, Immanuel Sibero Show quoteHide quote "Rick Byham, (MSFT)" <rick***@REDMOND.CORP.MICROSOFT.COM> wrote in message news:B5FDC6F5-0D23-43F7-8400-2DEF1C3172B5@microsoft.com... > That is the right key. I just changed a value and the new (bogus) name > appeared in the SSMS list. > -- > Rick Byham (MSFT), SQL Server Books Online > This posting is provided "AS IS" with no warranties, and confers no rights. > > -- > > I don't doubt you are seeing this, but I can't reproduce it so I'm not sure > what's going on. > However, I think the local servers list is obtained by reading the registry. > And the network list, is obtained by the sending out a UDP datagram and > asking listening SQL Servers to respond. So I'm guessing that the local > server problem is in the registry. > Using RegEdit, I go to HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL > Server \Instance Names\SQL and I see both my instances listed. > But I'm not positive that's the key that is being queried. And since I don't > have an affected computer I can't see the problem. > -- > Rick Byham (MSFT), SQL Server Books Online > This posting is provided "AS IS" with no warranties, and confers no rights. > > > -- > Rick Byham (MSFT), SQL Server Books Online > This posting is provided "AS IS" with no warranties, and confers no rights. > > "Guess" <goah***@getlost.com> wrote in message > news:uhxqjbYKJHA.5336@TK2MSFTNGP05.phx.gbl... > > > > Hi, > > > > Sorry to jump in here. But I'm at my wits' end. I have the same issue - > > Running SQL Standard 2005 64bit - SP2 on Win2003 64bit R2 SP2. > > > > On SSMS, when I click the down arrow on the Server Name and click on > > <Browse > > for more...>, under the Local Servers tab, the Database Engine can not be > > collapsed even though I know there are two local instances running (one > > default, and one named). Based on some postings here, this can be because > > SQLBrowser is not running, or a firewall issue. However, windows firewall > > is not running, and SQLBrowser IS running on this machine. > > > > Under the Network Servers tab, everything looks okay. The Database Engine > > is > > collapsible and I can see a list of SQL instances from other machines in > > the > > domain. > > > > I can manually type in the local instance name on the Server Name field, > > then SSMS will connect. > > > > > > Other side notes: > > - I installed SQL 2005 Developer on an XP machine to reproduce the above > > issue and was not able to. On the Local Servers tab, I can see the list of > > local instances. > > > > - This is a big issue for me because I'm using the Outlook 2007 Database > > Tool to create a database (BCM data base). The second screen of this tool > > tries to detect local instance, so when it runs on the Windows 2003 > > server, > > it simply quits and says "Can not retrieve the list of SQL Server > > instances. > > Please make sure SQL Server is running". Of course, SQL server IS running. > > > > - On the other hand, the Outlook Database Tool runs just fine on the XP > > machine with SQL 2005 developer. The tool was able to see the local > > instance. > > > > - I have tried uninstalling and reinstalling The SQL Standard, and I have > > tried to use administrator as a login account for SQLBrowser, but no joy. > > > > Anyone have any insights? > > > > > > > > Thanks, > > Immanuel Sibero > > > > > > > > "Rick Byham, (MSFT)" <rick***@REDMOND.CORP.MICROSOFT.COM> wrote in message > > news:ED8B0924-BB83-40E0-9B3E-7D623CD99C8D@microsoft.com... > >> Also, it's the SQL Server Browser Service that provides that info. Is the > >> SQL Server Browser Service on the SQL Server computer running? > >> -- > >> Rick Byham (MSFT), SQL Server Books Online > >> This posting is provided "AS IS" with no warranties, and confers no > > rights. > >> > >> "Jeffrey Williams" <jeff.williams3***@verizon.ent> wrote in message > >> news:emMmKbLIJHA.4600@TK2MSFTNGP06.phx.gbl... > >> > John A Grandy wrote: > >> >> There is nothing listed in the dropdown and attempting to browse does > >> >> not find anything. > >> >> > >> >> After I posted, I tried typing in the server name and I was able to > >> >> connect. > >> >> > >> >> But I'm wondering why can't SSMS auto-discover sql servers on the > > network > >> >> ? > >> >> > >> >> "Ekrem Önsoy" <ek***@compecta.com> wrote in message > >> >> news:A7AECB3D-8DFC-4D3C-B905-21F1FB79AEC9@microsoft.com... > >> >>> What do you mean "do not see a local instance"? Do you mean when you > >> >>> open up SSMS, you can't see the instance which you want to connect in > >> >>> the Connect to Server dialog box's Server drop down box? > >> >>> > >> >>> If its name does not appear in this list, did you try to type it > >> >>> yourself and connect to it this way? If you have tried this way and > >> >>> it > >> >>> does not connect, do you see an error message or something? Tell us > >> >>> what happends more detailed if possible. > >> >>> > >> >>> -- > >> >>> Ekrem Önsoy > >> >>> > >> >>> > >> >>> > >> >>> > >> >>> "John A Grandy" <johnagrandy-at-gmail-dot-com> wrote in message > >> >>> news:ukqr24DIJHA.1308@TK2MSFTNGP02.phx.gbl... > >> >>>> Windows Server 2003 x64 Enterprise Edition > >> >>>> > >> >>>> SQL Server 2005 Developer Edition > >> >>>> > >> >>>> Why would SSMS run locally not see a local sql server instance , > >> >>>> when > >> >>>> SSMS run on another box on the network can see this instance and > >> >>>> connect to it ? > >> >>>> > >> >>>> I have never had to do any config for SSMS ... it always works > >> >>>> out-of-the-box ... > >> >>>> > >> >>> > >> >> > >> > > >> > When you browse - the dialog comes up browsing the network. There is > >> > another tab in the dialog for local instances where you should see your > >> > local instance. > >> > > > > > > I'm reporting back on this issue. I played around with the registry key you Are you sure the user that is launching SSMS has permissions on that> mentioned. I observed the same behavior as you did on the SQL 2005 Developer > installed on an XP machine. But strangely enough, I could not reproduce this > with the SQL 2005 Standard 64-bit, running on Win2003 R2 64-bit. On this > server machine, the instance list is actually on the registry but apparently > is ignored on the SSMS list (so it doesnt matter whether or not I change > them, it simply doesnt show on the SSMS list). registry key? > Here's something more: If you are implying that this is a 64-bit issue then that is not the only> - Since my Win2003 R2 64-bit installation is a new one and had some time on > my hand, I blew it away, reinstalled from scratch down to the partitions, > and then installed SQL 2005 32bit Developer version. To my surprise, the > instance list now shows up. thing. I have two copies of Developer on 64-bit and this issue does not appear (I have not tried BCM but I can certainly browse local instances in other similar dialogs). > One quick question for you though: Personally I think it is a mistake to do this as opposed to figuring out why> IS it okay to run SQL Standard 32bit on Windows 2003 R2 64bit?? the Outlook tool can't see those registry keys. I would stick to hunting down the registry issue. You can get RegMon to see if permission on those keys are denied or if the tool is looking somewhere else to produce its list. http://technet.microsoft.com/en-us/sysinternals/bb896652.aspx Aaron,
Thanks for the note. Yes, I tried different users actually including the domain Administrator, local Administrator, and the domain account used by SQL service. Also note that I reproduced the same exact steps with the same user login (same everything) using the SQL Developer 32bit and found no issue (I started from scratch with the SQL Developer 32bit - I reformatted the drive). I'm installing SQL Standard 32bit now and see if this works for me. I do need to confirm though, if I can run SQL Standard 32bit on Windows 2003 64bit? Thanks, Immanuel Sibero Show quoteHide quote "Aaron Bertrand [SQL Server MVP]" <ten.xoc@dnartreb.noraa> wrote in message news:C513CB57.142DD%ten.xoc@dnartreb.noraa... > > I'm reporting back on this issue. I played around with the registry key you > > mentioned. I observed the same behavior as you did on the SQL 2005 Developer > > installed on an XP machine. But strangely enough, I could not reproduce this > > with the SQL 2005 Standard 64-bit, running on Win2003 R2 64-bit. On this > > server machine, the instance list is actually on the registry but apparently > > is ignored on the SSMS list (so it doesnt matter whether or not I change > > them, it simply doesnt show on the SSMS list). > > Are you sure the user that is launching SSMS has permissions on that > registry key? > > > Here's something more: > > - Since my Win2003 R2 64-bit installation is a new one and had some time on > > my hand, I blew it away, reinstalled from scratch down to the partitions, > > and then installed SQL 2005 32bit Developer version. To my surprise, the > > instance list now shows up. > > If you are implying that this is a 64-bit issue then that is not the only > thing. I have two copies of Developer on 64-bit and this issue does not > appear (I have not tried BCM but I can certainly browse local instances in > other similar dialogs). > > > One quick question for you though: > > IS it okay to run SQL Standard 32bit on Windows 2003 R2 64bit?? > > Personally I think it is a mistake to do this as opposed to figuring out why > the Outlook tool can't see those registry keys. I would stick to hunting > down the registry issue. You can get RegMon to see if permission on those > keys are denied or if the tool is looking somewhere else to produce its > list. > > http://technet.microsoft.com/en-us/sysinternals/bb896652.aspx > > I'm installing SQL Standard 32bit now and see if this works for me. I do Yes, I think you can, but I really wouldn't do that. Can you try installing> need to confirm though, if I can run SQL Standard 32bit on Windows 2003 > 64bit? the 64 bit again, and if you still have the same issue (it might have been based on another cause), you could try the RegMon utility I pointed out earlier. Seems silly to resort to 32-bit on 64-bit platform because of some silly drop-down on a one-time utility. Have you considered running the utility remotely? If another machine in the domain can see the instances on that box, then why can't you run the Outlook tool from the other machine? Aaron,
I agree with you on the idea of resorting to running the 32bit on the 64bit platform. I'm going to try the 64bit from scratch (reformatting and fresh install of Win2003 64bit) one more time and try the RegMon utility also. I have tried running the Outlook tool remotely. No joy. It enumerates local instances only (and yes other machines in the domain can see the instance and accesses it just fine - i.e. odbc, etc.) The utility is not exactly one-time, it is needed for creating new databases and offers a customized database backup / restore tasks. I will report back. Thanks again, Immanuel Sibero Show quoteHide quote "Aaron Bertrand [SQL Server MVP]" <ten.xoc@dnartreb.noraa> wrote in message news:C513D901.142FD%ten.xoc@dnartreb.noraa... > > I'm installing SQL Standard 32bit now and see if this works for me. I do > > need to confirm though, if I can run SQL Standard 32bit on Windows 2003 > > 64bit? > > Yes, I think you can, but I really wouldn't do that. Can you try installing > the 64 bit again, and if you still have the same issue (it might have been > based on another cause), you could try the RegMon utility I pointed out > earlier. > > Seems silly to resort to 32-bit on 64-bit platform because of some silly > drop-down on a one-time utility. Have you considered running the utility > remotely? If another machine in the domain can see the instances on that > box, then why can't you run the Outlook tool from the other machine? > Guess (goah***@getlost.com) writes:
> My big problem is with the Outlook Database Tool that apparently can not I would guess that tool looks for> detect the local instance when running on the 64bit SQL Edition. HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Microsoft SQL Server\Instance Names\SQL Because this is where all 32-bit requests are diverted by default. You could try to add instance list there. > IS it okay to run SQL Standard 32bit on Windows 2003 R2 64bit?? Yes, and sometimes this is necssary for other reasons.-- Erland Sommarskog, SQL Server MVP, esq***@sommarskog.se Links for SQL Server Books Online: SQL 2008: http://msdn.microsoft.com/en-us/sqlserver/cc514207.aspx SQL 2005: http://msdn.microsoft.com/en-us/sqlserver/bb895970.aspx SQL 2000: http://www.microsoft.com/sql/prodinfo/previousversions/books.mspx Erland,
Thank you for the reply. I am giving the SQL64bit one more chance, and also investigate the registry setting that you suggested. I will report back. Thanks, Immanuel Sibero "Erland Sommarskog" <esq***@sommarskog.se> wrote in message Server\Instance Names\SQLnews:Xns9B331E081417Yazorman@127.0.0.1... > Guess (goah***@getlost.com) writes: > > My big problem is with the Outlook Database Tool that apparently can not > > detect the local instance when running on the 64bit SQL Edition. > > I would guess that tool looks for > > HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Microsoft SQL > could try to add instance list there.> Because this is where all 32-bit requests are diverted by default. You > http://www.microsoft.com/sql/prodinfo/previousversions/books.mspx> > IS it okay to run SQL Standard 32bit on Windows 2003 R2 64bit?? > > Yes, and sometimes this is necssary for other reasons. > -- > Erland Sommarskog, SQL Server MVP, esq***@sommarskog.se > > Links for SQL Server Books Online: > SQL 2008: http://msdn.microsoft.com/en-us/sqlserver/cc514207.aspx > SQL 2005: http://msdn.microsoft.com/en-us/sqlserver/bb895970.aspx > SQL 2000: Show quoteHide quote > Aaron and Erland,
I reinstalled the 64bit version while making sure that all the steps that I take are exactly the same as when I installed the 32bit version. The issue is still there with the 64bit version. - The 32bit version lets the Outlook Tool detect the local instances but the 64bit does NOT. - The 32bit version shows the list of local instances under the database engine when collapsed (i.e. under the "Local Servers" Tab of the SSMS server name dropdown), but the 64bit version does NOT. After running RegMon, the Outlook Tool looks at the value in HKLM\Software\Microsoft\Microsoft SQL Server\InstalledInstances. This value appears to be a concatenation of the local instance names. After installations of both the 64bit and the 32bit SQL Standard, this key is created in both cases. But for some reason the Outlook tool ignores this registry key (or can not read it) when run under the 64bit. Again, my issue is with the Outlook tool, so I have to revert back to the 32bit version to move on. I have to believe that this could be an issue between the 64bit and the 32bit versions since the Outlook tool is not the only one having a problem with listing local instances, SSMS itself can not detect the local instances under the "Local Servers" tab. Thank you for all your help. Immanuel Sibero Show quoteHide quote "Guess" <goah***@getlost.com> wrote in message news:%2384ejsmKJHA.5692@TK2MSFTNGP04.phx.gbl... > > Erland, > Thank you for the reply. I am giving the SQL64bit one more chance, and also > investigate the registry setting that you suggested. > > I will report back. > > Thanks, > Immanuel Sibero > > > > "Erland Sommarskog" <esq***@sommarskog.se> wrote in message > news:Xns9B331E081417Yazorman@127.0.0.1... > > Guess (goah***@getlost.com) writes: > > > My big problem is with the Outlook Database Tool that apparently can not > > > detect the local instance when running on the 64bit SQL Edition. > > > > I would guess that tool looks for > > > > HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Microsoft SQL > Server\Instance Names\SQL > > > > Because this is where all 32-bit requests are diverted by default. You > could try to add instance list there. > > > > > IS it okay to run SQL Standard 32bit on Windows 2003 R2 64bit?? > > > > Yes, and sometimes this is necssary for other reasons. > > -- > > Erland Sommarskog, SQL Server MVP, esq***@sommarskog.se > > > > Links for SQL Server Books Online: > > SQL 2008: http://msdn.microsoft.com/en-us/sqlserver/cc514207.aspx > > SQL 2005: http://msdn.microsoft.com/en-us/sqlserver/bb895970.aspx > > SQL 2000: > http://www.microsoft.com/sql/prodinfo/previousversions/books.mspx > > > > > I have to believe that this could be an issue between the 64bit and the Is this before or after you right-click "Local Server Groups" > Tasks >> 32bit versions since the Outlook tool is not the only one having a problem > with listing local instances, SSMS itself can not detect the local instances > under the "Local Servers" tab. Register Local Servers? This should happen for you automatically but I've read several people say that they've had to "kick it," so to speak. Aaron,
This is on the very first step in SSMS: - On the "Connect to Server" window, I click the dropdown for Server Name. - I select "<Browse for More...>. This is the last choice in the dropdown. - This brings me to the "Browse for Servers" window. - Then I select the "local servers" tab. - On this tab, there is "Database Engine". In the 64bit version, this selection can not be collapsed to show the local instance list, but in the 32bit version, this "Database Engine" has a plus sign to its left. Clicking the plus sign will show the list of local instances. Thanks for your help, Immanuel Sibero. Show quoteHide quote "Aaron Bertrand [SQL Server MVP]" <ten.xoc@dnartreb.noraa> wrote in message news:C5192DCC.1473C%ten.xoc@dnartreb.noraa... > > I have to believe that this could be an issue between the 64bit and the > > 32bit versions since the Outlook tool is not the only one having a problem > > with listing local instances, SSMS itself can not detect the local instances > > under the "Local Servers" tab. > > Is this before or after you right-click "Local Server Groups" > Tasks > > Register Local Servers? This should happen for you automatically but I've > read several people say that they've had to "kick it," so to speak. > > Aaron, Can you try something for me?> > This is on the very first step in SSMS: > - On the "Connect to Server" window, I click the dropdown for Server Name. > - I select "<Browse for More...>. This is the last choice in the dropdown. > - This brings me to the "Browse for Servers" window. > - Then I select the "local servers" tab. > - On this tab, there is "Database Engine". In the 64bit version, this > selection can not be collapsed to show the local instance list, but in the > 32bit version, this "Database Engine" has a plus sign to its left. Clicking > the plus sign will show the list of local instances. Before you do any of this "Connect to Server" business. Open SSMS and open the Registered Servers tab (Ctrl+Alt+G). Right-click Database Engine there and choose "Update Local Server Registration"... If this changes anything (e.g. adds servers under "Database Engine") then try your connect to server business again. If this doesn't change anything then something is corrupt on your system. Because I have 64bit and I certainly see my local instances (though I don't recall if I ever had to "kick it" this way initially). Aaron,
Thanks for the additional tip. > If this doesn't change anything then something is corrupt on your system. Here is what I did:> Because I have 64bit and I certainly see my local instances (though I don't > recall if I ever had to "kick it" this way initially). - "Update Local Server Registration" per your instruction. This clears out the Database Engine list. So, now it doesnt show any instances under Database Engine. - I right click Database Engine>New>Server Registration. This brings up the New Server Registration with the Server Name box on it. This Server Name box behaves the same way (i.e. I can type in the instance name and it will work, but if I click on the drop down, and click on "<Browse for More..>", the local instance list is missing under the Database Engine on the Local Server tab). You may be correct that something may be corrupt on the system but I dont know where else to look. Note that I have reinstalled this SQL 2005 64bit five or six times. Every time I started from scratch all the way to the partitions (yes, I actually repartitioned and reinstalled Win2003 R2 64bit). I even redownloaded the SQL Install EXE file and reburn the ISO file for Win2003 R2 64bit, just in case the install files were corrupted. I'm still observing the same issue. Meanwhile, I have also installed and reinstalled the 32bit version and it worked everytime. <G> I was able to see the local instance list under Database Engine and the Outlook Tool works without issue. Maybe I'll revisit this again, but for now I'll have to go with the Winserver 64bit and SQL 32bit. Thanks for all your help. Immanuel Sibero Show quoteHide quote "Aaron Bertrand [SQL Server MVP]" <ten.xoc@dnartreb.noraa> wrote in message news:C51939E1.1475F%ten.xoc@dnartreb.noraa... > > Aaron, > > > > This is on the very first step in SSMS: > > - On the "Connect to Server" window, I click the dropdown for Server Name. > > - I select "<Browse for More...>. This is the last choice in the dropdown. > > - This brings me to the "Browse for Servers" window. > > - Then I select the "local servers" tab. > > - On this tab, there is "Database Engine". In the 64bit version, this > > selection can not be collapsed to show the local instance list, but in the > > 32bit version, this "Database Engine" has a plus sign to its left. Clicking > > the plus sign will show the list of local instances. > > Can you try something for me? > > Before you do any of this "Connect to Server" business. Open SSMS and open > the Registered Servers tab (Ctrl+Alt+G). Right-click Database Engine there > and choose "Update Local Server Registration"... > > If this changes anything (e.g. adds servers under "Database Engine") then > try your connect to server business again. > > If this doesn't change anything then something is corrupt on your system. > Because I have 64bit and I certainly see my local instances (though I don't > recall if I ever had to "kick it" this way initially). > John A Grandy (johnagrandy@g-mail-dot-com) writes:
> After I posted, I tried typing in the server name and I was able to Rather than typing the server name, a single dot should do.> connect. -- Erland Sommarskog, SQL Server MVP, esq***@sommarskog.se Links for SQL Server Books Online: SQL 2008: http://msdn.microsoft.com/en-us/sqlserver/cc514207.aspx SQL 2005: http://msdn.microsoft.com/en-us/sqlserver/bb895970.aspx SQL 2000: http://www.microsoft.com/sql/prodinfo/previousversions/books.mspx John A Grandy wrote:
> Windows Server 2003 x64 Enterprise Edition Somebody knows the answer to this issue?> > SQL Server 2005 Developer Edition > > Why would SSMS run locally not see a local sql server instance , when SSMS > run on another box on the network can see this instance and connect to it ? > > I have never had to do any config for SSMS ... it always works > out-of-the-box ... > > Also having this issue on Sql Server 2005 Std Edition x64 , with SP2- Local servers don't show up in SSMS - not a problem to connect with dbserver (typing a dot), but it is not possible to connect to reporting services neither (via SMSS) - heard that typing http:\\localhost\reports in SSMS when trying to connect woult also work, but didn't try that yet. I have to say that 1) the services run with the local built-in account (set during installation) 2) at first the sql browser service was not enabled - i enabled it after installation when i saw the problem - after this, i could connect to my local server via "browse for severs, network servers", but still not via the "local servers"-tab 2)when installing sqlserver the IIS-website was stopped, and I configured reportingservices afterwards (after i had started the default iis-site). Can't speak for reporting services, but for database engine you should be
able to switch to registered servers view, right-click the registered servers or local server group node and choose to update local registrations. I only have 2008 SSMS in front of me and I know the option is now in a slightly different spot, but the concept is the same. On 3/4/09 2:40 PM, in article QrDrl.43304$1N5.39561@newsfe21.ams2, "Lucas D" <nore***@test.com> wrote: Show quoteHide quote > John A Grandy wrote: >> Windows Server 2003 x64 Enterprise Edition >> >> SQL Server 2005 Developer Edition >> >> Why would SSMS run locally not see a local sql server instance , when SSMS >> run on another box on the network can see this instance and connect to it ? >> >> I have never had to do any config for SSMS ... it always works >> out-of-the-box ... >> >> > Somebody knows the answer to this issue? > > Also having this issue on Sql Server 2005 Std Edition x64 , with SP2- > Local servers don't show up in SSMS - not a problem to connect with > dbserver (typing a dot), but it is not possible to connect to reporting > services neither (via SMSS) - heard that typing http:\\localhost\reports > in SSMS when trying to connect woult also work, but didn't try that yet. > > I have to say that > 1) the services run with the local built-in account (set during > installation) > 2) at first the sql browser service was not enabled - i enabled it after > installation when i saw the problem - after this, i could connect to my > local server via "browse for severs, network servers", but still not via > the "local servers"-tab > 2)when installing sqlserver the IIS-website was stopped, and I > configured reportingservices afterwards (after i had started the default > iis-site).  
Other interesting topics
Re: Replace SSMS 2005 with SSMS 2008
Performance Monitor / Database Storage using ODBC Re: SQL Server Management Studio 2008 Express failed to retrieve d How interpreting performance monitor counter value in Profiler backup always fails on restore Multiple copies of the same file How to regret tuning? 1000 Attempt to read unknown version of BCP format file RE: SQL Mirroring of SQL Reporting Services RE: Database Engine Tuning Advisor suggestion to replace syntax. |
|||||||||||||||||||||||
