April 2, 2013 at 7:02 pm
Hi
We installed SQL Server 2012 SP1 on Windows 2008R2(VM) and have setup DNS aliases for our servers.
I am an admin on the Windows server with SA access to the SQL server.
Current Issues:
I am able to connect to both Database Engine and Integration services using the Server Name.
I am able to connect to the Database Engine but not to the Integration Services using the Alias.
I have tried adding user explicitly to the Microsoft SQL Server Integration Services 11.0 on DCOM Config and restarted SSIS.
Added DisableLoopbackCheck, modified to 1 and have rebooted the server, still the error persists.
Below is the error message:
Cannot connect to <AliasName>.
===================================
Failed to retrieve data for this request. (Microsoft.SqlServer.Management.Sdk.Sfc)
------------------------------
For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft%20SQL%20Server&LinkId=20476
------------------------------
Program Location:
at Microsoft.SqlServer.Management.Sdk.Sfc.Enumerator.Process(Object connectionInfo, Request request)
at Microsoft.SqlServer.Management.SqlStudio.Explorer.ObjectExplorerService.ValidateConnection(UIConnectionInfo ci, IServerType server)
at Microsoft.SqlServer.Management.UI.ConnectionDlg.Connector.ConnectionThreadUser()
===================================
Connecting to the Integration Services service on the computer "AliasName" 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.
------------------------------
For help, click: http://go.microsoft.com/fwlink/?LinkId=220763
------------------------------
Program Location:
at Microsoft.SqlServer.Dts.Runtime.Application.GetServerInfo(String server, String& serverVersion)
at Microsoft.SqlServer.Dts.SmoEnum.DTSEnum.GetData(EnumResult erParent)
at Microsoft.SqlServer.Management.Sdk.Sfc.Environment.GetData()
at Microsoft.SqlServer.Management.Sdk.Sfc.Environment.GetData(Request req, Object ci)
at Microsoft.SqlServer.Management.Sdk.Sfc.Enumerator.GetData(Object connectionInfo, Request request)
at Microsoft.SqlServer.Management.Sdk.Sfc.Enumerator.Process(Object connectionInfo, Request request)
===================================
Connecting to the Integration Services service on the computer "AliasName" 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.
------------------------------
Program Location:
at Microsoft.SqlServer.Dts.Runtime.Wrapper.ApplicationClass.GetServerInfo(String bstrMachineName, String& serverVersion)
at Microsoft.SqlServer.Dts.Runtime.Application.GetServerInfo(String server, String& serverVersion)
Any insight would be helpful.
May 8, 2013 at 9:29 am
I was having the same issue today, and this helped to resolve it for me. Hope it works for you too. http://sqlbuzz.wordpress.com/2011/12/07/connecting-to-the-integration-services-service-on-the-computer-mirrorstand-failed-with-the-following-error-access-is-denied/
May 30, 2014 at 11:07 pm
Open SQL Management studio as Administrator and then connect to Integration service. Hope this resolves your issue.
March 30, 2016 at 11:53 am
Ops no luck...
Thanks.
April 10, 2016 at 8:13 pm
Unbelievable!!!
After going through a large number of posts that told me to change a lot of settings in windows, finally, I found this one!! It worked!! And so simple!!
Thank you very much Detty Thomas!
June 3, 2016 at 6:53 am
Right clicking and running SSMS as administrator worked for me as well. But I have to say, it seems pretty silly to have this issue - the credentials we're using to connect to the respective components of SQL Server (SSIS, SSAS, SSRS, etc.) ought to dictate whether or not we can get into them, not running SSMS as an administrator or not.
Viewing 6 posts - 1 through 5 (of 5 total)
You must be logged in to reply to this topic. Login to reply