|
We are in the process of migrating from SQL Server 2008 Reporting Services to SQL Server 2008 R2 Reporting Services. The only issue I have is migrating a custom data extension. I copied the custom dll to the bin files and made the changes to the various config files. The custom extension doesn’t appear in the data source type drop down in Report Manager. Does the dll need to be recompiled and then copied to the bin folders? If so, what steps are required to recompile the dll so the SQL Server 2008 R2 Reporting Services can use it? Thanks for any help on this.
(comments are locked)
|
|
Followed all these steps to a tee... the bottom line being that the dll was created under 2008 and I believe it needs to be recompiled under 2008 r2. Running the upgrade advisor on the old SQL Server 2008 reporting services instance seems to confirm this. The MSDN article doesn’t mention that custom data extensions probably need to be recompiled. Here’s a copy of the section that addresses this: If your installation includes custom report items, assemblies, or extensions, you must redeploy the custom components. If you are not using custom components, skip to "Configure the Report Server". To redeploy the custom components, do the following:
That said, I am working with the applications developer group to try the recompile. Did you add the Extension elements in RSReportServer.config for the report server and RSReportDesigner.config for Report Designer?
Sep 12 '12 at 11:41 AM
Usman Butt
Sure did... We've been using custom data extensions for years and the migration from 2005 to 2008 went smoothly. I did see some postings that indicated some changes between how SQL Server 2008 and SQL Server 2008 R2 use/manage custom data extensions. I'm going to try the recompile and see what happens.
Sep 12 '12 at 11:50 AM
PAMatt
(comments are locked)
|

