Upgrade SQL 2008 to R2 with Reporting Services with Custom Authentication and Security Extensions
Hi Folks, I am not sure, if i am writing to the right section, but... I have installed System Center Operation Manager 2007 R2 which currently uses MS SQL 2008 with SP1 and Reporting Services. SCOM uses Reporting Services and added some Custom Authentication and Security Extensions to Reporting Services when I installed Reporting feature. When I tried to upgrade to SQL 2008 R2, installer complained about these custom extensions and denied me to continue with migration process. Is there any way how to migrate to R2 with these extensions ? Thank you :)
January 19th, 2011 5:14am

Hi, 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: 1.Determine whether the assemblies are supported or need recompilation: Custom authentication extensions created for the SQL Server 2000 release must be recompiled. Custom rendering extensions for SQL Server 2008 Reporting Services must be rewritten using the Rendering Object Model (ROM). HTML 3.2 and HTML OWC renderers are not supported in SQL Server 2008 Reporting Services. Other custom assemblies should not require recompilation. 2.Move the assemblies to the new report server and Report Manager \bin folders. In SQL Server 2008, the report server binaries are located in \Program files\Microsoft SQL Server\MSRS10.MSSQLSERVER\Reporting Services\ReportServer\bin for the default SQL Server 2008 Reporting Services instance. 3.Modify the configuration files to add entries for your custom component. The entries will vary depending on the kind of assembly you are using. For instructions on where to place files and add configuration entries, see the following: a.Deploying a Custom Assembly b.How to: Deploy a Custom Report Item c.Deploying a Data Processing Extension d.Deploying a Delivery Extension e.Deploying a Rendering Extension f.Implementing a Security Extension See http://msdn.microsoft.com/en-us/library/ms143724.aspx for more details on how to migrate a Reporting Services Installation. thanks, Jerry
Free Windows Admin Tool Kit Click here and download it now
January 23rd, 2011 8:56pm

Hi, 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: 1.Determine whether the assemblies are supported or need recompilation: Custom authentication extensions created for the SQL Server 2000 release must be recompiled. Custom rendering extensions for SQL Server 2008 Reporting Services must be rewritten using the Rendering Object Model (ROM). HTML 3.2 and HTML OWC renderers are not supported in SQL Server 2008 Reporting Services. Other custom assemblies should not require recompilation. 2.Move the assemblies to the new report server and Report Manager \bin folders. In SQL Server 2008, the report server binaries are located in \Program files\Microsoft SQL Server\MSRS10.MSSQLSERVER\Reporting Services\ReportServer\bin for the default SQL Server 2008 Reporting Services instance. 3.Modify the configuration files to add entries for your custom component. The entries will vary depending on the kind of assembly you are using. For instructions on where to place files and add configuration entries, see the following: a.Deploying a Custom Assembly b.How to: Deploy a Custom Report Item c.Deploying a Data Processing Extension d.Deploying a Delivery Extension e.Deploying a Rendering Extension f.Implementing a Security Extension See http://msdn.microsoft.com/en-us/library/ms143724.aspx for more details on how to migrate a Reporting Services Installation. thanks, Jerry
January 23rd, 2011 8:56pm

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics