SharePoint Experts, Information Architects, Expert Witness

We provide consulting in a broad array of business and technology from architecture to design to deployment of global systems with a focus on surfacing data in the enterprise. Specialists in Microsoft, we are a premier provider of SharePoint Expertise (including 2016 and Office 365). We also provide Expert Witness/Legal Expert in eDiscovery, source discovery, patent infringement, piracy and more! We also have established SICG DLDS s.a. - our counterpart in Costa Rica that specializes in water systems ( - Contact me direct: or call 704-873-8846 x704.

Search This Blog

Wednesday, March 23, 2011

SharePoint Usage and Health Data Collection Proxy stopped

If you've been working with SharePoint 2010 and have had some troubles with the Usage Proxy Service not running, it turns out it is a common problem. Like many, I'd searched high and low for the answer and finally came across the 'right' answer from Jeremy (no last name) in the SharePoint Commander blog.

You can determine if you have this problem by opening the Service Applications (Central Administration > Application Management > Manage Service Applications) - under the Web Analytics service, you see the Usage and Health Data Collection Proxy as 'Stopped'. Apparently another 'bug' in 2010, this is because the service is not completely provisioned when created. To fix the best method is via the SharePoint PowerShell.

Open the PowerShell then enter (italised):

PS C:\users\SPFarmAcct > Get-SPServiceApplicationProxy

This will return a list of all of the Service Proxies inlcuding the Display Name, Type Name and Id (a GUID value) - locate the Usage and Health proxy in the list and copy the Id next to it (usually the last item).

Return to the PowerShell and enter:

PS C:\users\SPFarmAcct > $UsageProxy = Get-SPServiceApplicationProxy | where {$_.ID -eq "ID you copied"}
PS C:\users\SPFarmAcct > $UsageProxy.Provision()

When you return to the Service Applications page, refresh it and the proxy should be running!

1 comment:

Anonymous said...

I had the same problem in SP 2013, and this fixes it there too. Thanks.