CLR Procedure not beeing seen by Reporting Services

I have written a CLR stored procedure and loaded it up into SQL... I
can run from there but when I reference it from Reporting Services, I
get an error saying that the stored procedure does not exist. IT
DOES!!!
There was a post in this group where the answer was to have the Command
Type set to Text and use EXEC... The challenge with that solution is
passing parameters doesn't seem to work this way.
I have seen where people have written a T-SQL "wrapper" for the
procedure but that yeilds the same results for me.
Any help would be appreciated.Make sure the login username and password as defined in your reporting
services datasource does have rights on the stored procedure.
Simply right click the stored procedure in enterprise manager, click
permissions and grant 'exec' rights to the user being used in the
datasource.|||I am not sure why I would need to that since we are running under
integrated security. I did try to give myself explicit permissions on
the proc as you suggested and still no luck. Does the assembly need to
be strong named?
nickismyname wrote:
> Make sure the login username and password as defined in your reporting
> services datasource does have rights on the stored procedure.
> Simply right click the stored procedure in enterprise manager, click
> permissions and grant 'exec' rights to the user being used in the
> datasource.|||Before continuing, make sure that CLR Integration is enabled on the SQL
server. To do this, simply execute the system stored procedure
sp_configure on the SQL Server with advanced options enabled:
EXEC sp_configure @.configname = 'Show Advanced Options', @.configvalue =1
RECONFIGURE WITH OVERRIDE
GO
EXEC sp_configure
Look for a record where the name is clr enabled and check its run_value
- it should be 1. If it's not, you'll need to set it to 1 in order to
to enable CLR Integration in SQL Server 2005. To do this, execute the
following T-SQL code:
EXEC sp_configure @.configname = 'clr enabled', @.configvalue = 1
RECONFIGURE WITH OVERRIDE
GO
There are three ways you can execute the above code against the SQL
Server:
SQL Server 2000 Query Analyzer
SQL Server 2005 SQLCMD Console Utility
SQL Server 2005 Management Studio|||It is... That was one of the first things that I did... The whole MS
"off-by-default" thing on their new baby servers can be frustrating.
Plus the proc wouldn't run from Sql Management Studio if it was off...
I did get a T-Sql "wrapper" proc to work (not sure why it wasn't
before) but I don't think this is the best solution. If you have any
other thoughts, I would love to hear them...
Thanks again
nickismyname wrote:
> Before continuing, make sure that CLR Integration is enabled on the SQL
> server. To do this, simply execute the system stored procedure
> sp_configure on the SQL Server with advanced options enabled:
> EXEC sp_configure @.configname = 'Show Advanced Options', @.configvalue => 1
> RECONFIGURE WITH OVERRIDE
> GO
> EXEC sp_configure
> Look for a record where the name is clr enabled and check its run_value
> - it should be 1. If it's not, you'll need to set it to 1 in order to
> to enable CLR Integration in SQL Server 2005. To do this, execute the
> following T-SQL code:
> EXEC sp_configure @.configname = 'clr enabled', @.configvalue = 1
> RECONFIGURE WITH OVERRIDE
> GO
> There are three ways you can execute the above code against the SQL
> Server:
> SQL Server 2000 Query Analyzer
> SQL Server 2005 SQLCMD Console Utility
> SQL Server 2005 Management Studio