Troubleshoot SharePoint 2016 Farm Trace Errors and Mobile Sign-In
Question details
The user needs help investigating repeated farm trace errors and mobile sign-in failures in an on-premises SharePoint deployment.

- Product
- SharePoint 2016 on-premises
- Device & OS
- not provided
- Scenario
- Users try to sign in to a SharePoint 2016 farm from mobile devices while the farm records trace errors.
- Observed behavior
- The farm repeatedly logs SPFeatureUseEntry trace errors, and mobile sign-in requests return 401 Unauthorized responses.
Record the time of a failed mobile sign-in, the site URL, and any correlation ID shown on the error page. Have a farm administrator review the logs and authentication settings, and remove passwords, tokens, and other sensitive information before sharing diagnostics.
Collect farm diagnostics and request SharePoint administration support
Use this approach to give a SharePoint specialist the information needed to investigate both the trace entries and mobile 401 responses.
An SPFeatureUseEntry trace and a 401 response do not by themselves establish a common cause. Compare their timestamps and correlation IDs before drawing conclusions.
Open the SharePoint site in the affected mobile browser and reproduce the sign-in attempt. Record the time, site URL, browser, error message, and any correlation ID; compare the result with a desktop browser if available.
In SharePoint Central Administration, open Monitoring > Configure diagnostic logging and check the trace log location. Collect relevant ULS entries around the failure time, including SPFeatureUseEntry entries and any matching correlation ID.
In Central Administration, review the web application's authentication providers under Application Management > Manage web applications, and review alternate access mappings under System Settings > Configure alternate access mappings. Record the claims configuration and farm topology without changing settings solely on the basis of the 401 response.
Post a question on Microsoft Q&A with the SharePoint tag. Include the sanitized ULS excerpts, authentication and claims configuration, alternate access mappings, mobile browser behavior, farm topology, and the time and correlation ID of the failure.

Work with Office documents using WPS Office
WPS Office is a free, lightweight alternative for working with Office documents in a familiar interface. Its Microsoft Office format support makes it easy to move existing files into WPS. It does not repair SharePoint farm authentication or trace errors.

Frequently Asked Questions
Does an SPFeatureUseEntry trace error cause the mobile 401 response?
Not necessarily. Check the ULS entries around the failed sign-in time and compare any correlation IDs before treating the two events as related.
Where can I find the SharePoint ULS log location?
In Central Administration, open Monitoring > Configure diagnostic logging and check the trace log location. Collect entries from the relevant time window.
What authentication details should I provide to support?
In Central Administration, review the affected web application's authentication providers under Application Management > Manage web applications. Include the provider and claims configuration, along with alternate access mappings, without sharing credentials or tokens.
Where should I ask for help with an on-premises SharePoint 2016 farm?
Post the sanitized diagnostic details on Microsoft Q&A using the SharePoint tag, and specify that the deployment is SharePoint 2016 on-premises.




