Showing posts with label execution. Show all posts
Showing posts with label execution. Show all posts

Friday, February 24, 2012

Custom Code for a Parameter

I'm using a GAC-installed assembly as part of a Reporting Services

(2005) report. The code does not need any permissions beyond execution.

All it does it take today's date and calculate last week's start and

end date. It's all just datetime manipulations. All methods are static.

In

the VS2005 report designer, I can do everything fine. The code runs as

expected and defaults the parameters to the right date.

When I

upload the rdl to the Report Server, I get the message "Error during

processing of ‘Start’ report parameter.

(rsReportParameterProcessingError) ". If I override the "Start"

parameter, it doesn't give me that error anymore. Start should be the

Sunday of the previous week.

I have deployed the signed assembly to the GAC on the report server as well as the bin folder for reporting services. Because it doesn't need anything beyond execution, I shouldn't have to modify any config files, right? I have already restarted IIS & the Reporting Services service.

What am I missing?

You need to mark the assembly with AllowPartiallyTrustedCallersAttribute.Once you deploy it to PrivateAssemblies folder (C:\Program Files\Microsoft Visual Studio 8\Common7\IDE\PrivateAssemblies) you should be able to hit F5 to debug it with the Report Host and see if something else is erroring out.

|||That was it. :) Attaching the attribute solved the problem!|||

Hello,

I defined an input parameter with the default value of ("Input_From_Year") and use it in the query as @.fromYear. When I go to Preview I see the result fine, but when I say Debug-> Start I see the following error in the internet explorer. Error during processing of 'fromYear' report parameter. (rsReportParameterProcessingError),but If I remove @.fromYear in the query, internet explorer works fine. What is problem?

Thanks!

|||Not quite sure what you mean by Debug->Start and IE and what your setup is but if this works in the Report Designer but it doesn't work on the server (or under the Report Host), most likely it's a security issue. If your custom assembly requires more that just Execution trust you need to elevate its rights as shown in this article.|||

I means the report can works in the report designer,but it doesn't work on the server after i deployed it to the server.deploy successfully,why does it give me the message that is Error during processing of 'fromYear' report parameter.(rsReportParameterProcessingError),I am not sure whether it's a security issue,but I check my custom assemblies,it is fullturst.

and any other reasons more?

|||

Hi Jason,

even I am facing same problem, where I am also getting same error called "error during processing of 'Validate' parameter."

did you got any solution.

If yes please share the solution with me.

thanks in advance,

Ramesh KS

|||

Hi,

Am facing the same problem. Did any one got the solution, please do share.

TIA

|||

Teo,

Would I have this same issue trying to use System.DirectoryServices?

R

Custom Code for a Parameter

I'm using a GAC-installed assembly as part of a Reporting Services

(2005) report. The code does not need any permissions beyond execution.

All it does it take today's date and calculate last week's start and

end date. It's all just datetime manipulations. All methods are static.

In

the VS2005 report designer, I can do everything fine. The code runs as

expected and defaults the parameters to the right date.

When I

upload the rdl to the Report Server, I get the message "Error during

processing of ‘Start’ report parameter.

(rsReportParameterProcessingError) ". If I override the "Start"

parameter, it doesn't give me that error anymore. Start should be the

Sunday of the previous week.

I have deployed the signed assembly to the GAC on the report server as well as the bin folder for reporting services. Because it doesn't need anything beyond execution, I shouldn't have to modify any config files, right? I have already restarted IIS & the Reporting Services service.

What am I missing?

You need to mark the assembly with AllowPartiallyTrustedCallersAttribute.Once you deploy it to PrivateAssemblies folder (C:\Program Files\Microsoft Visual Studio 8\Common7\IDE\PrivateAssemblies) you should be able to hit F5 to debug it with the Report Host and see if something else is erroring out.

|||That was it. :) Attaching the attribute solved the problem!|||

Hello,

I defined an input parameter with the default value of ("Input_From_Year") and use it in the query as @.fromYear. When I go to Preview I see the result fine, but when I say Debug-> Start I see the following error in the internet explorer. Error during processing of 'fromYear' report parameter. (rsReportParameterProcessingError),but If I remove @.fromYear in the query, internet explorer works fine. What is problem?

Thanks!

|||Not quite sure what you mean by Debug->Start and IE and what your setup is but if this works in the Report Designer but it doesn't work on the server (or under the Report Host), most likely it's a security issue. If your custom assembly requires more that just Execution trust you need to elevate its rights as shown in this article.|||

I means the report can works in the report designer,but it doesn't work on the server after i deployed it to the server.deploy successfully,why does it give me the message that is Error during processing of 'fromYear' report parameter.(rsReportParameterProcessingError),I am not sure whether it's a security issue,but I check my custom assemblies,it is fullturst.

and any other reasons more?

|||

Hi Jason,

even I am facing same problem, where I am also getting same error called "error during processing of 'Validate' parameter."

did you got any solution.

If yes please share the solution with me.

thanks in advance,

Ramesh KS

|||

Hi,

Am facing the same problem. Did any one got the solution, please do share.

TIA

|||

Teo,

Would I have this same issue trying to use System.DirectoryServices?

R

Custom Code for a Parameter

I'm using a GAC-installed assembly as part of a Reporting Services

(2005) report. The code does not need any permissions beyond execution.

All it does it take today's date and calculate last week's start and

end date. It's all just datetime manipulations. All methods are static.

In

the VS2005 report designer, I can do everything fine. The code runs as

expected and defaults the parameters to the right date.

When I

upload the rdl to the Report Server, I get the message "Error during

processing of ‘Start’ report parameter.

(rsReportParameterProcessingError) ". If I override the "Start"

parameter, it doesn't give me that error anymore. Start should be the

Sunday of the previous week.

I have deployed the signed assembly to the GAC on the report server as well as the bin folder for reporting services. Because it doesn't need anything beyond execution, I shouldn't have to modify any config files, right? I have already restarted IIS & the Reporting Services service.

What am I missing?

You need to mark the assembly with AllowPartiallyTrustedCallersAttribute.Once you deploy it to PrivateAssemblies folder (C:\Program Files\Microsoft Visual Studio 8\Common7\IDE\PrivateAssemblies) you should be able to hit F5 to debug it with the Report Host and see if something else is erroring out.

|||That was it. :) Attaching the attribute solved the problem!|||

Hello,

I defined an input parameter with the default value of ("Input_From_Year") and use it in the query as @.fromYear. When I go to Preview I see the result fine, but when I say Debug-> Start I see the following error in the internet explorer. Error during processing of 'fromYear' report parameter. (rsReportParameterProcessingError),but If I remove @.fromYear in the query, internet explorer works fine. What is problem?

Thanks!

|||Not quite sure what you mean by Debug->Start and IE and what your setup is but if this works in the Report Designer but it doesn't work on the server (or under the Report Host), most likely it's a security issue. If your custom assembly requires more that just Execution trust you need to elevate its rights as shown in this article.|||

I means the report can works in the report designer,but it doesn't work on the server after i deployed it to the server.deploy successfully,why does it give me the message that is Error during processing of 'fromYear' report parameter.(rsReportParameterProcessingError),I am not sure whether it's a security issue,but I check my custom assemblies,it is fullturst.

and any other reasons more?

|||

Hi Jason,

even I am facing same problem, where I am also getting same error called "error during processing of 'Validate' parameter."

did you got any solution.

If yes please share the solution with me.

thanks in advance,

Ramesh KS

|||

Hi,

Am facing the same problem. Did any one got the solution, please do share.

TIA

|||

Teo,

Would I have this same issue trying to use System.DirectoryServices?

R

Custom Code for a Parameter

I'm using a GAC-installed assembly as part of a Reporting Services

(2005) report. The code does not need any permissions beyond execution.

All it does it take today's date and calculate last week's start and

end date. It's all just datetime manipulations. All methods are static.

In

the VS2005 report designer, I can do everything fine. The code runs as

expected and defaults the parameters to the right date.

When I

upload the rdl to the Report Server, I get the message "Error during

processing of ‘Start’ report parameter.

(rsReportParameterProcessingError) ". If I override the "Start"

parameter, it doesn't give me that error anymore. Start should be the

Sunday of the previous week.

I have deployed the signed assembly to the GAC on the report server as well as the bin folder for reporting services. Because it doesn't need anything beyond execution, I shouldn't have to modify any config files, right? I have already restarted IIS & the Reporting Services service.

What am I missing?

You need to mark the assembly with AllowPartiallyTrustedCallersAttribute.Once you deploy it to PrivateAssemblies folder (C:\Program Files\Microsoft Visual Studio 8\Common7\IDE\PrivateAssemblies) you should be able to hit F5 to debug it with the Report Host and see if something else is erroring out.

|||That was it. :) Attaching the attribute solved the problem!|||

Hello,

I defined an input parameter with the default value of ("Input_From_Year") and use it in the query as @.fromYear. When I go to Preview I see the result fine, but when I say Debug-> Start I see the following error in the internet explorer. Error during processing of 'fromYear' report parameter. (rsReportParameterProcessingError),but If I remove @.fromYear in the query, internet explorer works fine. What is problem?

Thanks!

|||Not quite sure what you mean by Debug->Start and IE and what your setup is but if this works in the Report Designer but it doesn't work on the server (or under the Report Host), most likely it's a security issue. If your custom assembly requires more that just Execution trust you need to elevate its rights as shown in this article.|||

I means the report can works in the report designer,but it doesn't work on the server after i deployed it to the server.deploy successfully,why does it give me the message that is Error during processing of 'fromYear' report parameter.(rsReportParameterProcessingError),I am not sure whether it's a security issue,but I check my custom assemblies,it is fullturst.

and any other reasons more?

|||

Hi Jason,

even I am facing same problem, where I am also getting same error called "error during processing of 'Validate' parameter."

did you got any solution.

If yes please share the solution with me.

thanks in advance,

Ramesh KS

|||

Hi,

Am facing the same problem. Did any one got the solution, please do share.

TIA

|||

Teo,

Would I have this same issue trying to use System.DirectoryServices?

R

Custom Code for a Parameter

I'm using a GAC-installed assembly as part of a Reporting Services

(2005) report. The code does not need any permissions beyond execution.

All it does it take today's date and calculate last week's start and

end date. It's all just datetime manipulations. All methods are static.

In

the VS2005 report designer, I can do everything fine. The code runs as

expected and defaults the parameters to the right date.

When I

upload the rdl to the Report Server, I get the message "Error during

processing of ‘Start’ report parameter.

(rsReportParameterProcessingError) ". If I override the "Start"

parameter, it doesn't give me that error anymore. Start should be the

Sunday of the previous week.

I have deployed the signed assembly to the GAC on the report server as well as the bin folder for reporting services. Because it doesn't need anything beyond execution, I shouldn't have to modify any config files, right? I have already restarted IIS & the Reporting Services service.

What am I missing?

You need to mark the assembly with AllowPartiallyTrustedCallersAttribute.Once you deploy it to PrivateAssemblies folder (C:\Program Files\Microsoft Visual Studio 8\Common7\IDE\PrivateAssemblies) you should be able to hit F5 to debug it with the Report Host and see if something else is erroring out.

|||That was it. :) Attaching the attribute solved the problem!|||

Hello,

I defined an input parameter with the default value of ("Input_From_Year") and use it in the query as @.fromYear. When I go to Preview I see the result fine, but when I say Debug-> Start I see the following error in the internet explorer. Error during processing of 'fromYear' report parameter. (rsReportParameterProcessingError),but If I remove @.fromYear in the query, internet explorer works fine. What is problem?

Thanks!

|||Not quite sure what you mean by Debug->Start and IE and what your setup is but if this works in the Report Designer but it doesn't work on the server (or under the Report Host), most likely it's a security issue. If your custom assembly requires more that just Execution trust you need to elevate its rights as shown in this article.|||

I means the report can works in the report designer,but it doesn't work on the server after i deployed it to the server.deploy successfully,why does it give me the message that is Error during processing of 'fromYear' report parameter.(rsReportParameterProcessingError),I am not sure whether it's a security issue,but I check my custom assemblies,it is fullturst.

and any other reasons more?

|||

Hi Jason,

even I am facing same problem, where I am also getting same error called "error during processing of 'Validate' parameter."

did you got any solution.

If yes please share the solution with me.

thanks in advance,

Ramesh KS

|||

Hi,

Am facing the same problem. Did any one got the solution, please do share.

TIA

|||

Teo,

Would I have this same issue trying to use System.DirectoryServices?

R

Tuesday, February 14, 2012

Cursors inside SQL Functions - Very long execution time

I have a report that requires the use of cursors within a function because we
don't have control over the design of the database. So, the datasource for
the report is as follows:
1. Report calls a Stored Proc
2. Stored Proc runs this statement: Select... dbo.Function()...
3. Inside the Function(), I loop through a cursor.
Now when I run this Stored Proc directly in Query Analyzer, it takes 3
seconds.
But, when the report is run through SQL Reporting Services, it takes 108
seconds. I ran a SQL Profiler and noticed that Reporting Services was using
.Net Provider and the provider is way too slow for running cursors
- 2000ms for .Net Provider vs 0ms for Query Analyzer.
Is there anything I can do other than finding a way out of using cursors?Assuming that you call a stored procedure from RS it makes absolutely no
difference as far as executing the procedure. Stored procedures execute on
the server. It is not like the dotnet provider is opening a cursor, it is
not, it calls the stored procedure and gets back the results. What is most
likely happening is one of two things. Sometime there can be a delay due to
security authentication. More likely, however, is that you are returning a
lot of records and the rendering is what is taking the time. What are you
rendering to? Html, pdf, excel? PDF and Excel take much longer to render to
than HTML. Are you using a filter? Filters bring over all the data and then
filters it. So, the key questions are, what are you rendering to and how
many records is the stored procedure returning.
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"Sanjay Gandhi" <SanjayGandhi@.discussions.microsoft.com> wrote in message
news:36286553-9F41-488F-BB24-4DC46C680168@.microsoft.com...
>I have a report that requires the use of cursors within a function because
>we
> don't have control over the design of the database. So, the datasource for
> the report is as follows:
> 1. Report calls a Stored Proc
> 2. Stored Proc runs this statement: Select... dbo.Function()...
> 3. Inside the Function(), I loop through a cursor.
> Now when I run this Stored Proc directly in Query Analyzer, it takes 3
> seconds.
> But, when the report is run through SQL Reporting Services, it takes 108
> seconds. I ran a SQL Profiler and noticed that Reporting Services was
> using
> .Net Provider and the provider is way too slow for running cursors
> - 2000ms for .Net Provider vs 0ms for Query Analyzer.
> Is there anything I can do other than finding a way out of using cursors?|||The number of records returned for the parameters I specified is only 69. And
I am rendering the report using the Reporting Server interface.
I may have solved this issue. I ran the Index Tuning Wizard on the query
used by the cursor and resulted in a 95% improvement. So that leads me to
think that when the cursor is run through Reporting Server, it did not use
the best execution plan. I'll do some more testing and see if that's it.
"Bruce L-C [MVP]" wrote:
> Assuming that you call a stored procedure from RS it makes absolutely no
> difference as far as executing the procedure. Stored procedures execute on
> the server. It is not like the dotnet provider is opening a cursor, it is
> not, it calls the stored procedure and gets back the results. What is most
> likely happening is one of two things. Sometime there can be a delay due to
> security authentication. More likely, however, is that you are returning a
> lot of records and the rendering is what is taking the time. What are you
> rendering to? Html, pdf, excel? PDF and Excel take much longer to render to
> than HTML. Are you using a filter? Filters bring over all the data and then
> filters it. So, the key questions are, what are you rendering to and how
> many records is the stored procedure returning.
>
> --
> Bruce Loehle-Conger
> MVP SQL Server Reporting Services
> "Sanjay Gandhi" <SanjayGandhi@.discussions.microsoft.com> wrote in message
> news:36286553-9F41-488F-BB24-4DC46C680168@.microsoft.com...
> >I have a report that requires the use of cursors within a function because
> >we
> > don't have control over the design of the database. So, the datasource for
> > the report is as follows:
> > 1. Report calls a Stored Proc
> > 2. Stored Proc runs this statement: Select... dbo.Function()...
> > 3. Inside the Function(), I loop through a cursor.
> >
> > Now when I run this Stored Proc directly in Query Analyzer, it takes 3
> > seconds.
> >
> > But, when the report is run through SQL Reporting Services, it takes 108
> > seconds. I ran a SQL Profiler and noticed that Reporting Services was
> > using
> > .Net Provider and the provider is way too slow for running cursors
> > - 2000ms for .Net Provider vs 0ms for Query Analyzer.
> >
> > Is there anything I can do other than finding a way out of using cursors?
>
>