Showing posts with label custom. Show all posts
Showing posts with label custom. Show all posts

Friday, March 9, 2012

Problem deploying custom report item. Items shows in preview screen in VS, but not in server dep

I have developed a custom report item that works fine in design and preview mode while in Visual Studio. I cannot get it to show up on my deployed reports. Here's what I have done so far:

1. Deployed the report using Visual Studio

2. updated the rsreportserver.config file with the following entry:

<ReportItems>
<ReportItem Name="PedigreeChart" Type="Uabr.Rap.PedigreeChart.PedigreeChartRenderer, Uabr.Rap.PedigreeChart" />
</ReportItems>

3. Updated the rssrvpolicy.config file with the following entry.

<CodeGroup
class="UnionCodeGroup"
version="1"
PermissionSetName="FullTrust"
Description="This code group grants Uabr.Rap.PedigreeChart.dll FUllTrust permission. ">
<IMembershipCondition
class="UrlMembershipCondition"
version="1"
Url="C:\Program Files\Microsoft SQL Server\MSSQL.3\Reporting Services\ReportServer\bin\Uabr.Rap.PedigreeChart.dll" />
</CodeGroup>

I've also tried using the StrongNameMembershipCondition with no better results.

4. The dll and its dependencies are copied to the bin directory of the report server.

5. When I load a report with this custom report item on it, the report loads fine with no errors or warnings in the log file (even with verbose tracing). The area where the custom item should be is just white. It's almost like Reporting Services isn't registering the item correctly.

This is particularly frustrating because the report works fine in Visual Studio - apparently I configured that correctly. Any suggestions would be greatly appreciated. I'm stumped.

Hello,

I'm having the exact same problem that you describe. I am also stumped and was wondering if you've found a solution to this problem?

Thanks

|||I got it working, but I'm honestly not sure what I did to get it to work. I ended up granting all assemblies on the server fulltrust, which wasn't my preference but seemed to take care of the issue. However I'm still not sure if that was the item that fixed things. What I am sure about was that is was some configuration issue and not an assembly problem in my case because all I did was srcrew with the configuration for a while. It was a frustrating experience and I'm sorry I can't help more.|||

Hi,

I hab the same problem in the beginning. What solved it for me was that ALL assemblies being used by the CRI have to be trusted, including unmanaged C++ DLLs if there are any. First I listed each DLL but then I gave all my DLLs a strong name and now it works with only the strong name membership condition.

For debugging I enabled something named like 'assembly load logging' on the local report server. I also tried attaching to the worker process in order to read the debugging messages in VS if I remember that right.

Hth,

Thomas

Problem deploying custom report item. Items shows in preview screen in VS, but not in server dep

I have developed a custom report item that works fine in design and preview mode while in Visual Studio. I cannot get it to show up on my deployed reports. Here's what I have done so far:

1. Deployed the report using Visual Studio

2. updated the rsreportserver.config file with the following entry:

<ReportItems>
<ReportItem Name="PedigreeChart" Type="Uabr.Rap.PedigreeChart.PedigreeChartRenderer, Uabr.Rap.PedigreeChart" />
</ReportItems>

3. Updated the rssrvpolicy.config file with the following entry.

<CodeGroup
class="UnionCodeGroup"
version="1"
PermissionSetName="FullTrust"
Description="This code group grants Uabr.Rap.PedigreeChart.dll FUllTrust permission. ">
<IMembershipCondition
class="UrlMembershipCondition"
version="1"
Url="C:\Program Files\Microsoft SQL Server\MSSQL.3\Reporting Services\ReportServer\bin\Uabr.Rap.PedigreeChart.dll" />
</CodeGroup>

I've also tried using the StrongNameMembershipCondition with no better results.

4. The dll and its dependencies are copied to the bin directory of the report server.

5. When I load a report with this custom report item on it, the report loads fine with no errors or warnings in the log file (even with verbose tracing). The area where the custom item should be is just white. It's almost like Reporting Services isn't registering the item correctly.

This is particularly frustrating because the report works fine in Visual Studio - apparently I configured that correctly. Any suggestions would be greatly appreciated. I'm stumped.

Hello,

I'm having the exact same problem that you describe. I am also stumped and was wondering if you've found a solution to this problem?

Thanks

|||I got it working, but I'm honestly not sure what I did to get it to work. I ended up granting all assemblies on the server fulltrust, which wasn't my preference but seemed to take care of the issue. However I'm still not sure if that was the item that fixed things. What I am sure about was that is was some configuration issue and not an assembly problem in my case because all I did was srcrew with the configuration for a while. It was a frustrating experience and I'm sorry I can't help more.|||

Hi,

I hab the same problem in the beginning. What solved it for me was that ALL assemblies being used by the CRI have to be trusted, including unmanaged C++ DLLs if there are any. First I listed each DLL but then I gave all my DLLs a strong name and now it works with only the strong name membership condition.

For debugging I enabled something named like 'assembly load logging' on the local report server. I also tried attaching to the worker process in order to read the debugging messages in VS if I remember that right.

Hth,

Thomas

Problem deploying custom report item. Items shows in preview screen in VS, but not in server dep

I have developed a custom report item that works fine in design and preview mode while in Visual Studio. I cannot get it to show up on my deployed reports. Here's what I have done so far:

1. Deployed the report using Visual Studio

2. updated the rsreportserver.config file with the following entry:

<ReportItems>
<ReportItem Name="PedigreeChart" Type="Uabr.Rap.PedigreeChart.PedigreeChartRenderer, Uabr.Rap.PedigreeChart" />
</ReportItems>

3. Updated the rssrvpolicy.config file with the following entry.

<CodeGroup
class="UnionCodeGroup"
version="1"
PermissionSetName="FullTrust"
Description="This code group grants Uabr.Rap.PedigreeChart.dll FUllTrust permission. ">
<IMembershipCondition
class="UrlMembershipCondition"
version="1"
Url="C:\Program Files\Microsoft SQL Server\MSSQL.3\Reporting Services\ReportServer\bin\Uabr.Rap.PedigreeChart.dll" />
</CodeGroup>

I've also tried using the StrongNameMembershipCondition with no better results.

4. The dll and its dependencies are copied to the bin directory of the report server.

5. When I load a report with this custom report item on it, the report loads fine with no errors or warnings in the log file (even with verbose tracing). The area where the custom item should be is just white. It's almost like Reporting Services isn't registering the item correctly.

This is particularly frustrating because the report works fine in Visual Studio - apparently I configured that correctly. Any suggestions would be greatly appreciated. I'm stumped.

Hello,

I'm having the exact same problem that you describe. I am also stumped and was wondering if you've found a solution to this problem?

Thanks

|||I got it working, but I'm honestly not sure what I did to get it to work. I ended up granting all assemblies on the server fulltrust, which wasn't my preference but seemed to take care of the issue. However I'm still not sure if that was the item that fixed things. What I am sure about was that is was some configuration issue and not an assembly problem in my case because all I did was srcrew with the configuration for a while. It was a frustrating experience and I'm sorry I can't help more.|||

Hi,

I hab the same problem in the beginning. What solved it for me was that ALL assemblies being used by the CRI have to be trusted, including unmanaged C++ DLLs if there are any. First I listed each DLL but then I gave all my DLLs a strong name and now it works with only the strong name membership condition.

For debugging I enabled something named like 'assembly load logging' on the local report server. I also tried attaching to the worker process in order to read the debugging messages in VS if I remember that right.

Hth,

Thomas

Problem deploying Custom Report Item

Hello,

I am having a problem with deploying a CRI.

On my local machine the CRI works fine, only at the development machine it doens't works.

I did the following steps:

copy the .dll to the C:\Program Files\Microsoft Visual Studio 8\Common7\IDE\PrivateAssemblies

copy the .dll to the C:\Program Files\Microsoft SQL Server\MSSQL.4\Reporting Services\ReportServer\bin

put this code in rsreportserver.config:

<ReportItems>

<ReportItem Name="BusinessConnectDiagram" type="LogicaCMG.BusinessConnect.DiagrammingCRI.GenerateDiagramRenderer,LogicaCMG.BCDiagramming"/>

</ReportItems>

put this code in rssrvpolicy.config:

<CodeGroup

class="UnionCodeGroup"

Version="1"

PermissionSetName="FullTrust"

Name="BusinessConnectCodeGroup"

Description="Code group for the Business connect diagrammer">

<IMembershipCondition

class="StrongNameMembershipCondition"

version="1"

PublicKeyBlob="002400000480000094000000060200000024000052534131000400000100010051C346CB2A79947C83804E550CF1561729DB2B5C7DEFF93758E419F16390A295DF4906ADD8FD9A29559D5E3C8BFA73D8D21B64724B1B0E688091C1541FD54D5290D6968C73E9ACA842B1E42AB3DE369F7B545933C8E101A737BB7D22F937921E7F02E00C5121D1DC312DBE96154E5A4E47BD7F489A655A09CF08EABCFB6AB7C1"

/>

</CodeGroup>

put this code in rsreportdesigner.config

<ReportItems>

<ReportItem Name="BusinessConnectDiagram" type="LogicaCMG.BusinessConnect.DiagrammingCRI.GenerateDiagramRenderer,LogicaCMG.BCDiagramming"/>

</ReportItems>

<ReportItemDesigner>

<ReportItem Name="BusinessConnectDiagram" Type="LogicaCMG.BusinessConnect.DiagrammingCRI.GenerateDiagramDesigner,LogicaCMG.BCDiagramming" />

</ReportItemDesigner

I get the following error message:

Could not load file or assembly 'ReportingServicesWebServer,

Also when i stop Reporting Services it won't start again. I get a timeout.

Hi,

I am also getting the same error. Even my Report manager is not working.

But, as i was digging thru, I was able to get it working by doing some changes in the Encryption Keys options in the Report Server Configuration manager. But it stopped again by giving some security exception for the CRi assembly.

Can u tell me, how you got the PublicKeyBlob value in rssrvpolicy.config file?

Thanks,

Problem deploying a custom renderer on MSRS 2005.

Hi,

I have been struggling to deploy a custom rendering extension onto
Reporting services 2005. I have followed all the steps given in the
MSDN article
http://msdn.microsoft.com/msdnmag/issues/05/02/customrenderers/defaul...

Especially -

1. Copied the dll generated to the reporting service bin folder.

2. Made the entry in C:\Program Files\Microsoft SQL Server\MSSQL.
3\Reporting Services\ReportServer\rsreportserver.config file as
<Extension Name="CUSTOM_RENDERER"
Type="MSDNMagazine.CustomRSRenderer.Renderer,MSDNMagazine.CustomRSRenderer"-/


3. Made an entry in C:\Program Files\Microsoft SQL Server\MSSQL.
3\Reporting Services\ReportServer\rssrvpolicy.config file as

<CodeGroup class="UnionCodeGroup" version="1"
PermissionSetName="FullTrust" Name="Custom Render Extension"
Description="This code group grants data extensions full trust.">
<IMembershipCondition class="UrlMembershipCondition" version="1"
Url="C:\Program Files\Microsoft SQL Server\MSSQL.3\Reporting Services
\ReportServer\bin\MSDNMagazine.CustomRSRenderer.dll"/>
</CodeGroup>

I am able to see the extension being listed in the Report manager list
of available rendering options,
But I get the following error from the report server when I try
exporting to the custom rendering extension


An attempt has been made to use a rendering extension that is not
registered for this report server.
Description: An unhandled exception occurred during the execution of
the current web request. Please review the stack trace for more
information about the error and where it originated in the code.

Exception Details: System.Exception: An attempt has been made to use a
rendering extension that is not registered for this report server.

Source Error:

An unhandled exception was generated during the execution of the
current web request. Information regarding the origin and location of
the exception can be identified using the exception stack trace
below.

Stack Trace:

[Exception: An attempt has been made to use a rendering extension that
is not registered for this report server.]
Microsoft.Reporting.WebForms.ServerReport.ServerUrlRequest(Boolean
isAbortable, String url, Stream outputStream, String& mimeType,
String& fileNameExtension) +489
Microsoft.Reporting.WebForms.ServerReport.InternalRender(Boolean
isAbortable, String format, String deviceInfo, NameValueCollection
urlAccessParameters, Stream reportStream, String& mimeType, String&
fileNameExtension) +958

Microsoft.Reporting.WebForms.ServerReportControlSource.RenderReport(String
format, String deviceInfo, NameValueCollection additionalParams,
String& mimeType, String& fileExtension) +84

Microsoft.Reporting.WebForms.ExportOperation.PerformOperation(NameValueColl-ection
urlQuery, HttpResponse response) +143
Microsoft.Reporting.WebForms.HttpHandler.ProcessRequest(HttpContext
context) +75

System.Web.CallHandlerExecutionStep.System.Web.HttpApplication.IExecutionSt-ep.Execute()
+154
System.Web.HttpApplication.ExecuteStep(IExecutionStep step,
Boolean& completedSynchronously) +64

Looking at the logs of the report server at Max trace level, gives me
the following dump


w3wp!processing!b!03/01/2007-22:35:22:: e ERROR: Throwing
Microsoft.ReportingServices.ReportProcessing.ReportProcessingException:
An attempt has been made to use a rendering extension that is not
registered for this report server., ;
Info:
Microsoft.ReportingServices.ReportProcessing.ReportProcessingException:
An attempt has been made to use a rendering extension that is not
registered for this report server.
w3wp!chunks!b!03/01/2007-22:35:22:: v VERBOSE: ###
ID=3f94a6f1-8ff7-448c-8cf3-494ab8fe4837, Length=0, CompressedLength=0,
TimeCompressing=0, TimeUncompressing=0, Ratio=0, Buffering=0,
Permanent=False
w3wp!library!b!03/01/2007-22:35:22:: v VERBOSE: Transaction rollback.
w3wp!webserver!b!03/01/2007-22:35:22:: e ERROR: Reporting Services
error Microsoft.ReportingServices.Diagnostics.Utilities.RSException:
An attempt has been made to use a rendering extension that is not
registered for this report server. >
Microsoft.ReportingServices.ReportProcessing.ReportProcessingException:
An attempt has been made to use a rendering extension that is not
registered for this report server.
at
Microsoft.ReportingServices.ReportProcessing.ReportRendererFactory.GetRende-rer(String
format, IReportServerInformation serverInfo)
at
Microsoft.ReportingServices.ReportProcessing.ReportProcessing.CreateRendere-r(String
format)
at
Microsoft.ReportingServices.ReportProcessing.ReportProcessing.RenderSnapsho-t(CreateReportChunk
createChunkCallback, RenderingContext rc, GetResource
getResourceCallback)
at
Microsoft.ReportingServices.Library.RenderSnapshotAction.Render()
at
Microsoft.ReportingServices.Library.RSService.RenderFromSessionNoCache(Cata-logItemContext
reportContext, ClientRequest session, RenderingResult& result)
at
Microsoft.ReportingServices.Library.RSService.RenderFromSession(CatalogItem-Context
reportContext, ClientRequest session, Warning[]& warnings,
ParameterInfoCollection& effectiveParameters)
at
Microsoft.ReportingServices.Library.RSService.RenderNext(CatalogItemContext
reportContext, ClientRequest session, Warning[]& warnings,
ParameterInfoCollection& effecectiveParameters, String[]&
secondaryStreamNames)
at
Microsoft.ReportingServices.Library.RenderNextCancelableStep.Execute()
at
Microsoft.ReportingServices.Diagnostics.CancelablePhaseBase.ExecuteWrapper(-)
End of inner exception stack trace
at
Microsoft.ReportingServices.Diagnostics.CancelablePhaseBase.ExecuteWrapper(-)
at
Microsoft.ReportingServices.Library.RenderNextCancelableStep.RenderNext(RSS-ervice
rs, CatalogItemContext reportContext, ClientRequest session, JobType
type, Warning[]& warnings, ParameterInfoCollection&
effectiveParameters, String[]& secondaryStreamNames)
at
Microsoft.ReportingServices.WebServer.ReportServiceHttpHandler.RenderReport-(HttpResponseStreamFactory
streamFactory)
at
Microsoft.ReportingServices.WebServer.ReportServiceHttpHandler.DoStreamedOp-eration(StreamedOperation
operation)
at
Microsoft.ReportingServices.WebServer.ReportServiceHttpHandler.RenderItem(I-temType
itemType)
at
Microsoft.ReportingServices.WebServer.ReportServiceHttpHandler.RenderPageCo-ntent()
at
Microsoft.ReportingServices.WebServer.ReportServiceHttpHandler.RenderPage()
w3wp!dbcleanup!9!3/1/2007-22:35:41:: v VERBOSE: Starting database
cleanup.
w3wp!library!9!3/1/2007-22:35:41:: v VERBOSE: Call to CleanBatch()
w3wp!dbcleanup!9!3/1/2007-22:35:41:: v VERBOSE: Cleaning expired
sessions from DB
w3wp!library!9!3/1/2007-22:35:41:: v VERBOSE: Transaction begin.
w3wp!library!9!3/1/2007-22:35:41:: v VERBOSE: Transaction commit.
w3wp!dbcleanup!9!3/1/2007-22:35:41:: v VERBOSE: Cleaning expired cache
from DB
w3wp!library!9!3/1/2007-22:35:41:: v VERBOSE: Transaction begin.
w3wp!library!9!3/1/2007-22:35:41:: v VERBOSE: Transaction commit.
w3wp!dbcleanup!9!3/1/2007-22:35:41:: v VERBOSE: Cleaning orphaned
snapshots from DB
w3wp!library!9!3/1/2007-22:35:41:: v VERBOSE: Transaction begin.
w3wp!library!9!3/1/2007-22:35:41:: v VERBOSE: Transaction commit.
w3wp!library!9!3/1/2007-22:35:41:: i INFO: Cleaned 0 batch records, 0
policies, 0 sessions, 0 cache entries, 0 snapshots, 0 chunks, 0
running jobs, 0 persisted streams
w3wp!dbcleanup!9!3/1/2007-22:35:41:: v VERBOSE: Database cleanup
executed.

Any inputs will be of great help to me. Thanks

Does deploying a custom rendering extension require Reboot of the

machine. I restarted MSSQL Report Server service on the server and this

_did not_ solve the problem.

What is the difference between deploying a custom Data Extension and a

custom Rendering Extension. The former is being deployed properly while

the later isn't.

Atleast, Please point me to some documentation on frequently

encountered problems with custom rendering extensions. I tried

searching on the net but there seems to be lack of any helping

information.
Thanks in advance.