Install Reporting Services 2008 R2 in Sharepoint Integrated mode via command line

In this article, we will discuss a few things to have you installing Reporting Services 2008 R2 with SharePoint 2010 in ‘SharePoint Integrated mode’ – not NATIVE mode using a config file for the SQL set up (Reporting Services is a SQL product) and also integrating Reporting Services with SharePoint (the Central Admin stuff). Continue reading


Microsoft SharePoint reporting services SSRS or CRM ASSERT: Assertion failed! un-named assertion fired for component processing Microsoft.ReportingServices.Diagnostics.Utilities.InternalCatalogException

You may receive these errors when generating reports (often large reports) through Microsoft Sharepoint Reporting Services SRSS or Microsoft CRM.

This error appears in the report server log:

ASSERT: Assertion failed! un-named assertion fired for component processing Microsoft.ReportingServices.Diagnostics.Utilities.InternalCatalogException
This error will appear in your web browser when accessing the report:

Reporting Services Error An internal error occurred on the report server. See the error log for more details (rsInternalError)

Solution:
Install SQL Server 2005 Service Pack 3

The cause is SQL server timing values may be incorrect when you use Cool’n’Quiet technology in AMD processors or SpeedStep technology in Intel processors. It can also occur on virtual servers on VMware (Intel or AMD).

Here are some links I hope you may find useful:

Link 1:
http://blogs.msdn.com/b/mariae/archive/2007/12/10/reporting-services-internal-error.aspx

Link 1: Mentions that AMD Cool’n’Quiet settings is the culprit, on further reading on the internet, I have found out that this can occur on intel systems (SpeedStep technology) as well.

Link 2:
http://support.microsoft.com/default.aspx?scid=kb;EN-US;931279

Link 2: States that the issue is a drift may occur between CPU frequency values and the problem was first corrected in SQL 2005 SP 3.
The Microsoft KB article 931279 states that this can occur if we use the CPU stepping or various Windows OS ‘power schemes’ settings. While the former (CPU stepping) is a bit more tricky to check, it would be worth checking the power scheme settings (Start>run>powercfg.cpl).

Link 3:
http://support.microsoft.com/kb/955706/en-us (SQL 2005 SP 3)

Link 3 contains a list of bugs that are fixed by SP3. There evidence that it fixes the SQL server timing values – KB article 931279 (Link 2).