March 28, 2019 at 10:15 am
Hi
I have just installed SQL Server 2016 including SSIS on a couple of Windows 2016 servers
However when trying to connect to SSIS on the actual SQL Server I am getting access denied.
I am a local administrator
I have SQL SA rights
The SQL & SSIS Service accounts are members of the local administrator group
All Googling points me at DCOM config and the Distributed users group which I am well aware of as pretty standard for setting up non-admin users however local server Administrators shouldn’t need adding.
However, I have added both myself and the service accounts to the Distributed COM Users Group and added them to Microsoft SQL Server Integration Services 13.0 & 14.0 under DCOM Config granting them Launch and Activation permissions & Access Permissions but to no avail
I am sure it must be something pretty simple that I am not aware of as I have never installed SQL 2016 before but used to 2008R2.
Does anyone have any suggestions ?
March 28, 2019 at 11:36 am
david.webley - Thursday, March 28, 2019 10:15 AMHiI have just installed SQL Server 2016 including SSIS on a couple of Windows 2016 servers
However when trying to connect to SSIS on the actual SQL Server I am getting access denied.
I am a local administrator
I have SQL SA rights
The SQL & SSIS Service accounts are members of the local administrator groupAll Googling points me at DCOM config and the Distributed users group which I am well aware of as pretty standard for setting up non-admin users however local server Administrators shouldn’t need adding.
However, I have added both myself and the service accounts to the Distributed COM Users Group and added them to Microsoft SQL Server Integration Services 13.0 & 14.0 under DCOM Config granting them Launch and Activation permissions & Access Permissions but to no avail
I am sure it must be something pretty simple that I am not aware of as I have never installed SQL 2016 before but used to 2008R2.
Does anyone have any suggestions ?
It could be a few different things. You can try doing as Run As and open SSMS as an administrator - and it doesn't matter if you are an administrator wherever.
In the full error message, see if it mentions the version of the tools, SSMS or however it's worded. If it does, try using the version of SSMS that is specifically for 2016 (16.x)
Sue
March 29, 2019 at 8:24 am
Great Yes It was an SSMS issue. Installed v16 and all is well.
I was aware of this requirement restrictions with SSIS but got a bit lost when Management studio got separated from the core install and version no's no longer in sync.
SSMS v18 with SQL Server 2019 for example.
Thank you for your assistance
March 29, 2019 at 8:29 am
david.webley - Friday, March 29, 2019 8:24 AMGreat Yes It was an SSMS issue. Installed v16 and all is well.
I was aware of this requirement restrictions with SSIS but got a bit lost when Management studio got separated from the core install and version no's no longer in sync.SSMS v18 with SQL Server 2019 for example.
Thank you for your assistance
Your welcome and thanks for posting back. It's become a rather common issue that confuses most - it's not just you 🙂
Sue
Viewing 4 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply