Tag Archives: SharePoint 2010

SharePoint Language Pack Activation & Blob Cache Errors

1 Reply

Following the installation of SharePoint 2010 SP2 I noticed a large number of event log errors for the Publishing Cache on web front end servers.  The error was “An error occurred in the blob cache.  The exception message was “The system cannot fine the file specified. (Exception from HRESULT: 0x80070002)”.

BlobCache1

Looking deeper into the error using the ULSViewer I could see that the error was being caused by language pack files that could not be found.  The files could not be found because following the installation of the language pack the Publishing Infrastructure feature had not been reactivated.  The TechNet notes here state “After you install a new language pack, you must deactivate and then reactivate any language-specific features before you use the new language pack.”

In order to resolve the error I went into Site Settings -> Site collection features.  I deactivated the SharePoint Server Publishing Infrastructure, then activated the feature.  You need to do this out of hours and it does affect your SharePoint site while the feature is deactivated.

Advertisement

RSS Viewer Web Part Stops Working After Installing SharePoint 2010 SP2

2 Replies

Following the installation of SharePoint 2010 SP2 (KB2687453) I found that the RSS viewer web part had stopped working; the web part continually showed the loading image.

2010SP2RSS1

After some research I discovered that the issue was introduced in SharePoint 2010 February 12, 2013 cumulative update (KB2767793).  Some suggested fixes are listed on the SharePoint forums.

The first option is to add a Content Editor Web Part to any page with the RSS viewer web part and paste the JavaScript below into the web part in HTML view.  Although this works it’s not a realistic work around if you have many pages with the RSS viewer web part.

<script type=”text/javascript”>
function CustomUpdateFormDigest()
{
if(window._spPageContextInfo != null)
{
var $v_2 = window._spPageContextInfo;
var $v_3 = $v_2.webServerRelativeUrl;
var $v_4 = window._spFormDigestRefreshInterval;
UpdateFormDigest($v_3, $v_4);
}
}
CustomUpdateFormDigest();
</script>

The second option is to add the above script to the SharePoint master page, but I couldn’t get this to work.

The third option is to turn off web page security validation for the web application from Central Administration -> Manage web applications.  Highlight the affected web application and select General Settings from the ribbon.

2010SP2RSS2

 

Turning off web page security validation worked, but I was then unable to create any new sites or lists because I received the error “An unhandled exception occured in the Silverlight application SharePoint 2010.

I have just finished testing the August 13, 2013 cumulative update for SharePoint 2010 (KB2817570) and it appears to fix the RSS viewer issue without any side affects.

Open SharePoint 2010 Search Results In A New Window

1 Reply

Configuring SharePoint 2010 to open search results in a new window requires editing the XSL that determines the search result display.

Open your search results page and edit the page.  Choose Edit Web Part from the Search Core Results web part. Expand display properties and click on XSL Editor…

SPSearchNewWindow1

Copy and paste XSL into a tool like Notepadd++.  Search for the section

<div class=”srch-Title3″>

Scroll down and add the attribute for target.

SPSearchNewWindow2

Copy and paste the XSL back into the window in SharePoint.  Save and publish the page.

Updating SharePoint 2010 Web Parts For SharePoint 2013

Leave a reply

Following an upgrade from SharePoint 2010 to 2013 I deployed some custom web parts.  When loading the page I received the error “/_CONTROLTEMPLATES/WEBPARTNAME/VisualWebPart1/VisualWebPart1UserControl.ascx” does not exist.

2013WebPartError1

The error is caused by the web part looking in the \14\TEMPLATE\CONTROLTEMPLATES folder rather than \15\TEMPLATE\CONTROLTEMPLATES.  Open the web part solution in Visual Studio and change the _ascxPath string.  Original value below:

2013WebPartError2

 

Change the string to include the 15 folder.

2013WebPartError3

 

Rebuild and re-deploy the web part.

 

Upgrading SharePoint 2010 To SharePoint 2013 Part 5

4 Replies

These are notes from my first upgrade of SharePoint 2010 to SharePoint 2013.  The purpose of the upgrade is to carry out an initial test upgrade to find any issues etc.  I’m not replicating the environment in terms of server roles etc. everything is installed on one server with local SQL.  I followed the steps outlined here: http://technet.microsoft.com/en-us/library/cc303436.aspx

This is part 5, part 1 can be found here, part 2 here, part 3 here and part 4 here.

Upgrade a site collection to SharePoint 2013

Reference: http://technet.microsoft.com/en-us/library/jj219650.aspx

Once the databases have been upgraded you can upgrade individual site collections.  You will see the notification bar at the top of the site with the option Start now or Remind me later.

Before beginning the site collection upgrade run health checks from Site Settings -> Site Collection Administration -> Site collection health checks.

On the run site collection health checks page, click Start checks.

After reviewing the health check results begin the site collection upgrade.  From the Site Settings page, click Site collection upgrade beneath Site Collection Administration.

On the following page, click Upgrade this Site Collection.

Once the upgrade has completed verify the upgrade from the Upgrade status page.  Go to Site Settings -> Site Collection Administration -> Site collection upgrade.  On this page click Review Site Collection Upgrade Status.

Finally, review everything is working and looks as you’d expect.

Additional configuration tweaks

Grant the default content access account the  “Retrieve People Data for Search Crawlers” permission for the User Profile Service application.

Configure the object cache user accounts http://technet.microsoft.com/en-us/library/ff758656.aspx

Enable the blob cache http://technet.microsoft.com/en-us/library/ee424404.aspx

Upgrading SharePoint 2010 To SharePoint 2013 Part 4

4 Replies

These are notes from my first upgrade of SharePoint 2010 to SharePoint 2013.  The purpose of the upgrade is to carry out an initial test upgrade to find any issues etc.  I’m not replicating the environment in terms of server roles etc. everything is installed on one server with local SQL.  I followed the steps outlined here: http://technet.microsoft.com/en-us/library/cc303436.aspx

This is part 4, part 1 can be found here, part 2 here, part 3 here and part 5 here.

Upgrade content databases to SharePoint 2013

Reference: http://technet.microsoft.com/en-us/library/cc263299.aspx

The SharePoint 2010 web application is configured to use Windows authentication, but Claims based authentication is required to enable the advanced functionality of SharePoint 2013.  Check the authentication provider that’s in use from Central Administration -> Manage web applications.  Click on the web application, then select Authentication Providers from the ribbon.

I used the process described here to convert a SharePoint 2010 classic mode web application to SharePoint 2013 claims based authentication.  You start by creating the web application using PowerShell, then once the SharePoint 2010 databases have been mounted using the command below, you use PowerShell to convert the web application to claims based authentication.

Use SQL Server Management Studio to restore the SharePoint 2010 content and My Site databases.

Reapply customisations web parts and web.config changes.

Use Mount-SPContentDatabase to attach the restored database into the web application you just created. Repeat the process for the My Sites database.

Verify the database upgrade status in Central Administration -> Upgrade and Migration -> check upgrade status.

View database upgrade log files in %COMMONPROGRAMFILES%\Microsoft Shared\web server extensions\15\LOGS

Next Steps

Verify sites as working correctly in SharePoint 2010 mode.

Configure search and perform a full crawl.

Backup the farm.

Upgrading SharePoint 2010 To SharePoint 2013 Part 2

6 Replies

These are notes from my first upgrade of SharePoint 2010 to SharePoint 2013.  The purpose of the upgrade is to carry out an initial test upgrade to find any issues etc.  I’m not replicating the environment in terms of server roles etc. everything is installed on one server with local SQL.  I followed the steps outlined here: http://technet.microsoft.com/en-us/library/cc303436.aspx

This is part 2, part 1 can be found here, part 2 here, part 3 here, part 4 here and part 5 here.

Copy databases to the new farm for upgrade to SharePoint 2013

Reference: http://technet.microsoft.com/en-us/library/jj839720.aspx

As this is a test upgrade, don’t set the databases to read-only.

Backup all the SharePoint 2010 content databases and the databases for any service applications you’re going to upgrade.  See part 1 for upgradeable service applications.

Copy the SharePoint 2010 database backups to the SharePoint 2013 SQL server.

Restore the SharePoint 2010 database backups on the SharePoint 2013 SQL server.

If upgrading SQL server versions, change the database compatibility level to match the new SQL server version.

Upgrading SharePoint 2010 To SharePoint 2013 Part 1

4 Replies

These are notes from my first upgrade of SharePoint 2010 to SharePoint 2013.  The purpose of the upgrade is to carry out an initial test upgrade to find any issues etc.  I’m not replicating the environment in terms of server roles etc. everything is installed on one server with local SQL.  I followed the steps outlined here: http://technet.microsoft.com/en-us/library/cc303436.aspx

This is part 1, part 2 can be found here, part 3 here, part 4 here and part 5 here.

Create the SharePoint 2013 farm

Reference: http://technet.microsoft.com/en-us/library/cc263026.aspx

Before taking SQL backups of the SharePoint 2010 databases:

  • Stop the Web Analytics service application.  Remove any Web Analytics web parts or features from the SharePoint 2010 site
  • PowerPoint Broadcast Sites cannot be upgraded

Record the passphrase of the Secure Store service application.

Export the encryption key for the User Profile service application.

Build test server: Windows Server 2012 and SQL Server 2012.

Install SharePoint 2013, don’t run the SharePoint Products configuration Wizard.

Install SharePoint 2013 language packs.

Install SharePoint 2013 updates as required.

Run the SharePoint Products configuration Wizard and create a new farm.

Run the Farm Configuration Wizard to configure the farm.  Don’t configure the Business Data Connectivity, Managed Metadata, PerformancePoint Services, Search, Secure Store, or the User Profile service applications if you’re using them in SharePoint 2010 as their content can be copied from SharePont 2010 and upgraded.  Don’t create a site collection, so click cancel at the end of the wizard on the site collection creation page.

Configure incoming and outgoing email settings, configure the Farm Administrators group and blocked file types as per SharePoint 2010.  Configure usage and health data collection, diagnostic logging and settings and schedules for timer jobs.

If the Workflow Auto Cleanup timer job is disabled in SharePoint 2010 you must disable it in SharePoint 2013 too.

Add the SharePoint Central Administration website to Trusted Sites and disable Internet Explorer Enhanced security.

Create A SharePoint Document Library To Store SSRS Reports

In this post I’m going to describe the process of creating a SharePoint document library to store SSRS reports.  I’ll also show the process of taking a report from a separate SSRS instance and moving it into SharePoint.  The SharePoint farm used here has been setup in a configuration where SSRS is integrated with SharePoint.

Create a standard document library to store the reports, then from the ribbon select Library Settings.

SSRS Doc Lib 1

 

On the library settings screen, choose Advanced Settings.

SSRS Doc Lib 2

 

Choose the option to “Allow management of content types”.

SSRS Doc Lib 3

 

 

Return to the library settings page and select Add from existing site content types under the Content Types heading.

SSRS Doc Lib 4

 

 

From the “Select site content types from:” drop down, select Report Server Content Types.  Add all three content types to the library and click Ok.

 

SSRS Doc Lib 5

 

 

To export the SSRS report from the existing server, navigate to the reports server and the screen showing the report you wish to export. Click Show Details.

SSRS Doc Lib 6

 

Click the Edit icon next to the report to be exported.

SSRS Doc Lib 7

 

Navigate to the Properties page and click Edit below Report Definition.  This will allow you to download the rdl file of the report.

SSRS Doc Lib 8

 

Back in the SharePoint document library, show the ribbon and click Report Data Source from the New Document drop down.  Enter the same information that’s used for the report data source on the existing SSRS server.

SSRS Doc Lib 9

 

Next, from the ribbon select Upload Document and browse the the rdl file you downloaded earlier.  Change the content type to Report Builder Report and click Save.

SSRS Doc Lib 10

 

From the drop down for the report, select Manage Data Sources.

SSRS Doc Lib 11

 

Select the data source name that appears.

SSRS Doc Lib 12

 

Next, click on the button next to Data Source Link and from the following screen select the data source you created earlier and click Ok.

SSRS Doc Lib 13 SSRS Doc Lib 14

 

 

You’ve now linked the uploaded report to the data source.  Clicking on the report name from the document library will cause the report to run.

 

SharePoint Web Part Error – The Specified Solution Was Not Found

If you develop, release and add a SharePoint 2010 sandboxed solution web part to a page, then change the web part type to non-sandboxed you may see the error: ” Web Part Error: The request could not be completed because the specified solution was not found”.

Just edit the page, delete the web part, then re-add the web part to the page.  This fixes the error.