Showing posts with label computer. Show all posts
Showing posts with label computer. Show all posts

Friday, March 9, 2012

Permissions

hi all

my computer = NZ3 (sql Server)
my computer = the report server

I can design / view / publish to local host (myserver)
others in domain can only view local host (myserver) and no content

so to test added one person - as content manager
he can now see all reports - but when he goes to run
gets the error cannot create a connection to the datasource?

I am using sql server 2005 standard

where else should I be changing or setting permissions

thanks
jewel

Hi,

seems that you are using Integrated Authentication. Although the user can manage the content (the actual report / permissions etc) he does not have access to the database. If you want to grant him access to the appropiate tables with the data, you will have to priviledge him on the database, otherwise he won′t be able to connect nor access the database. Open the SSMS and navigate to the security node of the server. Add the Windows user as a login and grant him the appropiate rights in the database.

HTH, Jens K. Suessmeyer.

http://www.sqlserver2005.de

|||

thanks Jens

that enabled him to see now cool.

So when I have a group set up - do I have to add each one in the Security Logins to enable this to work?

thanks

Jewel

|||

Hi,

yes you need to Map those Windows User group to Security Node and then Assign them proper privilage for Database and Objects of Database for access as per the Role/Group.

Hemantgiri S. Goswami

Wednesday, March 7, 2012

Permission problems: Need help with CLR credentials

Hi everyone....

I have made a CLR stored procedure which goes to a shared folder on a remote computer. I am having permission problems when executing the stored procedure. (In case anyone is wondering, I am using the .NET SYSTEM.IO class)

I have done the following:

CREATE CREDENTIAL myuser
WITH IDENTITY = 'mydomain\myuser', SECRET = 'some56*Z';

CREATE LOGIN sam WITH PASSWORD = 'meowPw!a3';

ALTER LOGIN sam WITH CREDENTIAL = myuser;

...(other SQL so that SAM can execute the SP)

Now, I login to SQL Server using the new login, and when I try to execute the CLR stored procedure, I get "unknown username or bad password.".

I know 100% for sure that the account in the "MYUSER" credential has access. Is there something else I need to do?

You need to use Impersonation so that your CLR stored proc accesses external resources as your Windows user account, rather than the account that SQL Server is running under.

You can see an example of how to do this here: http://msdn2.microsoft.com/en-us/library/ms131068.aspx

If you are already doing this and it doesn't work, post the relevant clr code you're using.

Steven