SQL2005 AS Named instance - SQL Browser issue?

Hi all

( Note: This question was first posted on microsoft.sqlserver.connect last week, but I was advised that the MSDN forums was the correct place for SQL 2005 postings.)

I have a development machine with SQL 2000 and AS 2000 sp4 on as the default instance SERVERNAME.
I have installed the September CTP of SQL 2005 as a named instance SERVERNAME\YUKON.
All appeared to go well, SQL server is fine and I've built tables etc.

However when I connect to the AS database using the BI tool I get the bizarre behaviour that I can build and process a cube, but not then connect to it to see the data!

The Error reported is:
"
The query could not be processed:
o Errors in the OLE DB provider. Could not connect to the redirector. Ensure that the SQLBrowser service is running on the 'SERVERNAME2' server.
o Errors in the OLE DB provider. An error occurred while named instance information was being retrieved from the SQLBrowser service on the 'SERVERNAME2' server.
"

I tried using a 3rd party client tool to connect as well - one which I know uses OLAP 9.0 to connect and supports the September CTP, and it simply couldn't find the named instance at all. It reported
"Errors in the OLE DB provider. Could not connect to the redirector. Ensure that the SQLBrowser service is running on the 'SERVERNAME' server"

Is there a known issue with the SQL Browser unable to handle named instances There is a post on microsoft.sqlserver.connect which reports very similar behaviour with named instances.
Is there a known work around that doesn't involve a complete re-install on a separate machine
Will there be time to fix it before the product launch

Thanks in advance,

Richard.
(Based in the UK)

Answer this question

SQL2005 AS Named instance - SQL Browser issue?

Needo
I wrestled with this problem for days. I did a full installation of SQL Server 2005 developer edition, and everything worked except for the "browser" tab in SSAS. I could build and process my cube, but I couldn't browse it. I had SQL Server 2005 running under a named instance. I tried changing security settings, Windows Firewall settings, SQL Server config settings, etc., but nothing would make this work.

Finally, I un-installed SQL Server 2005 re-installed it as the default instance. Upon doing this, my "browser" tab worked in SSAS.
sannasum
I had been having this very same problem (couldn't even connect to my AS server using Management Studio on my local machine). I installed SP1 and all post SP1 hotfixes. Even this didn't seem to help the problem. What DID help it was to check the accounts under which the relevant services were running:

1) Ensure the "SQL Server Browser" service is running under the Local System account (I previously was using a NETWORK SERVICE account - which was probably my own fiddling fault.).

2) My "Sql Server Analysis Services (InstanceName)" Service is also running as Local System.

And then it worked. Hooray!.

Hope this helps somebody.
MarkC

There is a known issue with connecting to named instances if the machines are disconnected from the network and the user's credentials cannot be verified with a domain controller. This typically happens to me when I run everything on my laptop and then disconnect.

This is fixed in SP1.

_-_-_ Dave
pierrebai

Dave,

This sounds like the problem. I run everything on my laptop, and always use domain credentials.

SP1 Already

(Just Teasing, SQL 2005 is pretty rock solid IMHO)

Regards,

Richard
v-mousah
Thanks anyway

Will let you know if I find a solution

Steve
Fishouille

I've seen reports, I haven't verified it personally, that a workaround is to establish the port number for the instance and then use it directly in your connect string using the <server>:port# syntax. That bypasses the instance name to port# translation that SQL Browser does. Give that a try.

_-_-_ Dave
Rajat Dasgupta
Hi

I am getting the same thing when I try Browse a cube. Do you have a solution

Steve
aayush_dabas
Hi Steve,

I'm afraid I don't have a solution.

My final "work round " was to switch completely to 2005 on my development machine so I didn't have to have a named instance at all. Then run SQL 2000 in a virtual PC.

Not exactly a solution though is it ;-)

Sorry I can't be more help.

Richard.
SQL2005 AS Named instance - SQL Browser issue?

Answer this question