SSAS 2008 R2 - 具有 DNS 别名的数据源不起作用
我有一个带有 SQL Server 引擎和 SQL Server Analysis Services (2008 R2) 的 SQL Server。服务器的物理名称是SQ21。为了保持灵活性，我们创建了一个 dns 别名（主机 A），它指向该服务器（分别是服务器的 IP 地址）。 这在几乎所有场景中都可以正常工作
- Sql server management studio
- 部署 SAA 项目（部署服务器）
我们有一个问题。如果我们想要处理 saas 数据库，我会收到错误： “关系模块中出现错误。无法使用具有 ID 的数据源建立连接”（注意，这是我从德语翻译的，因此确切的术语可能略有不同）
一旦我更改了数据源服务器属性回到物理服务器就可以了。
可能是什么问题？克伯罗斯？或者两个服务器（sql server 引擎和 saas）是否位于同一服务器上？
I have an SQL Server with SQL Server Engine and SQL Server Analysis Services (2008 R2). The physical name of the server is SQ21. For beeing flexible we created a dns alias (Host A) which points to this server (respectively the IP Adress of the Server).
This works fine in nearly all scenarios
- Sql server management studio
- Deplyoing of SAAs Projects (Deployment Server)
We have one problem. If we want process the saas database i get an error:
"Error in relational Module. With the Datasource with ID could not be established a connecton"(attention, this is a tranlsation made by me from german, so the exact term could be slightly different)
As soon as I change the Datasource-Server Property back to the physical server it works.
What could be the problem? Kerberos? Or could it be that the both servers (sql server engine and saas) are on the same server?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（2）
我遇到了同样的问题并且能够找到解决方案。您必须在服务器上禁用严格的名称检查，并向注册表中的 BackConnectionHostNames 列表添加一个与您要使用的别名相匹配的条目。有关执行这两项操作的详细信息，请参阅本文的解决方法方法#1（不必担心该文章适用于 SharePoint；该过程适用于使用环回检查进行身份验证的任何应用程序，其中包括 SSAS 2005/2008）。您可能还需要一个与您的别名匹配的 SPN，因此如果在更改注册表（并重新启动）后它不起作用，请尝试添加 SPN。
I had this same issue and was able to find a fix. You have to disable strict name checking on the server and add an entry to the BackConnectionHostNames list in the registry that matches the alias you want to use. See workaround method #1 of this article for details on doing both (don't worry that the article is for SharePoint; the procedure applies to any app that uses loopback checking for authentication, which includes SSAS 2005/2008). You may also need an SPN that matches your alias, so if it doesn't work after making the registry changes (and rebooting), try adding the SPN also.
一台机器是否有多个 IP 地址？如果是这样，则可能是 MSSQL 没有侦听 DNS 主机名解析的地址。
也可能是 DNS 条目尚未传播，或者由于某些其他原因，您的服务器未将主机名解析为正确的 IP 地址。从 SQL Server 计算机上的命令提示符处键入
（当然，使用 DNS 主机名代替 host.domain.com，并且末尾的“.”很重要）。您应该得到类似这样的信息：
如果最后一个地址未绑定到 SQL Server 或者您没有得到答案，那就是问题所在。
Does the machine have more than one IP address? If so, it could be that MSSQL is not listening on the address to which the DNS host name resolves.
It could also be that the DNS entry has not propagated yet, or for some other reason your server is not resolving the host name to the correct IP address. From a command prompt on the SQL Server machine, type
(use the DNS host name in place of host.domain.com, of course, and the "." at the end is important). You should get something like this:
If that last address is not bound to the SQL Server or you don't get an answer, that's the issue.