André Krijnen

I just started out today to restore some Content Databases to test out my new created features on my development environment, to check if everything works as planned. But yet, I’ve figured out that I had some issues creating and deleting sites.

So I checked the ULS logs and nothing to see, I checked event viewer and also there no errors containing the message which I had: “Supported method not found” or something in that other.

Well I remember when I installed Service Pack 1 of SharePoint Server 2010 and tried to remove a site I had the same message. This was related to some bug or something. So I installed June CU Refresh and that worked perfectly. Well in this case I had both installed, so that shouldn’t be the problem.

So I checked the status of my Content Databases and what I noticed was that the schema version of the database wasn’t the same version as June CU Refresh. And the message was that I could update. Also the strange notice is that my Content Databases aren’t updated when you restore a database and attach it to SharePoint.

So what I did was run with powershell the following script:


$contentdb = Get-SPContentDatabase | Where-Object {$_.Name -match "WSS_ContentDB" }
Upgrade-SPContentDatabase -Identity $contentdb


Voila, content database is getting updated.

Today was the day I could install Service Pack 1 for Reporting Services 2008 R2 at a customer which has SharePoint 2010 with Reporting Services 2008 r2 integrated. Before Service Pack 1 we had alot of performance issues with Reporting Services. It didn’t perform while the hardware was more then sufficient. Sometimes it took more then 30 ms to load a simple report.

Today I installed the Service Pack 1 for Reporting Services, and it didn’t take alot of time to install it. Even while it is virtualized.

I installed the following updates:

• SQL Server 2008 R2 Service Pack 1

Also what I did is installing the following features from the SQL Server 2008 R2 Service Pack 1 Feature Pack:

• SQLSERVER2008_ASADOMD10.msi
• SQLSERVER2008_ASAMO10.msi
• SQLSERVER2008_ASOLEDB10.msi
• SqlCmdLnUtils.msi
• SharedManagementObjects.msi
• PowerShellTools.msi

All are installed on the server which runs SharePoint 2010 and Reporting Services 2008 r2.

After reboot. I checked the performance again to check if it installed correctly without any errors. I did, SharePoint Server ran, and started some reports. While it took the same time to run the Reports like before I took the time to install some more from the feature pack.

I installed the SQL Server 2008 Native Client on each server running SharePoint. When you run the prerequisite installer it installs also the SQL Server 2008 Native Client. So when it was done, I rebooted the servers which had these updates.

When the SharePoint Server cames up, I ran the rsSharePoint.msi from the Feature Pack on every server in the SharePoint farm.

Run the installer like this: msiexec /i rsSharePoint.msi skipca=1

It checks if the addin is installed, and asks if you want to update the Package. Of course, yes.

It takes about 30 seconds to install and it is done.

Now I started SharePoint and checked the Reports which I ran before, and the performance increased more then I could imagine. Even SharePoint reacted more snappy as before. It looks like Microsoft made some major performance increasements on the Native Client and the Reporting Services Add-In for SharePoint.

My advice: install it!