I try to open a SSAS Cube but I get a OLE DB error message below.
The same cube I can browse with the SQL Server Business Intelligence Development Studio.
Error message:
Microsoft OLE DB Provider for Analysis Services 2005 Microsoft OLE DB Provider for Analysis Services 2005 reported:
Errors in the OLE DB provider. Could not connect to the redirector. Ensure that the SQLBrowser service is running on the '<MY Server Name>' server. Errors in the OLE DB provider. An error occurred while named instance information was being retrieved from the SQLBrowser service on the '<MY Server Name>' server.
The SQL Browser is used when you are attempting to communicate with a named instance. What you are seeing is a known problem, fixed in SP1, where the SQL Browser needs communication with a domain controller to validate your access rights. This happens to me if I disconnect my laptop from the network and try an connect to a named instance on it. I've also seen it if the SQL Browser is running under a service account that isn't a machine administrator -- and third I've seen this if you are running under XP SP2 and the firewall is stopping your connectivity to the SQL Browser.
You have a few options: 1) make it the default instance -- that works without any problems, 2) always make sure a DC is available, 3) make sure the XP firewall is disabled on the SQL Browser port# (and the various instance port#s), 4) attempt to connect specifically to the port # for the instance (which bypasses the redirector) -- try using <server>:<port#> syntax for the server name.
Hope that helps.
_-_-_ Dave
|||
Thanks Dave,
I have check the options:
1. I have installed sql2005 with the default instance <MSSQLSERVER> that is not the problem
2. I'm connected to the DC
3. I have disabled the firewall, and that has changed the error message!!
The new message is:
Error reported by OLAP server.
Additional information:
Microsoft? OLE DB Provider for Analysis Services reported:
Cannot connect to the server '<MYSERVER>. The server is either not started or too busy.
But I can work with the SQL Server Business Intelligence Development Studio without any problem!!
|||I have found the solution for the reported error message.
After reinstalling the "Workstation components" I can connect to the cubes in SSAS for a client Olap tool.
Thanks Dave for your support.
Regards,
Peter
|||I got the same error with the same symptoms but resolved the OLAP connection problem simply by reinstalling the OLAP provider for SQL Server 2005. The file name is SQLServer2005_ASOLEDB9.msi and it can be found on the microsoft downloads site.|||Hi Dave,
Some questions for you about your options:
1. How do you make SQL Server 2005 the default instance if SQL Server 2000 is also installed on the same machine.
SQL Server 2000 can be removed if this is an option.
2. How can you confirm that the DC is available besides when you log into the server which is on the domain?
3. The sql server is on a windows 2003 server. The AD server is in another state and is accessed via a VPN. Could this be a problem?
4. How do you connect to the port # since when I use the Data Connection Wizard and use 10.1.1.1:1384 it comes back with the error:
"Transport Layer error."
If I use the instance name syntax -> 10.1.1.1\InstanceName - it works but then it uses the redirector which causes the main error.
So a couple of your solutions have some problems for me... is there any other way around them?
Thanks,
Andrew.
>>1. How do you make SQL Server 2005 the default instance if SQL Server 2000 is also installed on the same machine.
There could be only a single default instance on the machine. And Analysis Services 2000 does not support named instances, so for AS 2005 be default instance you need to remove AS2000.
>>2. How can you confirm that the DC is available besides when you log into the server which is on the domain?
Not sure about this. You can try posting on windows networing newsgroup.
>>4. How do you connect to the port # since when I use the Data Connection Wizard and use 10.1.1.1:1384 it comes back with the error:
"Transport Layer error."
Make sure you've got port numeber correctly. By default named instance picks up a port number dynamically on every restart. You can force it to use fixed port by specifying Port server configuration property.
Edward.
--
This posting is provided "AS IS" with no warranties, and confers no rights.
No comments:
Post a Comment