通过 SSMS 连接时 SQL Server 2012 集成服务失败 [英] SQL Server 2012 Integration Services failed when connecting thru SSMS
问题描述
我最近安装了 SQL Server 2012，我主要使用默认设置.数据库工作正常，我可以愉快地使用 SSMS(SQL Server Management Studio)进行连接，但是当我连接到集成服务服务器时，我收到此消息
<块引用>连接到计算机上的 Integration Services 服务localhost"失败并出现以下错误:访问被拒绝."
默认情况下，只有管理员才能访问集成服务服务.在 Windows Vista 和更高版本上，该过程必须是以管理权限运行以连接到集成服务服务.有关信息，请参阅帮助主题如何配置对服务的访问.
这是截图
我不知道为什么，但我是域管理员并且对服务器拥有完全权限.还有为什么当我从我的桌面连接时它可以成功连接，只有当我从服务器本身连接时才会出现这个问题.如何解决此问题，以便我可以使服务器上的 SSMS 连接到其 Integration Services 实例.
据我所知，用户访问控制，或 UAC，基本上可以拦截对您的组成员身份的请求，因此在这种情况下，它似乎阻止了您的成员身份传递给 SQL Server.>
其他人在他们的评论中指出，您可能仍需要右键单击并以管理员身份运行 SSMS.
正如一位敏锐的观察者所指出的这是一个快速修复，而不是一个真正的解决方案.人们不应该只是以管理员身份运行东西.这些安全墙的存在是有原因的"我同意.UAC 旨在让 Windows 用户进入最小权限原则思维模式 - 只升级到强大的帐户在需要的时候.问题是众所周知，SSMS 与 UAC 不能很好地配合".在我看来，这给您留下了三个选择
- 您可以关闭 UAC 并完成工作
- 让 UAC 开启并告诉你的老板你无法工作
- 编写自己的不受 UAC 影响的查询工具
I had recently installed SQL server 2012 and I used mostly the default settings. Database works fine and I can happily connect using SSMS (SQL Server Management Studio) but when I connect to the Integration Services Server I get this message
Connecting to the Integration Services service on the computer "localhost" failed with the following error: "Access is denied."
By default, only administrators have access to the Integration Services service. On Windows Vista and later, the process must be running with administrative privileges in order to connect to the Integration Services service. See the help topic for information on how to configure access to the service.
here is the screenshot
I am not sure why but I am the domain admin and have full rights over the server. Also why when I connect from my Desktop it can successfully connect, only if I connect from the server itself which gives me this issues. How do I fix this so that I can make SSMS on the server connect to its Integration Services instance.
As I understand it, User Access Control, or UAC, can basically intercept requests for your group membership so in this case, it appears it was preventing your membership getting passed to SQL Server.
Others have noted in their comments that you may still need to right click and run SSMS as an Administrator.
As noted by an astute observer "This is a quick-fix, not a real solution. People shouldn't just be running stuff as administrator. These security walls are in place for a reason" And I agree. UAC is designed to get Windows users into a Principle of least privilege mindset - only escalate to a powerful account when required. The issue is that SSMS is known to not "play well" with UAC. As I see it, this leaves you with three options
- You can turn off UAC and get your work done
- Leave UAC on and tell your boss you are unable to work
- Write your own query tool that is not affected by UAC
这篇关于通过 SSMS 连接时 SQL Server 2012 集成服务失败的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！
