Posts Tagged ‘SharePoint’

ULS Log Viewer v2 for SharePoint 2013

September 18, 2014

Microsoft has released an updated version of the ULS Log Viewer application for SharePoint 2013. Get it here:


Fixing SharePoint 2013: Sideloading of apps is not enabled on this site

December 7, 2013

I am using Visual Studio 2012 to develop SharePoint Apps for my on-premise SharePoint 2013 environment. I wanted to set up a simple dev environment for one of my host-header site collections, but when I tried to deploy my SharePoint App I got the error:

Sideloading of apps is not enabled on this site

The feature required to enable sideloading is as follows:

DisplayName: EnableAppSideLoading

Id: ae3a1339-61f5-4f8f-81a7-abd2da956a7d

CompatibilityLevel: 15

To enable sideloading, use the following PowerShell commands:

$site = Get-SPSite ""

$sideLoadingId = new-object System.Guid "ae3a1339-61f5-4f8f-81a7-abd2da956a7d"


Using the Synchronization Service in SharePoint 2010 – Forefront Identity Manager 2010

June 25, 2012

If you use the User Profile Synchronization Service in SharePoint 2010, you may not realise that you are also getting an identity management product included – Forefront Identity Manager 2010 (or FIM 2010). FIM 2010 is a full-featured identity management system, and included with SharePoint 2010 is the basic version that does not have a lot of the “extras” (like Certificate Management, the FIM portal, etc) but is used to import and export data between identity systems. Typically this is SharePoint 2010 User Profiles and Active Directory (other systems are also supported).

To view the FIM 2010 interface you can open the Synchronization Service Manager, which is by default located at:

C:\Program Files\Microsoft Office Servers\14.0\Synchronization Service\UIShell\miisclient.exe

Note that this is only installed when you configure the User profile Sychronization Service on SharePoint 2010, so if you have a multi-server deployment you need to be on the server that has the User Profile Synchronization Service running.

I’ve implemented a full FIM 2010 deployment previously so was quite interested to note that it is indeed the same product, with some reduced functionality. This has been helpful a couple of times when the synchronization has failed from SharePoint 2010 and I have needed to troubleshoot the issue by opening the Sync Service Manager.

Synchronization Service for SharePoint 2010

Synchronization Service Manager for SharePoint 2010

I was getting the following error in the Application event log after a Full Sync was being performed:

Event ID 6298 (Timer)
The Execute method of job definition Microsoft.Office.Server.UserProfiles.UserProfileImportJob (ID 719df063-5757-4542-8ed1-a2c1622f6603) threw an exception. More information is included below.
Generic failure

I also noted that the FIM Sync Service was stopping on the server, but the SharePoint 2010 Central Admin reported the service still running. 10-20 minutes later, the FIM Sync Service would start again.  I opened up the Sync Service Manager and checked the Management Agent Operations under the “Operations” tab. This tells you which Management Agents (responsible for synchronising data between systems) had been run recently and the result. My sync runs had not started at all.

I decided to run a full sync on all Management Agents in the following order:

1. On the Active Directory Domain Services management agent, I ran the profiles: DS_FULLIMPORT and DS_FULLSYNC

2. On the Extensible Connectivity type management agent (which is the customised SharePoint management agent), I ran the profiles: DS_FULLIMPORT, DS_FULLSYNC, DS_EXPORT, DS_DELTAIMPORT

(for FIM-people, this is the export and confirming import required to ensure data is full synchronised)

The imports completed successfully and further “normal” syncs via the SharePoint interface worked too.

FIM Sync Results

FIM Synchronization Results

It is possible to adjust the synchronization settings via the Sync Service Manager, but I wouldn’t recommend it – there is no documentation about the connection between SharePoint and the FIM Sync Engine, so it is possible you could break the interface by making changes.

HOWTO Stop or Cancel a Running Timer Job in SharePoint 2010

May 17, 2012

I had an issue with several of my FAST for SharePoint 2010 timer jobs not processing properly, they were in the “Running” stage but never actually finished. The jobs were:

Crawl Log Report for Search Application FASTConnectorSSA (Web server 1)

Crawl Log Cleanup for Search Application FASTConnectorSSA (Web server 1)

Crawl Log Cleanup for Search Application FASTQuerySSA (Web server 2)

Crawl Log Report for Search Application FASTQuerySSA (Web server 2)

These timer jobs process log files from the FAST Search servers and display them on the Search Farm pages for content source details, crawl history, etc.

To cancel running services you must restart the SharePoint Timer service on all servers that the jobs are running on. In my example above, I had to restart the timer service on “Web server 1” and “Web server 2” to get rid of their jobs. Central admin jobs list then showed they had disappeared.

If there is an issue with the Job itself (i.e. it is a custom job not behaving) then you should Disable the job definition first, then restart the SharePoint Timer servers. That will make sure the job doesn’t start running again according to its schedule.

SharePoint Search Server 2008 Shared Services Provider Limitation

February 16, 2010

Search Server 2008 Standard Edition and Search Server 2008 Express Edition are only allowed one Shared Services Provider. If you want more, you need to upgrade to MOSS 2007 or SharePoint 2010. This is because both editions are limited to one server.

Having problems with an SSP on Search Server Express 2008 and thought I’d just create a new one, but no, it can’t be that simple can it… 🙂

WCF Talking to SharePoint Web Services

November 12, 2008

This had nailed me for about 3 days – how to get a Windows Communication Foundation-based call to a SharePoint 2007 Web Service.  Thankfully, there is a solution:

In particular, I was using:

<security mode=TransportCredentialOnly>
<transport clientCredentialType=Ntlm/>

in my app.config, which I think was the issue.  Replacing that with:

<security mode=TransportCredentialOnly>
<transport clientCredentialType=Ntlm proxyCredentialType=Ntlm realm=“”/>
<message clientCredentialType=UserName algorithmSuite=Default/>

and the code change as specified in the blog post fixed everything!  Once again, I am a victim of not knowing enough about WCF security configuration *sigh*  Annoyingly, some web service calls worked, and some didn’t, which made it more difficult to spot the issue.  These worked:

  • SiteData (GetSiteAndWeb)
  • Lists (GetList)

but this one (my important one!) didn’t:

  • Lists (GetListItems)

After I made the config change, all worked perfectly.


UPDATE: Two more items to add to this post, the first in particular because I kept on getting exceptions all wrapped up in a FaultException:

“Exception of type ‘Microsoft.SharePoint.SoapServer.SoapServerException’ was thrown.” 

This was particularly annoying because I couldn’t work out any way to get the underlying exception information.

  1. Adding this line fixed my FaultException problem :
    sharepointServiceClient.ClientCredentials.Windows.AllowedImpersonationLevel = System.Security.Principal.TokenImpersonationLevel.Impersonation;
  2. Make sure you set the Endpoint address to the site you want to interrogate.  Usually this means adding a line similar to:
    listsClient.Endpoint.Address = new EndpointAddress(webInfo.SiteUrl + “/_vti_bin/lists.asmx”);
    otherwise you will probably just get FaultExceptions / SoapServerExceptions and not be able to work out why!