Re: AS2005: Can't access named instance / sqlbrowser issue...



You might be having different problem . Try installing SQL Server 2005 SP1
Go to MSDN forum for more information about troubleshooting connectivity
problems
http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=314855&SiteID=1

Edward.
--
This posting is provided "AS IS" with no warranties, and confers no rights.




"Hugo" <Hugo@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:62887C72-AEAD-4FA2-8B10-07B3C57B4542@xxxxxxxxxxxxxxxx
Thank you for your response. I can start SQL Server Browser Service but
cannot connect to the named instance. I have checked all security on
folders.
It still doesn't work.

Oliver

"Edward Melomed [MSFT]" wrote:

Which problem exactly (below there are 2 problems mentioned)

1. You cannot start SQL Server Browser service?
2. SQL Server Browser service is started, but you cannot connect to the
named instance?

Edward.
--
This posting is provided "AS IS" with no warranties, and confers no
rights



"Hugo" <Hugo@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:E35529E3-ACD1-4837-8EF2-687DEA2FFD17@xxxxxxxxxxxxxxxx
I have the same problem but It doesn't work with me.

Do you have any additional information?

Thanks a lot!

Hugo

"Jéjé" wrote:

thanks a lot!

security on the folder solves the issue!! :-)))


"Edward Melomed [MSFT]" <edwardm@xxxxxxxxxxxxxxxxxxx> wrote in message
news:uUzjQaDKGHA.3352@xxxxxxxxxxxxxxxxxxxxxxx
Several things to check:
1. File share permissions:
C:\Program Files\Microsoft SQL Server\90\Shared
C:\Program Files\Microsoft SQL Server\90\Shared\ASConfig

2. Reg Key
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\90\SQL
Browser
Should have AnalysisServiceListener value set to 1

3. Try deleting msmdredir.ini and .bak files
C:\Program Files\Microsoft SQL Server\90\Shared\ASConfig
Restart SQLBrowser and then your named instance.

Edward.

--
This posting is provided "AS IS" with no warranties, and confers no
rights



"Jéjé" <willgart_A_@xxxxxxxxxxxxxx> wrote in message
news:ujYp3HDKGHA.1728@xxxxxxxxxxxxxxxxxxxxxxx
Hi,

starting the sqlbrowser cause this error (event log):
The SQLBrowser service was unable to establish Analysis Services
discovery.

I can't access my named instance of Analysis services.

the "default" instance is an SQL2000 version, not 2005.



I can access my AS server if I specify the port in the connection
(like
<server>:PORT) but this port change everytime I restart the
service.

Can I use a fixed value for this port?



I have uninstalled / reinstall AS but this change nothing.



any idea?



thanks.



Jerome.














.



Relevant Pages

  • Re: Unable to Apply SP4 to SQL 2000 Cluster (new Node)
    ... Rebuild the node in the failover cluster. ... Scenario 1" in SQL Server 2000 Books Online. ... This setup process updates to SP4 only the binaries on the new ...
    (microsoft.public.sqlserver.clustering)
  • Re: Migrating DTS Packages on SQL 2000 to SSIS on 2005
    ... You can install a named instance of SQL Server 2005 on the same box as SQL ... server as SSIS does not support named instances. ...
    (microsoft.public.sqlserver.dts)
  • Re: WSS 3.0 question
    ... I followed the advise given in removing WSS 3.0 etc, ... the server is complaining that the SQL service(?) was tempered with or corrupt. ... I may just instal the SQL server as I was going eventuall use it anyway. ... If WSUS 3.0 is installed, I would suggest you uninstall it and then you install WSS 3.0. ...
    (microsoft.public.windows.server.sbs)
  • Re: Do SqlServer 2000 & SqlServer 2005 co-exist
    ... I understand that you can connect to SQL 2000 named instance on the local ... to an instance of SQL Server 2000 or of SQL Server 7.0 that was installed ... Select TCPIP, and click Properties, and set the port of the instance to ...
    (microsoft.public.sqlserver.setup)
  • Re: SQL Server 2005 Cluster Setup Quiz
    ... I did test and it did not install the client tools. ... http://www.clusterhelp.com - Cluster Training ... Microsoft SQL Server MVP ... Provide a template on how to read SQL Server 2005 setup log files. ...
    (microsoft.public.sqlserver.clustering)