permissions problems creating a linked server

I am trying to create a linked server in the management studio and am getting an error

"A required operation could not be completed. You must be a member of the sysadmin role to perform this operation"

I have tried giving the user rights via

GRANT ALTER ANY LINKED SERVER TO [DOM\user]

as well as adding them to the setupadmin group. No luck.

I can add the linked server via sp_addlinkedserver as the user.

Any ideas?After searching some more I came across this.

http://msdn2.microsoft.com/en-us/library/aa560998.aspx

Which states you must be a member of the sysadmin role to create a linked server to do this via the management tools. Any idea why?

When I script the GUI all of the SP's it calls are available to logins with the setupadmin role or who have been granted access to alter any linked server.

Permissions on stored procedures

Using Server Management Studio Express and SQL Server 2005 Express - is it possible to assign Exec permissions for users on a sproc by sproc basis. If so, how do I do this?

TIA

--
Mike BrindOk - I've found out how to do it. Just run a GRANT command in the Query Pane on the chosen procedure for the selected user.
sql

Permissions on a new stored procedure

Help!

I usually use SQL 2000 at work but upon deciding to work from home have installed and setup SQL express 2005. I use the management studio to write table and sps but for new sp I cannot find how to allow permission. I have been able to allow permission for all sps on the database I restored that I am now working on and have successfully allocated permissions to a new table but cannot do the same with the sp. The sp is viewable in the database but permission is denied when attempting to execute via my ASP script.

Any ideas?

Error Type:
Microsoft SQL Native Client (0x80040E09)
EXECUTE permission denied on object 'procBannerSlotList', database 'HotLizardWebsite', schema 'dbo'.

It seems after all this time I've managed to work it out for myself - so for anyone out there not aware of the solution - the solution is this:

In the database security - right click the role you wish permissions to be set for. Go to the Securables section, click Add and just add all objects belonging to dbo - I then just removed the dt prefixed objects that were not relevant - sp permissions now fully operational

Permissions Not Visible - SQL 2005 Management Studio

I'm trying to apply some security to my database, so i've created a role, added my user to the role and then set the security rights for the role. Everything work great, the security right behave exactly as defined...
However, when I go back the the Permissions pages, the values that i've already set don't appear in the lists (the all still work). In Fact they don't show up anywhere either in the permissions for the table / sp concerned or the right for the user or role.
Is it just me, or is it a problem with SQL 2005 Management Studio? or can anybody suggest a way of finding the securty rights of any given database object?
Microsoft SQL Server 2005 Beta 2
Microsoft SQL Server Management Studio 9.00.1116.00
Regards
Gary T

Security in SQL Server 2005 is Schema based, try these articles to get started. Hope this helps.
http://www.databasejournal.com/features/mssql/article.php/3481751

http://www.windowsitpro.com/Article/ArticleID/42031/42031.html?Ad=1

|||

This has got me completely confused !!!!
In my simple world...
I would create a database role and the give this role the required rights to my database objects i.e the tables (select, insert update etc), stored procedures (execute etc). I would then create user accounts and add them to the required database roles...
CREATE ROLE [MyDB_AccessRole]
...Table def's...
GRANT SELECT ON [dbo].[MyTable] TO [MyDB_AccessRole] ..etc
...SP defs ...
GRANT EXECUTE ON [dbo].[MySP] TO [MyDB_AccessRole] ..etc
CREATE USER [DBUser] FOR LOGIN [DBUser]
EXEC sp_addrolemember N'MyDB_AccessRole, N'DBUser'

So far so good... this still all works in SQL 2005 (althought it nevers shows the rights anywhere?)
Then we have schemas...
CREATE SCHEMA [MyDB_AccessSchema] AUTHORIZATION [MyDB_AccessRole] ?

Is is true that the schema is just like the role? (i.e. A collection of database objects and permissions) if so, why do we need both.
Has anybody any simple examples (for dummies like me) that would explain the different between a role and a schema.
Having tried to create a role, I stiil don;t seem to be able to see the rights the user, role or schema has.
regards
Gary T

permissions not 'sticking' with Yukon June CTP?

Hi,
I'm trying to assing permissions using the MS SQL Management studio on the
Yukon June CTP, but every time i assign permissions and press 'OK' and go
back to the permissions screen, it is gone. I am new to MSSQL -- do i need
to run a FLUSH PRIVELEGES or some equivalent command?
Thanks,
StephenStephen wrote:
> Hi,
> I'm trying to assing permissions using the MS SQL Management studio
> on the Yukon June CTP, but every time i assign permissions and press
> 'OK' and go back to the permissions screen, it is gone. I am new to
> MSSQL -- do i need to run a FLUSH PRIVELEGES or some equivalent
> command?
> Thanks,
> Stephen
Please post SQL Server 2005 issues in the 2005 newsgroups. These
newsgroups are currently for versions other than 2005.
http://www.microsoft.com/technet/community/newsgroups/server/sql.mspx
--
David Gugick
Quest Software
www.imceda.com
www.quest.comsql

permissions not 'sticking' with Yukon June CTP?

Hi,
I'm trying to assing permissions using the MS SQL Management studio on the
Yukon June CTP, but every time i assign permissions and press 'OK' and go
back to the permissions screen, it is gone. I am new to MSSQL -- do i need
to run a FLUSH PRIVELEGES or some equivalent command?
Thanks,
Stephen
Stephen wrote:
> Hi,
> I'm trying to assing permissions using the MS SQL Management studio
> on the Yukon June CTP, but every time i assign permissions and press
> 'OK' and go back to the permissions screen, it is gone. I am new to
> MSSQL -- do i need to run a FLUSH PRIVELEGES or some equivalent
> command?
> Thanks,
> Stephen
Please post SQL Server 2005 issues in the 2005 newsgroups. These
newsgroups are currently for versions other than 2005.
http://www.microsoft.com/technet/com...erver/sql.mspx
David Gugick
Quest Software
www.imceda.com
www.quest.com

permissions not 'sticking' with Yukon June CTP?

Hi,
I'm trying to assing permissions using the MS SQL Management studio on the
Yukon June CTP, but every time i assign permissions and press 'OK' and go
back to the permissions screen, it is gone. I am new to MSSQL -- do i need
to run a FLUSH PRIVELEGES or some equivalent command?
Thanks,
StephenStephen wrote:
> Hi,
> I'm trying to assing permissions using the MS SQL Management studio
> on the Yukon June CTP, but every time i assign permissions and press
> 'OK' and go back to the permissions screen, it is gone. I am new to
> MSSQL -- do i need to run a FLUSH PRIVELEGES or some equivalent
> command?
> Thanks,
> Stephen
Please post SQL Server 2005 issues in the 2005 newsgroups. These
newsgroups are currently for versions other than 2005.
http://www.microsoft.com/technet/co...server/sql.mspx
David Gugick
Quest Software
www.imceda.com
www.quest.com

Permissions Management

Hello,
I am trying to set up permissions to secure databases in our Developement. I
have set up "View any Database" to Deny at the Database level.
when i login as admin i see all the database while the rest see Master and
Temp DB. What do i have to do at the database level so i can make other
databases visible to appropriate personnel and also give them control such as
Create Tables, Update SP etc.
Thanks
MannyManny
If the user is an owner of db try the following
Create a new SQL login "login1"
? Create a user named ?login1? in master database
? Grant CREATE DATABASE to login1
? While impersonating login1, create a database called ?dbteste?
? Revoke CREATE DATABASE permission from login1
? Revoke VIEW ANY DATABASE permission from PUBLIC
? Register this server as login1
? From the ?login1? session, expand database tree. Now, you should see
master, tempdb, dbteste
? Grant VIEW ANY DATABASE to PUBLIC
? From the ?login1? session, you should see all the databases
"Manny Chohan" <MannyChohan@.discussions.microsoft.com> wrote in message
news:5E4EAE5B-E79D-408C-98AC-946C8EC0566E@.microsoft.com...
> Hello,
> I am trying to set up permissions to secure databases in our Developement.
> I
> have set up "View any Database" to Deny at the Database level.
> when i login as admin i see all the database while the rest see Master and
> Temp DB. What do i have to do at the database level so i can make other
> databases visible to appropriate personnel and also give them control such
> as
> Create Tables, Update SP etc.
> Thanks
> Manny|||So basically the user who is creating the database will be only one who can
view the database in the tree.
What i am trying to do is following:
I have users User1, User2, User3 and Databases as DB1, DB2 and DB3.
I would like to revoke Public from seeing all the databases.
User 1 should have access to DB1 (as DBO) and DB2 as read/write
User 2 should only have access to DB2 (DBO)
User 3 should have access to DB2 (DBO) and DB3 as read only.
Hope i am clear in explaining things
THanks
Manny
"Uri Dimant" wrote:
> Manny
> If the user is an owner of db try the following
> Create a new SQL login "login1"
> â?¢ Create a user named â'login1â' in master database
> â?¢ Grant CREATE DATABASE to login1
> â?¢ While impersonating login1, create a database called â'dbtesteâ'
> â?¢ Revoke CREATE DATABASE permission from login1
> â?¢ Revoke VIEW ANY DATABASE permission from PUBLIC
> â?¢ Register this server as login1
> â?¢ From the â'login1â' session, expand database tree. Now, you should see
> master, tempdb, dbteste
> â?¢ Grant VIEW ANY DATABASE to PUBLIC
> â?¢ From the â'login1â' session, you should see all the databases
>
>
> "Manny Chohan" <MannyChohan@.discussions.microsoft.com> wrote in message
> news:5E4EAE5B-E79D-408C-98AC-946C8EC0566E@.microsoft.com...
> > Hello,
> >
> > I am trying to set up permissions to secure databases in our Developement.
> > I
> > have set up "View any Database" to Deny at the Database level.
> >
> > when i login as admin i see all the database while the rest see Master and
> > Temp DB. What do i have to do at the database level so i can make other
> > databases visible to appropriate personnel and also give them control such
> > as
> > Create Tables, Update SP etc.
> >
> > Thanks
> >
> > Manny
>
>|||Manny,
VIEW ANY DATABASE is a server level permission and cannot be granted nor
denied at the database level. To accomplish what you wish to do, you can
deny the permission to the public role (rather than to individual users) and
put users in the db_owner role of the database(s) they should have access.
This would then allow them to see only databases which they have ownership
of.
With regards to granting/revoking DDL permissions, I suggest you try out the
tool SQL CodeSecure. It allows you to set DDL permissions very easily, as
well as audit all changes modifications made to a database and even rollback
changes or recover deleted objects.
You can download the application from this location:
http://www.sql-labs.com/downloads/SQLCodeSecure.zip
HTH.
"Manny Chohan" <MannyChohan@.discussions.microsoft.com> wrote in message
news:5E4EAE5B-E79D-408C-98AC-946C8EC0566E@.microsoft.com...
> Hello,
> I am trying to set up permissions to secure databases in our Developement.
> I
> have set up "View any Database" to Deny at the Database level.
> when i login as admin i see all the database while the rest see Master and
> Temp DB. What do i have to do at the database level so i can make other
> databases visible to appropriate personnel and also give them control such
> as
> Create Tables, Update SP etc.
> Thanks
> Manny

Permissions in SQL Server 2005 to allow users to view the Management Activity monitor?

For SQL Server 2000 we have a user login mapped to msdb with database role membership of db_datareader and public checked. This seems to allow the developers to view the Management Activity monitor. For SQL Server 2005 the same mapping is in place but the developers cannot view the Management Activity monitor. Developers are NOT granted the sysadmin role, and should not have that role.

What permissions need to be set for SQL Server 2005 to allow users to view the Management Activity monitor? They should not be allowed to take actions on the activities.

The Active Monitor tool requires VIEW SERVER STATE permission; this permission is required to select from DMVs such as sys.sysprocesses.

-Raul Garcia

SDE/T

SQL Server Engine

|||

Thank you so much! This did the trick.

Barb

|||

Does Management Studio Express support the Activity Monitor?

I've enabled VIEW SERVER STATE for admin and still can't find the Activity Monitor in the GUI.

Thanks

|||

Unfortunately I am not familiar with the different GUI tools available for SQL Express. I would recommend asking this question on the SQL Express forum (http://forums.microsoft.com/MSDN/ShowForum.aspx?ForumID=385&SiteID=1) instead.

Thanks,

-Raul Garcia

SDE/T

SQL Server Engine

|||

Where do you set this: To view the Activity Monitor the user needs VIEW SERVER STATE permission on a SQL Server 2005 server.

|||

The easiest way is to just open a connection (i.e. using sqlcmd or Management Studio) using your sysadmin credentials and issue the following statement:

GRANTVIEWSERVER STATETO <<login name>>

This will grant <<login_name>> VIEW ANY STATE permission.

-Raul Garcia

SDE/T

SQL Server Engine

Permissions in SQL Server 2005 to allow users to view the Management Activity monitor?

For SQL Server 2000 we have a user login mapped to msdb with database role membership of db_datareader and public checked. This seems to allow the developers to view the Management Activity monitor. For SQL Server 2005 the same mapping is in place but the developers cannot view the Management Activity monitor. Developers are NOT granted the sysadmin role, and should not have that role.

What permissions need to be set for SQL Server 2005 to allow users to view the Management Activity monitor? They should not be allowed to take actions on the activities.

The Active Monitor tool requires VIEW SERVER STATE permission; this permission is required to select from DMVs such as sys.sysprocesses.

-Raul Garcia

SDE/T

SQL Server Engine

|||

Thank you so much! This did the trick.

Barb

|||

Does Management Studio Express support the Activity Monitor?

I've enabled VIEW SERVER STATE for admin and still can't find the Activity Monitor in the GUI.

Thanks

|||

Unfortunately I am not familiar with the different GUI tools available for SQL Express. I would recommend asking this question on the SQL Express forum (http://forums.microsoft.com/MSDN/ShowForum.aspx?ForumID=385&SiteID=1) instead.

Thanks,

-Raul Garcia

SDE/T

SQL Server Engine

|||

Where do you set this: To view the Activity Monitor the user needs VIEW SERVER STATE permission on a SQL Server 2005 server.

|||

The easiest way is to just open a connection (i.e. using sqlcmd or Management Studio) using your sysadmin credentials and issue the following statement:

GRANT VIEW SERVER STATE TO <<login name>>

This will grant <<login_name>> VIEW ANY STATE permission.

-Raul Garcia

SDE/T

SQL Server Engine

Permissions in SQL Server 2005 to allow users to view the Management Activity monitor?

For SQL Server 2000 we have a user login mapped to msdb with database role membership of db_datareader and public checked. This seems to allow the developers to view the Management Activity monitor. For SQL Server 2005 the same mapping is in place but the developers cannot view the Management Activity monitor. Developers are NOT granted the sysadmin role, and should not have that role.

What permissions need to be set for SQL Server 2005 to allow users to view the Management Activity monitor? They should not be allowed to take actions on the activities.

The Active Monitor tool requires VIEW SERVER STATE permission; this permission is required to select from DMVs such as sys.sysprocesses.

-Raul Garcia

SDE/T

SQL Server Engine

|||

Thank you so much! This did the trick.

Barb

|||

Does Management Studio Express support the Activity Monitor?

I've enabled VIEW SERVER STATE for admin and still can't find the Activity Monitor in the GUI.

Thanks

|||

Unfortunately I am not familiar with the different GUI tools available for SQL Express. I would recommend asking this question on the SQL Express forum (http://forums.microsoft.com/MSDN/ShowForum.aspx?ForumID=385&SiteID=1) instead.

Thanks,

-Raul Garcia

SDE/T

SQL Server Engine

|||

Where do you set this: To view the Activity Monitor the user needs VIEW SERVER STATE permission on a SQL Server 2005 server.

|||

The easiest way is to just open a connection (i.e. using sqlcmd or Management Studio) using your sysadmin credentials and issue the following statement:

GRANT VIEW SERVER STATE TO <<login name>>

This will grant <<login_name>> VIEW ANY STATE permission.

-Raul Garcia

SDE/T

SQL Server Engine

Permissions for Connecting to Reporting Services in Management Studio

Hi,

We have a user in the System Administrator and System User roles of

2005 SSRS. He is able to connect to the website

(http://<servername>/Reports) and do whatever he needs to do.

But, when he tries to connect to Reporting Services in Management

Studio, he receives the following error:

===================================

Cannot connect to <servername>.

===================================

The machine could not

be found

(Microsoft.SqlServer.Management.UI.RSClient)

Program

Location:

at

Microsoft.SqlServer.Management.UI.RSClient.RSConnectionInfo.ParseServerName(String

serverName)

at

Microsoft.SqlServer.Management.UI.RSClient.RSConnectionInfo.RSTypeImpl.CreateSqlOlapConnectionInfoBase(UIConnectionInfo

ci)

at

Microsoft.SqlServer.Management.UI.RSClient.RSConnectionInfo.RSTypeImpl.GetConnectionObject(UIConnectionInfo

ci)

at

Microsoft.SqlServer.Management.UI.ConnectionDlg.RSType.GetConnectionObject(UIConnectionInfo

ci)

at

Microsoft.SqlServer.Management.UI.VSIntegration.ObjectExplorer.ObjectExplorer.ValidateConnection(UIConnectionInfo

ci, IServerType server)

at

Microsoft.SqlServer.Management.UI.ConnectionDlg.Connector.ConnectionThreadUser()

I added him to the Distributed COM Users group, in DCOM security I

added him to the Default Launch and Activation Permissions (Local

Launch, Remote Launch, Local Activation, Remote Activation), I gave him

all permissions to the root namespace (and sub-namespaces) in wmi.

After giving him these permissions, the error message changes slightly

(no longer does he get 'the machine name cannot be found'):

Program

Location:

at

System.Runtime.InteropServices.Marshal.ThrowExceptionForHRInternal(Int32

errorCode, IntPtr errorInfo)

at

System.Management.ManagementObjectCollection.ManagementObjectEnumerator.MoveNext()

at

Microsoft.SqlServer.Management.UI.RSClient.RSConnectionInfo.ParseServerName(String

serverName)

at

Microsoft.SqlServer.Management.UI.RSClient.RSConnectionInfo.RSTypeImpl.CreateSqlOlapConnectionInfoBase(UIConnectionInfo

ci)

at

Microsoft.SqlServer.Management.UI.RSClient.RSConnectionInfo.RSTypeImpl.GetConnectionObject(UIConnectionInfo

ci)

at

Microsoft.SqlServer.Management.UI.ConnectionDlg.RSType.GetConnectionObject(UIConnectionInfo

ci)

at

Microsoft.SqlServer.Management.UI.VSIntegration.ObjectExplorer.ObjectExplorer.ValidateConnection(UIConnectionInfo

ci, IServerType server)

at

Microsoft.SqlServer.Management.UI.ConnectionDlg.Connector.ConnectionThreadUser()

If

I add him to the local administrators group, he can connect using

Management Studio. But, that is not what we want to do. And, in fact,

we want to revoke any of these extra permissions that we have assigned

in order to try to get this working. Does anyone know what permissions

a person needs (likely in the OS) for connecting to Reporting Services

in Management Studio?

Thanks,

Michelle

Try granting permissions on \root\Microsoft\SqlServer\ReportServer\v9 namespace to Everyone.

As a workaround you can type in the url to report server instead of machine name. This will cause management studio to not go through the WMI code path to resolve report server url.

|||Thanks! The workaround worked. The dba used

http://<servername>/reportserver for the server name in

Management Studio and is able to connect to Reporting Services.

Michelle

Permissions for Connecting to Reporting Services in Management Studio

Hi,

We have a user in the System Administrator and System User roles of

2005 SSRS. He is able to connect to the website

(http://<servername>/Reports) and do whatever he needs to do.

But, when he tries to connect to Reporting Services in Management

Studio, he receives the following error:

===================================

Cannot connect to <servername>.

===================================

The machine could not

be found

(Microsoft.SqlServer.Management.UI.RSClient)

Program

Location:

at

Microsoft.SqlServer.Management.UI.RSClient.RSConnectionInfo.ParseServerName(String

serverName)

at

Microsoft.SqlServer.Management.UI.RSClient.RSConnectionInfo.RSTypeImpl.CreateSqlOlapConnectionInfoBase(UIConnectionInfo

ci)

at

Microsoft.SqlServer.Management.UI.RSClient.RSConnectionInfo.RSTypeImpl.GetConnectionObject(UIConnectionInfo

ci)

at

Microsoft.SqlServer.Management.UI.ConnectionDlg.RSType.GetConnectionObject(UIConnectionInfo

ci)

at

Microsoft.SqlServer.Management.UI.VSIntegration.ObjectExplorer.ObjectExplorer.ValidateConnection(UIConnectionInfo

ci, IServerType server)

at

Microsoft.SqlServer.Management.UI.ConnectionDlg.Connector.ConnectionThreadUser()

I added him to the Distributed COM Users group, in DCOM security I

added him to the Default Launch and Activation Permissions (Local

Launch, Remote Launch, Local Activation, Remote Activation), I gave him

all permissions to the root namespace (and sub-namespaces) in wmi.

After giving him these permissions, the error message changes slightly

(no longer does he get 'the machine name cannot be found'):

Program

Location:

at

System.Runtime.InteropServices.Marshal.ThrowExceptionForHRInternal(Int32

errorCode, IntPtr errorInfo)

at

System.Management.ManagementObjectCollection.ManagementObjectEnumerator.MoveNext()

at

Microsoft.SqlServer.Management.UI.RSClient.RSConnectionInfo.ParseServerName(String

serverName)

at

Microsoft.SqlServer.Management.UI.RSClient.RSConnectionInfo.RSTypeImpl.CreateSqlOlapConnectionInfoBase(UIConnectionInfo

ci)

at

Microsoft.SqlServer.Management.UI.RSClient.RSConnectionInfo.RSTypeImpl.GetConnectionObject(UIConnectionInfo

ci)

at

Microsoft.SqlServer.Management.UI.ConnectionDlg.RSType.GetConnectionObject(UIConnectionInfo

ci)

at

Microsoft.SqlServer.Management.UI.VSIntegration.ObjectExplorer.ObjectExplorer.ValidateConnection(UIConnectionInfo

ci, IServerType server)

at

Microsoft.SqlServer.Management.UI.ConnectionDlg.Connector.ConnectionThreadUser()

If

I add him to the local administrators group, he can connect using

Management Studio. But, that is not what we want to do. And, in fact,

we want to revoke any of these extra permissions that we have assigned

in order to try to get this working. Does anyone know what permissions

a person needs (likely in the OS) for connecting to Reporting Services

in Management Studio?

Thanks,

Michelle

Try granting permissions on \root\Microsoft\SqlServer\ReportServer\v9 namespace to Everyone.

As a workaround you can type in the url to report server instead of machine name. This will cause management studio to not go through the WMI code path to resolve report server url.

|||Thanks! The workaround worked. The dba used

http://<servername>/reportserver for the server name in

Management Studio and is able to connect to Reporting Services.

Michelle

Permissions for Connecting to Reporting Services in Management Stu

Hi,
We have a user in the System Administrator and System User roles of 2005
SSRS. He is able to connect to the website (http://<servername>/Reports) and
do whatever he needs to do. But, when he tries to connect to Reporting
Services in Management Studio, he receives the following error:
===================================
Cannot connect to <servername>.
===================================
The machine could not be found (Microsoft.SqlServer.Management.UI.RSClient)
--
Program Location:
at
Microsoft.SqlServer.Management.UI.RSClient.RSConnectionInfo.ParseServerName(String serverName)
at
Microsoft.SqlServer.Management.UI.RSClient.RSConnectionInfo.RSTypeImpl.CreateSqlOlapConnectionInfoBase(UIConnectionInfo ci)
at
Microsoft.SqlServer.Management.UI.RSClient.RSConnectionInfo.RSTypeImpl.GetConnectionObject(UIConnectionInfo ci)
at
Microsoft.SqlServer.Management.UI.ConnectionDlg.RSType.GetConnectionObject(UIConnectionInfo ci)
at
Microsoft.SqlServer.Management.UI.VSIntegration.ObjectExplorer.ObjectExplorer.ValidateConnection(UIConnectionInfo ci, IServerType server)
at
Microsoft.SqlServer.Management.UI.ConnectionDlg.Connector.ConnectionThreadUser()
I added him to the Distributed COM Users group, in DCOM security I added him
to the Default Launch and Activation Permissions (Local Launch, Remote
Launch, Local Activation, Remote Activation), I gave him all permissions to
the root namespace (and sub-namespaces) in wmi. After giving him these
permissions, the error message changes slightly (no longer does he get 'the
machine name cannot be found'):
Program Location:
at
System.Runtime.InteropServices.Marshal.ThrowExceptionForHRInternal(Int32
errorCode, IntPtr errorInfo)
at
System.Management.ManagementObjectCollection.ManagementObjectEnumerator.MoveNext()
at
Microsoft.SqlServer.Management.UI.RSClient.RSConnectionInfo.ParseServerName(String serverName)
at
Microsoft.SqlServer.Management.UI.RSClient.RSConnectionInfo.RSTypeImpl.CreateSqlOlapConnectionInfoBase(UIConnectionInfo ci)
at
Microsoft.SqlServer.Management.UI.RSClient.RSConnectionInfo.RSTypeImpl.GetConnectionObject(UIConnectionInfo ci)
at
Microsoft.SqlServer.Management.UI.ConnectionDlg.RSType.GetConnectionObject(UIConnectionInfo ci)
at
Microsoft.SqlServer.Management.UI.VSIntegration.ObjectExplorer.ObjectExplorer.ValidateConnection(UIConnectionInfo ci, IServerType server)
at
Microsoft.SqlServer.Management.UI.ConnectionDlg.Connector.ConnectionThreadUser()
If I add him to the local administrators group, he can connect using
Management Studio. But, that is not what we want to do. And, in fact, we want
to revoke any of these extra permissions that we have assigned in order to
try to get this working. Does anyone know what permissions a person needs
(likely in the OS) for connecting to Reporting Services in Management Studio?
Thanks,
MichelleMichelle wrote:
> Hi,
> We have a user in the System Administrator and System User roles of 2005
> SSRS. He is able to connect to the website (http://<servername>/Reports) and
> do whatever he needs to do. But, when he tries to connect to Reporting
> Services in Management Studio, he receives the following error:
> ===================================> Cannot connect to <servername>.
>
> ===================================> The machine could not be found (Microsoft.SqlServer.Management.UI.RSClient)
> --
> Program Location:
>
> at
> Microsoft.SqlServer.Management.UI.RSClient.RSConnectionInfo.ParseServerName(String serverName)
> at
> Microsoft.SqlServer.Management.UI.RSClient.RSConnectionInfo.RSTypeImpl.CreateSqlOlapConnectionInfoBase(UIConnectionInfo ci)
> at
> Microsoft.SqlServer.Management.UI.RSClient.RSConnectionInfo.RSTypeImpl.GetConnectionObject(UIConnectionInfo ci)
> at
> Microsoft.SqlServer.Management.UI.ConnectionDlg.RSType.GetConnectionObject(UIConnectionInfo ci)
> at
> Microsoft.SqlServer.Management.UI.VSIntegration.ObjectExplorer.ObjectExplorer.ValidateConnection(UIConnectionInfo ci, IServerType server)
> at
> Microsoft.SqlServer.Management.UI.ConnectionDlg.Connector.ConnectionThreadUser()
> I added him to the Distributed COM Users group, in DCOM security I added him
> to the Default Launch and Activation Permissions (Local Launch, Remote
> Launch, Local Activation, Remote Activation), I gave him all permissions to
> the root namespace (and sub-namespaces) in wmi. After giving him these
> permissions, the error message changes slightly (no longer does he get 'the
> machine name cannot be found'):
> Program Location:
>
> at
> System.Runtime.InteropServices.Marshal.ThrowExceptionForHRInternal(Int32
> errorCode, IntPtr errorInfo)
> at
> System.Management.ManagementObjectCollection.ManagementObjectEnumerator.MoveNext()
> at
> Microsoft.SqlServer.Management.UI.RSClient.RSConnectionInfo.ParseServerName(String serverName)
> at
> Microsoft.SqlServer.Management.UI.RSClient.RSConnectionInfo.RSTypeImpl.CreateSqlOlapConnectionInfoBase(UIConnectionInfo ci)
> at
> Microsoft.SqlServer.Management.UI.RSClient.RSConnectionInfo.RSTypeImpl.GetConnectionObject(UIConnectionInfo ci)
> at
> Microsoft.SqlServer.Management.UI.ConnectionDlg.RSType.GetConnectionObject(UIConnectionInfo ci)
> at
> Microsoft.SqlServer.Management.UI.VSIntegration.ObjectExplorer.ObjectExplorer.ValidateConnection(UIConnectionInfo ci, IServerType server)
> at
> Microsoft.SqlServer.Management.UI.ConnectionDlg.Connector.ConnectionThreadUser()
> If I add him to the local administrators group, he can connect using
> Management Studio. But, that is not what we want to do. And, in fact, we want
> to revoke any of these extra permissions that we have assigned in order to
> try to get this working. Does anyone know what permissions a person needs
> (likely in the OS) for connecting to Reporting Services in Management Studio?
> Thanks,
> Michelle
Hi Michelle,
I'm having a very similiar problem to yours and I was wondering if you
ever found a solution to your problem. I haven't found much about it
on the internet yet, but I'm going to continue my search today. I'll
let you know if I find anything.
Thanks,
Rob