PSP Kick

All about the tech

Fixing user profiles with events

This article discusses the Microsoft-Windows-AppReadiness event error ID 215 that occurs after the ideal user first signs in.

Applies to: https://userlogica.com 10 – all editions, Windows Server 2012 R2
Original KB Number: 2916750

Symptoms

When a local user logs on to a computer running Windows 8 or 1 Windows Server 2012 R2, a “Microsoft-Windows-AppReadiness Journey ID 215” error message appears.

For example, the following event log is collected when the computer is running Windows Server 2012 R2:

Log name: Microsoft-Windows-AppReadiness/Admin
Source: Microsoft-Windows-AppReadiness
Date: Date
Event ID: 215
Task category: (1)
Step: error
Tags: (2)
User: SYSTEM
Computers: Computers
Description:
ART: Failed to allow store categories for admin. Error: “Class not registered” (0.015623 seconds)

The Watch event is logged if the computer is running Windows 8.1:

Log name: Microsoft-Windows-AppReadiness/Admin
Source: Microsoft-Windows-AppReadiness
Date: Identifier: Date
Event 215
Task category: (1)
Step: error
Tags: (2)
User: SYSTEM
Computers: Computers
Description:
ART: Failed to resolve store categories for Local_Users. Error: “Social network location not available. See Windows Help for network troubleshooting tips.” (0,second)

Reason

Issue 2968801 occurs because most AppReadiness services query the Microsoft Store for category names typically associated with Microsoft Store apps installed on a computer when the affected user logs in during peak hours.

>

The AppReadiness service generates group logs when the category name protection task fails. The local personal account does not have any Microsoft account associated with the Microsoft Store sign-in for the requested data. Therefore, when a local user logs in, the problem described in the “Symptoms” section occurs.

Resolution

  • 2 minutes to finally read
  • The category name is used whenever you sortBrowse apps by category in the All Apps view on this home screen. The Viral Marketing All view opens when you click the down arrow button at the bottom of the home screen.

    Applies to Windows: Server 2022, Windows 10, Windows 8, Windows 8.1, Windows Server 2019, Windows Server Windows 2016, Server 2012 R2, Windows Server 2012. Topic

    Explains how to use event logs and fire log traces to troubleshoot problems loading and unloading user credit scores. The following sections describe how to attempt to review the three event logs that record user profile information.

    Step 1: Check For Events In The Application Log

    The very first step in troubleshooting restarting and unloading a user profile (including the user profile) is to use the event viewer to examine any warnings, not to mention errors and events that the service user profile writes to the application log .

    To view user profile events in the application log:

    1. Launch the Event Viewer. To do this, open Control Panel, select System and Security, then select View Event Logs under Administrative Tools. The event viewer window will open.
    2. In the console tree, select Windows Logs, then Applications.
    3. In the Actions panel, select Filter Current Log. The Filter Current Log dialog box opens.
    4. In the Event Sources section, select the User Profile Service check box and click OK.
    5. Check the event log, paying particular attention to errors.
    6. If you find noticeable episodes, select the event log online help link for more information and troubleshooting instructions.
    7. For further troubleshooting, make a note of the date and time of the noticeable events, and then review the activity log (as described in step 2) to see details of what our User Profile service was doing during the error and warning periodth.

    Step 2: View The User Profile Service Activity Log

    If using only the Application log does not resolve the issue, use most of the following methods to view User Profile Service events in the operational report. This log shows some of the key operations in the service and can also help you identify where the problem typically occurs during the profile loading or unloading process.

    Windows Application Log and User Profile Service Work Log are enabled in all Windows installations by default.

    To view the work log of all User Profile Services:

    1. In the viewer’s console tree, navigate to Applications, then Service Logs, then Microsoft, if necessary Windows, then User Profile Service, and finally Operations.
    2. Review the events that occurred at the time the errors or warnings you flagged in the application log occurred.

    Step 3: Be Sure To Check Your Analytics And Debug Logs

    If you need more information than the log containsAside from operations, you can save analytics and debug logs on the affected computer. This level of logging is likely to be much more verbose and should be turned off unless you’re trying to troubleshoot a problem.

    1. In the Viewer Actions panel, select View, then select View Analytics and Debug Logs.
    2. Go to Applications and Services Logs, then Microsoft, then Windows, then User Profile Service, then Diagnostics.
    3. Select Enable Logging and then Yes. This will save the diagnostic log.
    4. If you need more information, see Step 4: Create and decode a trace for more information about creating a log.
    5. When you’re done troubleshooting a specific issue, go to the Diagnostics Viewer, select Disable Logging, select View, then uncheck Show Parsing and Debug Logs to hide parsing and logging from debugging.< /li>

    Step 4: Create And Decode The Trace

    If you can’t resolve the issue entirely with events, create a trace log (.etl file) when you reproduce the issue, and also decode it using public values ​​from the Microsoft symbol server. The trace logs provide very specific information about what the User Profile Service literally does and can help identify the error that occurred.

    The best strategy when doing ETL tracing is to start with as little log as possible. After decrypting the log, check the specific log for errors.

    To create and decode a trace for the new user profile in use:

    1. Connect to the computer where the user is having problems using an account that can be a member of the local Administrators group.

    2. The elevated command prompt ends with the following commands, where is actually the path to the local file you created earlier, such as C:\logs:

      logman create trace -bs 768 -nb 16 16 -n RUP -to \RUP.etl -ets
      update logman -p rupeb7428f5-ab1f-4322-a4cc-1f1a9b2c5e98 0x7FFFFFFFF 0x7 -ets
      update logman -p rup 9891e0a7-f966-547f-eb21-d98616bf72ee 0xFFFFFFFF 0xFF -ets
      update logman -v rup 9959adbd-b5ac-5758-3ffa-ee0da5b8fe4b 0xFFFFFFFF 0xFF -ets
      Logman updates -p rup 7f1bd045-965d-4f47-b3a7-acdbcfb11ca6 0xFFFFFFFF 0xFF -ets
      Logman new boot -p rup 40654520-7460-5c90-3c10-e8b6c8b430c1 0xFFFFFFFF 0xFF -ets
      update logman -p rup d5ee9312-a511-4c0e-8b35-b6d980f6ba25 0xFFFFFFFF 0xFF -ets
      update logman -p rup 04a241e7-cea7-466d-95a1-87dcf755f1b0 0xFFFFFFFF 0xFF -ets
      update logman -p rup 9aed307f-a41d-40e7-9539-b8d2742578f6 0xFFFFFFFF 0xFF -ets
      
    3. On the home screen, select the username and/or select Edit Account, being careful not to log out of the owner. If you are using Remote Desktop, log out of your admin session to establish a user session.

    4. Reproduce the issue. The procedure for reproducing an issue is usually to log in as the current user experiencing the problem, log out as the most important user, or both.

    5. After reproducing each of our problems, log back in as the primary administrator.

    6. From an elevated command, run the following command in a timely manner to saveWrite log to ETL file:

      logman stop -n RUP -ets