SharePoint Experts, Information Architects, Expert Witness

SICG provides a broad array of business and technology consulting from architecture to design to deployment of global systems with a focus on surfacing data in the enterprise. We focus on the "How", not just the possible. Contact me direct: or call 704-873-8846 x704.

Search This Blog

Monday, November 26, 2012

WSS Usage Application Proxy SharePoint 2013 Install

As was true with SharePoint 2010, SharePoint 2013 still has an issue with the WSS Usage Application. When a new farm has been installed and the Usage Application started, the Usage Application Proxy is not correctly enabled by default – this is a bug that must be corrected using PowerShell:

1) Login to the server running Central Administration, click Start > Microsoft SharePoint 2010 Products > SharePoint 2010 Management Shell. In the PowerShell, type in:

2) This will return a list of the current service applications – you are looking for the WSS_UsageApplication for example:

DisplayName          TypeName             Id
-----------          --------             --
State Service App... State Service Proxy  e51696f1-3523-4e20-9b75-578485024b37
Managed Metadata ... Managed Metadata ... 830bafcf-f0d3-4254-91e4-8cfe11840e27
Search Service Ap... Search Service Ap... a988d821-8247-4294-ba11-961b22e51f8b
Application Disco... Application Disco... af617d69-7332-49f3-a61c-0eef3f7470cf
Excel Services Ap... Excel Services Ap... b6c5b951-7b4d-4837-83f3-c916c1ef6c7d
WSS_UsageApplication Usage and Health ... 83301455-c854-4596-af5c-0bc6ee963b6d

3) Copy the Id of the WSS_UsageApplication (Mark and copy), then enter the following commands:
$WUAP = Get-SPServiceApplicationProxy | where {$_.ID -eq "<copied Id>"}

4) Close the PowerShell and double check the status in Central Administration > Application Management > Manage Service Applications - the Proxy should now be started.

1 comment:

Anonymous said...

Great help. Thanks a lot! :)