Question

I'm receiving this error on our SharePoint server in event viewer.

When I check the Configure usage and health data collection I see WSS_Logging_fd8d31dd9b964a649407b44127593673 as the database name. When I check the database the DB is listed as WSS_Logging with no GUID attached to it.

If I try to Enable usage data collection, or make any changes at all, I receive the error:

A Usage Application already exists in this farm

The service app does exist in the Manage Service Applications page.

I'm thinking this may have become corrupt. Is there any downsides or repercussions to recreating this service?

Was it helpful?

Solution

Run powershell Get-SPServiceApplication and check if you have multiple Usage Service Applications.

Then I would suggest deleting that and recreating a new one.

OTHER TIPS

Please check the account running the SharePoint tracing service, add it into the "Performance Log Users" group, and give it read/write permissions on the 15/Logs folder , then restart the SharePoint tracing serice.

Did you try to change the database used by your Usage service application ?

Set-SPUsageApplication -DatabaseServer <DatabaseServerName> -DatabaseName <DatabaseName>

You can try this as a farm's administrator and SPShellAdmin :

Set-SPUsageApplication -DatabaseServer <DatabaseServerName> -DatabaseName WSS_Logging
Licensed under: CC-BY-SA with attribution
Not affiliated with sharepoint.stackexchange
scroll top