Remotely logged into the server where SQL Server Integration Service was running.These are the steps I followed: DCOM User Group Membership
SQL MANAGEMENT STUDIO 2008 R2 WILL NOT START WINDOWS
In this case the Integration Service was part of a SQL Server 2008 R2 installation and was hosted in a Windows 2008 R2 server.
I was pretty sure there was a better solution than making someone a Windows or SQL admin.Īs it turns out, a user needs to have certain permissions enabled against the DCOM component for Integration Service to remotely access it with a tool like Management Studio. I started to look at the error message closely and tried to make some sense of it. I did not want him to be an administrator even in a development box, so Once his Windows AD account was added as a local Administrator in the development box, things looked okay. Promptly rolling back his elevated permissions, I decided to look at the Windows side of things.
Next he was made a db_owner in the msdb database, this did not help either. Going against all security best practices and knowing I was committing a cardinal sin, I assigned his account to the sysadmin server role. I just wanted the problem to go away so I started with some elevated permissions, hoping my wild guesswork would help. Initially I tried to resolve the issue by adding his Windows account as a user in the msdb database and then assigning the account under db_ssadmin role. Like so many other DBAs, my first instinct was to resolve the issue rather than investigating its root cause.
0 kommentar(er)
