Re: SQL CLR Sproc isn't running right

Well here is the wierd thing... I put a handler on the info messages event
of the connection to see what was being said.. and I got a permissions error
back saying DBO doesn't have permission to insert records into the table...
why does DBO needs this? shouldn't it already have it? all my plain text
stored procedures work fine inserting data when executed as a user that has
no permissions to insert into a table... the user has execute permission on
all the stored procedures... so not sure why its saying DBO doesnt have
permission... any ideas? as for seeing the SP cant really show it since it
contains company info in it... but the assemblie's stored procedures do all
have execute permissions set for the role that the executing user is in...

"William Vaughn" <billvaNoSPAM@xxxxxxxxx> wrote in message
news:835BD744-5FC7-4298-9AAF-19C6844FA906@xxxxxxxxxxxxxxxx
What errors are being thrown? What does the SP do? What security setting
does it use? Can we see the SP?

--
__________________________________________________________________________
William R. Vaughn
President and Founder Beta V Corporation
Author, Mentor, Dad, Grandpa
Microsoft MVP
(425) 556-9205 (Pacific time)
Hitchhiker's Guide to Visual Studio and SQL Server (7th Edition)
____________________________________________________________________________________________
"Smokey Grindel" <nospam@xxxxxxxxxx> wrote in message
news:uEaLVQ3YIHA.5984@xxxxxxxxxxxxxxxxxxxxxxx
I have a stored procedure for SQL Server 2005 which is done with the
CLR... when its executed as a admin it works. when its executed as a
non-admin it doesn't work... any ideas? the user has permission to execute
the procedure on the server... seems to be something with the .NET SPROC's
that is going wierd




.

Relevant Pages

  • Re: Stored Procedure Ignoring Table Permissions
    ... --deny permission on table test to the user 'Myuser' ... --The DELETE permission was denied on the object 'test', ... grant execute ON object::dbo.myp ... The access front end calls these stored procedures and everything ...
    (microsoft.public.sqlserver.security)
  • Re: System.Security.SecurityException was unhandled
    ... The exception gave you the CLSID. ... the first thing to check might be whether the COM server ... assembly actually has the permission in question. ... When I execute the application I received and error message. ...
    (microsoft.public.dotnet.security)
  • Re: System.Security.SecurityException was unhandled
    ... assembly actually has the permission in question. ... Try and find the sorce of the security permission error, ... setting was done on both versions 1.1 and 2.0 .NET framework. ... When I execute the application I received and error message. ...
    (microsoft.public.dotnet.security)
  • Re: System.Security.SecurityException was unhandled
    ... Is it a must that I need to register the COM server to the machine using ... CAS permissions on the client machine, and the COM issue is a new problem. ... assembly actually has the permission in question. ... When I execute the application I received and error message. ...
    (microsoft.public.dotnet.security)
  • Re: System.Security.SecurityException was unhandled
    ... I was using Oracle so was getting an Oracle permission problem. ... setting was done on both versions 1.1 and 2.0 .NET framework. ... On the server or the client? ... When I execute the application I received and error message. ...
    (microsoft.public.dotnet.security)