January 14, 2006 at 11:01 pm
Setting: Windows 2003, SP1. Box member of workgroup. Clean install of Sql 2005, installed as instance,
sql 2000 is default. Never had betas or CTP of 2005 installed on this box. I'm logged in as Administrator of box
Problem: When I try to Connect to Analysis Services from Microsoft SQL Server Management Studio
I get the error:
Cannot conect to "newpc\sql2005"
>
Additional Information: A connection cannot be made to redirector. Ensure that 'SQL Browser'
service is running(Microsoft.AnalysisServices.AdomdClient)
>
No connection could be made because the target machine actively refused it (System).
After much fumbling I found that changing the logon account that started the Sql Server Browser from
NT AUTHORITY\NetworkService to 'LocalAccount" did the trick. Is this a bug with AS?
TIA,
Bill
January 17, 2006 at 8:00 am
This was removed by the editor as SPAM
February 14, 2006 at 6:56 am
Thanks, your message helped me to solve the same problem.
I believe it's basically a lack of privileges on the server. I also had a simliar problem with a network ID we use to run various services - until I added the ID to the Administrators server role (I'm sure this isn't the secure way to do it but it works!).
Loz
April 7, 2006 at 1:06 am
I've set the SQLBrowser service account to "LocalService" but that did not to the trick.
After changing it to "Local System" SSAS was accessable, but the Server-browser (SSMS) did not show it !!!
I was able to connect using servername\instancename, but they were not discovered in the serverbrowser !
Thanks for your input !
Johan
Learn to play, play to learn !
Dont drive faster than your guardian angel can fly ...
but keeping both feet on the ground wont get you anywhere :w00t:
- How to post Performance Problems
- How to post data/code to get the best help[/url]
- How to prevent a sore throat after hours of presenting ppt
press F1 for solution, press shift+F1 for urgent solution 😀
Need a bit of Powershell? How about this
Who am I ? Sometimes this is me but most of the time this is me
April 26, 2006 at 4:00 pm
Hi fellows,
I am having a similar problem. I can develop and deploy AS projects. In the business intelligence studio I can browse dimensions. But when trying to browse a successfully processed cube I get:
"Errors in the OLEDB provider. Could not connect to the redirector. Ensure that the SQLBrowser is running on the "XXX" server."
I have elevated all privileges to Administrator, and tried using Local System for the Sql Server Browser.
Still no go.
Anyone has any more input on this matter.
AS is runing as a named instance XXX\SQL2K5.
Regards
rockmoose
You must unlearn what You have learnt
November 15, 2006 at 5:53 am
Hi all.
My problem was that I could connect to remote AS server using Management Studio, but ASP.NET application failed. My application uses a ReportViewer control that is supplied with VS2005 for ASP.NET 2.0, I configured the control to render report in local processing mode, that is, report itself used the AS server just as a datasource.
So, what I did:
1)Enabled Anonymous Connections for Analysis Services(SQL Server 2005 Surface Area Configuration -> Surface Area Configuration for Features.
2)Added ANONYMOUS LOGON user to Analysis Services admins
3)Added <identity impersonate="true"/> to web.config
That did the trick, of course it lacks security, but still.... it is better than nothing.
September 23, 2008 at 2:43 am
I got it after chaning from NETWORKService to LocalSystem account.
Thanks
March 20, 2009 at 6:51 pm
Make sure you SSAS Service is running .
Go to windows service and check if SQL Server Analysis Service is running.
March 24, 2009 at 6:40 am
To login to the SSAS your user account needs to be known to AS Server. Create user account with your credentials in the server to login to the server from SSMS or BIDS. YOu also need to be part of OLAP group in the Server, if you would be deploying cubes from SSMS/BIDS
March 9, 2010 at 6:51 am
We can check whether SQL express is installed on a machine or not and then can install it along with our application.Following is the code sample in VB.NET to implement the same.
[VB.NET CODE STARTS HERE]
' Need to add System.Management reference
Imports System.Management
' Check if SQL express is already installed in the destination machine
Public Shared Function isExpressInstalled() As Boolean
Const edition As String = "Express Edition"
Const instance As String = "MSSQL$SQLEXPRESS"
Const spLevel As Integer = 1
Dim fCheckEdition As Boolean = False
Dim fCheckSpLevel As Boolean = False
Try
Dim getSqlExpress As ManagementObjectSearcher = New ManagementObjectSearcher("root\Microsoft\SqlServer\ComputerManagement", "select * from SqlServiceAdvancedProperty where SQLServiceType = 1 and ServiceName = '" + instance + "' and (PropertyName = 'SKUNAME' or PropertyName = 'SPLEVEL')")
If getSqlExpress.Get.Count = 0 Then
Return False
End If
For Each sqlEngine As ManagementObject In getSqlExpress.Get
If sqlEngine("ServiceName").ToString.Equals(instance) Then
Select Case sqlEngine("PropertyName").ToString
Case "SKUNAME"
fCheckEdition = sqlEngine("PropertyStrValue").ToString.Contains(edition)
Case "SPLEVEL"
fCheckSpLevel = Integer.Parse(sqlEngine("PropertyNumValue").ToString) >= spLevel
End Select
End If
Viewing 11 posts - 1 through 10 (of 10 total)
You must be logged in to reply to this topic. Login to reply