{"id":503,"date":"2012-03-04T16:47:00","date_gmt":"2012-03-04T16:47:00","guid":{"rendered":"https:\/\/www.geekmungus.co.uk\/?p=503"},"modified":"2022-11-05T10:53:42","modified_gmt":"2022-11-05T10:53:42","slug":"sql-reporting-services-and-sharepoint-2007-broken-by-windows-updates","status":"publish","type":"post","link":"https:\/\/geekmungus.co.uk\/?p=503","title":{"rendered":"SQL Reporting Services and SharePoint 2007 Broken by Windows Updates"},"content":{"rendered":"\n
Heres a nasty little problem, we have a SharePoint farm that consists of 4 servers, two Web Front Ends, and application server and a SQL server.<\/p>\n\n\n\n
This is Microsoft SharePoint 2007 Enterprise SP2 running on Microsoft Windows 2003 R2 SP2 (32-bit), all was well until a recent automatic update was installed which broke the application server.<\/p>\n\n\n\n
The application server hosted the \u201cSharePoint Central Administration Website\u201d and also SQL Reporting Services 2008 that was linked into the SharePoint farm.<\/p>\n\n\n\n
PROBLEM(S)<\/strong><\/p>\n\n\n\n
The following morning after the update the Central Administration Website started to show the following error: \u201cCannot connect to the configuration database.\u201d<\/p>\n\n\n\n
A reboot of all the farm servers and tried again, still no joy, I could not access the \u201cCentral Administration Website\u201d running on the application server.<\/p>\n\n\n\n
It\u2019s worth noting however the web front ends were unaffected and happily connected to the databases, and our main SharePoint site collection was accessible and worked fine. To make things more confusing the backup \u201cCentral Administration Website\u201d that ran on one of the web front end servers also worked fine, but this showed that the configuration database was not corrupted which was something.<\/p>\n\n\n\n
Another of the problems caused was that the SQL Reporting services server was dead too, it complained it could not access the database with the following errors (in the event log) when starting up:<\/p>\n\n\n\n
Event Type: Error\nEvent Source: Report Server (MSSQLSERVER)\nEvent Category: Management\nEvent ID: 107\nDate: 04\/03\/2012\nTime: 09:08:32\nUser: N\/A\nComputer: OAKSMFSPAPP01\nDescription:\nReport Server (MSSQLSERVER) cannot connect to the report server database.\n \nFor more information, see Help and Support Center at http:\/\/go.microsoft.com\/fwlink\/events.asp.<\/code><\/pre>\n\n\n\n
However also in the SQL Reporting server logs that in my case were located here:<\/p>\n\n\n\n
03\/04\/2012-08:42:43:: e ERROR: Throwing Microsoft.ReportingServices.Diagnostics.Utilities.InternalCatalogException: An internal error occurred on the report server. See the\nerror log for more details., ;\n Info: Microsoft.ReportingServices.Diagnostics.Utilities.InternalCatalogException: An internal error occurred on the report server. See the error\nlog for more details. ---> System.TypeInitializationException: The type initializer for 'Microsoft.ReportingServices.Diagnostics.CatalogItemNameUtility' threw an exception. --->\nSystem.Runtime.InteropServices.SEHException: External component has thrown an exception.<\/code><\/pre>\n\n\n\n
Something that many posts on the Internet advised was to re-run the \u201cSharePoint products and Technologies Configuration Wizard\u201d to try to fix SharePoints issues. There was also talk of running the psconfig command to reinstall SharePoint on the server. However both methods resulted in the same error message as shown below:<\/p>\n\n\n\n
\u201cAn exception of type system.typeinitializationException was thrown. Additional exception information: The type initializer for \u2018System.Data.Common.DbConnectionOptions\u2019 threw an exception.\u201d<\/p>\n\n\n\n<\/figure>\n\n\n\n
But the above string: \u201cSystem.Data.Common.DbConnectionOptions\u201d turned out to be the key to it, this is a component of .net framework and is used by both SQL Reporting Services and SharePoint, this was failing therefore neither application could contact the SQL server databases.<\/p>\n\n\n\n
CAUSE and SOLUTION<\/strong><\/p>\n\n\n\n
It turns out that when we looked through the list of all the updates installed and checked the event logs there were a list of about 10 updates that got applied, however, the two specific ones were those related to Microsoft .NET Framework 2.0 Service Pack 2.<\/p>\n\n\n\n
KB2656352<\/p>\n\n\n\n
KB2633880<\/p>\n\n\n\n
Removing these two updates and rebooting of all the farm servers resolved the issues we were seeing and the \u201cSharePoint Central Administration WebSite\u201d and SQL Reporting services started to work again as expected.<\/p>\n\n\n\n
Other bits I also tried:<\/p>\n\n\n\n
Reinstall of .net 2 and 3 using the following commands:<\/p>\n\n\n\n
I also tried to reinstall the SQL Client using the sqlncli.msi installer pack, as it appeared to be missing, in my case it was located here, I just ran this to ensure SQL client was installed correctly.<\/p>\n\n\n\n
![\"\"](\"https:\/\/www.geekmungus.co.uk\/wp-content\/uploads\/2021\/07\/image-69.png\")
<\/figure>\n\n\n\n