23
2013
Cannot connect to named instances of Analysis Services after fresh installation or rename of server
An article by 
Many a times when a new SQL Server 2008 R2 analysis services instance is installed or a server is renamed then following error is received while trying to connect to named instance of analysis service,
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 ::1:2383 (System)
This is mostly because of browser service account not given appropriate privileges or permissions are not set correctly, in this scenario do following,
1. Go to Start > Computer > right click, select Manage > Server Manager > Configuration > Local Users and Groups > Groups
2. Check for SQL Server Browser Group name, for e.g. (Note down the name)
3. Now navigate to following folder,
c:\Program Files (x86)\Microsoft SQL Server\90\Shared
4. Inside it there will be ASConfig folder,
5. Right click ASConfig folder > Go to Properties > Go to Security tab
6. Check if same SQL Browser Service group present or not, if present then edit the permissions and give Write permissions and If SQL browser group not present then add it and give write permissions as below,
7. Now go to “SQL Server Configuration Manager” (Start > All Programs > Microsoft SQL Server 2008 R2 > Configuration Tools > SQL Server Configuration Manager)
8. Store SQL Server Browser Services
9. Stop SQL Server Analysis Services
10. Start SQL Server Browser Services
11. Start SQL Server Analysis Services
12. Try to connect SQL Server Analysis Services using SSMS or Powershell, etc. it should work fine!
——————–
Above solution shall work perfectly, in case it doesn’t then follow below links, they have provided few more workarounds for similar kind of issue,
For e.g. Restart Browser Service with –c switch or Connect Analysis services using port number, etc.
http://support.microsoft.com/kb/2658571
http://asstoredprocedures.codeplex.com/discussions/441913
About the Author: Nitin G
Indian born, trekker, biker, photographer, lover of monsoons. I've been working full time with SQL Server since year 2005 and blogs to post the content aquired during my research on new topics or fixing issues faced by me as a DBA while working in different kind of projects, hope some of my posts may helps others in SQLDBA community. Everything you read on my blog is my own personal opinion and any code is provided "AS-IS" with no warranties!
3 Comments + Add Comment
Leave a comment
Subscribe to this blog via Email
Old Posts
- November 2017 (3)
- October 2017 (4)
- September 2017 (2)
- May 2017 (1)
- April 2017 (1)
- July 2016 (3)
- May 2016 (1)
- April 2016 (1)
- February 2016 (2)
- January 2016 (1)
- October 2015 (1)
- September 2015 (1)
- August 2015 (1)
- July 2015 (2)
- June 2015 (3)
- April 2015 (1)
- March 2015 (1)
- December 2014 (1)
- September 2014 (2)
- April 2014 (1)
- January 2014 (3)
- October 2013 (2)
- September 2013 (2)
- August 2013 (4)
- July 2013 (1)
- June 2013 (2)
- May 2013 (5)
- April 2013 (3)
- March 2013 (1)
- February 2013 (9)
- January 2013 (11)
- December 2012 (14)
- November 2012 (3)
- October 2012 (4)
- July 2012 (2)
- June 2012 (3)
- May 2012 (2)
- April 2012 (8)
- March 2012 (6)
- February 2012 (3)
- January 2012 (1)
- December 2011 (5)
- November 2011 (8)
- October 2011 (5)
- September 2011 (3)
- August 2011 (3)
- July 2011 (3)
- May 2011 (1)
- November 2010 (1)
Tags
Calender
| M | T | W | T | F | S | S |
|---|---|---|---|---|---|---|
| « Nov | ||||||
| 1 | 2 | 3 | 4 | 5 | 6 | 7 |
| 8 | 9 | 10 | 11 | 12 | 13 | 14 |
| 15 | 16 | 17 | 18 | 19 | 20 | 21 |
| 22 | 23 | 24 | 25 | 26 | 27 | 28 |
| 29 | 30 | |||||
View Post by Categories
Recent Articles
- Setting up Always ON Availability Group in Multi Subnet Cluster – Recommendations
- Configuring Replication with Always ON Availability Group
- Login failed for user ‘DOMAIN\COMPUTER$’. Reason: Could not find a login matching the name provided. [CLIENT: ]
- Modern Servicing Model (Service Pack and Cumulative Updates) for SQL Server 2017 and onwards
- Fix: SSMS 2012 opening Debug window when pressing F5
Above solution is working for me…!!!
Hi,
I renamed my AS instance to ‘Tabular’ from what it previously was. Before the rename, the connection was successful from the MS SQL Management Studio. Now, after the rename, I get the same error as on the first screenshot of this page. I tried your proposed solution but it still doesn’t work.
What I can see in the SQL Config Manager is that the Analysis Service is also stopped and tells that the service couldn’t respond in a timely manner when I try to ‘Start’ it.
What could be the problem now? Can I rename it to what it was earlier? (I tried leaving the name blank since it was the default name before too but it says that a server with the name MSSQLSERVER already exists).
Any help would be appreciated, thanks.
Thank you for your detailed solution. Just wanted to give you props for helping me out. 🙂