Tag Archives: Central Administration

RSS Viewer Web Part Stops Working After Installing SharePoint 2010 SP2

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.


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);

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.



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.


Incorrect Permissions For Central Administration Following Initial SharePoint 2013 Installation

Following the installation of a SharePoint 2013 environment I had an issue where Farm Administration security settings hadn’t been correctly applied.  Even though my SharePoint setup user account was listed in the Farm Administrators group and was a local administrator, many options were missing from the Central Administration site.  Some of the missing options included manage services on server and I was unable to create new service applications.

In order to correct the permissions, I re-ran the SharePoint 2013 Products Configuration Wizard.  When running the wizard I left all the options as they were.  Once the wizard had completed the permissions had been set correctly and Central Administration displayed all the options correctly.

Extend SharePoint 2013 People Search Using Business Connectivity Services – Multi-Value User Properties

Following on from the four part series Extend SharePoint 2013 People Search Using Business Connectivity Services I had a requirement to update multi-value user properties using BCS.  If you haven’t read the posts in the series I highly recommend that you do as I’m only going to cover the changes I had to make in order to import multi-value properties.

For this example I’ve added a column to my SQL Server table called Speciality and updated the stored procedure to return the values in this column.


In the screen shot above I’ve added three specialties for myself, SharePoint, Hyper-V and SQL Server.  This has created multiple rows, an additional row for each specialty  each with the same email address.  The email address is important as this will be used by a filter within the external content type to return multiple values for each user.

Next, in SharePoint Designer open the external content type that references the stored procedure and click on Operations Design View in the ribbon.


In Data Source Explorer find the stored procedure under Routines, right click on it and choose New Read List Operation.


Click Next and on the Input Parameters screen click to add a Filter.  Create the filter, in my case on the email field and click Ok.  


On the Return Parameter screen click on Email, then tick Map to Identifier.  Finish the wizard and save changes to your external content type.


From Central Administration open your User Profile Synchronization Service and click on Configure Synchronization Connections.


Use the drop down to edit your external content type connection.  You can now choose a 1:many mapping, filter using the email filter against the WorkEmail user profile property.


To create a multi-value user open the User Profile Synchronization Service and click on Mange User Properties.


Click on New Property, select the property type as string (Multi Value) and choose the multi value separator you’d like to use.


Map the new property to the correct attribute from your BCS data connection and click Ok.


Run a full profile synchronization, then click on Manage User Profiles to search for a user and check the properties have been populated.



SharePoint People Picker – There was an error in the callback

When trying to configure the people picker to search a trusted domain I ran the command “STSADM.exe -o setproperty -pn peoplepicker-searchadforests -url http://servername&#8221; using the SharePoint 2010 Management Shell from the Central Administration server in our SharePoint farm.  I received the error:

“The Web application at http://servername could not be found.  Verfiy that you have typed the URL correctly.  If the URL should be serving existing content, the system administrator may need to add a new request URL mapping to the intended application.”

The error was strange because the web application URL I entered does exist.  I removed the URL parameter and ran the command again.  This time it ran without error.  To check the value I ran the command “STSADM.exe -o getproperty -pn peoplepicker-searchadforests”  This returned the value I expected.  However, when I tried to search for users from the remote domain nothing was returned.

I then connected to one of the Web Front End servers and ran “STSADM.exe -o getproperty -pn peoplepicker-searchadforests”.  Again, it returned the expected value.  I then ran the command with the URL parameter “STSADM.exe -o getproperty -pn peoplepicker-searchadforests -URL http://servername&#8221;  This didn’t return the expected value.

I realized that the initial command  “STSADM.exe -o setproperty -pn peoplepicker-searchadforests -url http://servername&#8221; needed to be run from the web front end server.  This time I didn’t receive the error about the web application not being found.

Unfortunately, this isn’t the end of the story as when I searched for a user I received the error “There was an error in the callback”.

People Picker


In order to fix this error I had to update the permissions on the registry key “HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Shared Tools\Web Server Extensions\14.0\Secure” on each Web Front End server.  The local groups need the following  permssions:

WSS_WPG – Read



Having changed the permissions I was able to search.