Home Dashboard Directory Help

Create and alias to a (named) instance of Analysis Services 2005/8 by Tiago Rente - VF-PT



Sign in
to vote
Type: Suggestion
ID: 432644
Opened: 4/15/2009 6:54:01 AM
Access Restriction: Public


It is possible to create alias to SQL Server (Database Engine) using "SQL Server Configuration Manager".

It must be possible to create an alias to a instance of Analysis Services 2005/8, regardless the instance is or is not a named instance.
E.g., <AS alias name> = <server name> or <AS alias name> = <server name>\<instance name>
Sign in to post a comment.
Posted by HAL9256 on 1/2/2014 at 12:03 PM
A workaround I found for using an Alias for just connecting to the default instance is is to disable the loopback check. This won't help with the named instances, but could help with a single named instance.

Execute the following Registry fix:

Windows Registry Editor Version 5.00

Posted by mvoltchenko on 6/18/2012 at 8:43 AM
Has there been a resolution to this issue? I am trying to create an alias to access Analysis Services in SQL 2012 and still getting the same error "No such host is know"
Posted by Shriniwas on 5/24/2010 at 8:09 AM
Is this issue resolved in SQL Server 2008? Is it possible to create Alias for Analysis server instance in 2008
Posted by Microsoft on 1/5/2010 at 6:56 PM
We are continuing to investigate this issue and will consider making a change in a future release of SQL Server.

The Analysis Services Team
Posted by Microsoft on 7/28/2009 at 4:21 PM
Thanks a lot renteta for your suggestion.
We will take a look at this for the future version of Analysis Services.
The Analysis Services Team.
Sign in to post a workaround.
Posted by Claude D Martel on 7/17/2013 at 7:07 PM
We decided to create our Project Server 2010 farm with the Alias, 32 and 64bit with the ports being dynamic, and have not been able to connect to the SSAS side of the SQL box using an alias. All configs in Excel services and Secure Store were thouroughly checked, we also added a DNS Host Record for the alias, we added multiple aliases, full control everywhere in the Databases... Nothing worked so this is how we are getting by...

In Project Server/SharePoint 2010 you can edit the odc files in BI, point them to the SQL_Server_name\InstanceName and re-save/ovewrite them to their respective librarie (as a temporary method). Until MS resolves this Actively Refused Connection to the Server, we will have to modify all new and existing odc connection strings to connect to SSAS, even funny though how the alias works for the database portion but is immediately refused access to the analysis service.