The CurrentUserName monitor is constructed on a thread with disposed identity

 1.  Rescheduled the timer job: User Profile Service Application - Feed Cache Repopulation Job  from 5 minutes to daily.

https://sites.google.com/site/milenadyle/home/sharepoint-troubleshooting/cache

  2.  Run SharePoint Management Shell:

Type: stop-spserviceinstance | where { $_.typename -eq “user profile synchronization service” }

The User Profile Synchronization service status should now be ‘Stopped’ or ‘Disabled’.

  3.  Check the Certificates store on the server that runs the User Profile Synchronisation Service and delete all the ForefrontIdentityManager certificates.

Start -> Run -> mmc

File -> Add / Remove Snap-in

Select Certificates -> Computer Account -> Finish -> Local Computer -> Finish -> OK

Expand Certificates -> Personal -> Certificates

Delete all ForefrontIdentityManager certificates (if you have tried to provision the UPS unsuccessfully several times, you will see more than one certificate).

Expand Certificates -> Trusted Root Certification Authorities -> Certificates

Delete all ForefrontIdentityManager certificates (if you have tried to provision the UPS unsuccessfully several times, you will see more than one certificate).

  4.  Set the FIM Services to run as Local System:

Start -> Run -> services.msc

Locate the two FIM Services: Forefront Identity Manager Service, Forefront Identity Manager Synchronization Service.

Edit properties and set it to run as Local System account.

  5.  Check Central Administration for the ProfileSynchronizationSetupJob and delete any running jobs.

Go to Central Administration -> Monitoring

Delete the job.

  6.  Provision the User Profile Service using Central Administration.

转载：https://social.technet.microsoft.com/Forums/en-US/a58c4e6f-200f-408b-aba8-68a67e5ee444/usage-infrastructure-error-usage-entry-dropped-due-to-exception

The CurrentUserName monitor is constructed on a thread with disposed identity

原文：https://www.cnblogs.com/snailJuan/p/12455230.html