Custom xml rendering extension not showing up after migration to 2008
Hi,
In SSRS 2005 I had a custom xml rendering extension with an xslt transformation specified in
RSReportServer.config file. It was configured like this:
<Render>
<Extension Name="PMB_XML" Type="Microsoft.ReportingServices.Rendering.XmlDataRenderer.XmlDataReport,Microsoft.ReportingServices.XmlRendering">
<OverrideNames>
<Name Language="en-US">My Customerlist XML</Name>
</OverrideNames>
<Configuration>
<DeviceInfo>
<Indented>True</Indented>
<XSLT>/PMB/Transforms/TransformCustomers.xsl</XSLT>
<FileExtension>xml</FileExtension>
</DeviceInfo>
</Configuration>
</Extension>
</Render>
This was working nicely, the format was available in the list of available export formats. Now we migrated to SSRS 2008, we configured it exactly the same and it doesn't show up in the list with available formats when trying to export. The path to the xsl
file is the same.
Anyone got ideas what could cause this problem?
Kind regards,
Kristof
October 5th, 2012 6:28am
Hi Kristof,
When migrate a Reporting Services installation, we should make the same modifications in the new RSReportServer.config file if we modified the RSReportServer.config file in the previous installation. If the installation includes custom report items, assemblies,
or extensions, we must redeploy the custom components.
For more detail about move custom extensions, please see:
the Move Custom Assemblies or Extensions part of the How to: Migrate a Reporting Services Installation:
http://msdn.microsoft.com/en-us/library/ms143724(v=sql.100).aspx
Deploying a Rendering Extension:
http://msdn.microsoft.com/en-us/library/ms154516(v=sql.100).aspx
If the information above does not help, please share the trace log files, so we can help to work out issue. The trace log file is located at \Microsoft SQL Server\<SQL Server Instance>\Reporting Services\LogFiles.
Regards,
Fanny Liu
Fanny Liu
TechNet Community Support
Free Windows Admin Tool Kit Click here and download it now
October 9th, 2012 5:40am
Thanks for your Help Fanny.
We solved it by installing SQL server 2008 sp1 CU3
Regards,
Kristof
October 10th, 2012 4:03am