We are currently in the progress of migrating our SharePoint 2016 on-premise site to 365 and everything has been working fine, nothing has been touch by any administrators. However, out of the blue yesterday morning at 6:10am the User Profile Server started erroring.
A summary of the errors it is throwing are:
The Execute method of job definition Microsoft.Office.Server.UserProfiles.LMTRepopulationJob (ID 9fd04747-aa54-4616-9946-bd6f352a8095) threw an exception. More information is included below.
Access is denied.. (Correlation=e6b0ef9f-f052-500e-6758-022d1aa4e7c1)
The Execute method of job definition Microsoft.Office.Server.UserProfiles.FeedCacheRepopulationJob (ID f99c8464-363f-483f-b238-c7038616c620) threw an exception. More information is included below.
Access is denied.. (Correlation=efb0ef9f-10e9-500e-6758-0d73f71237f8)
The Execute method of job definition Microsoft.Office.Server.ActivityFeed.ActivityFeedUPAJob (ID ec9a7806-f483-4091-ac56-1f8c6e11944a) threw an exception. More information is included below.
The trust relationship between the primary domain and the trusted domain failed.
. (Correlation=2fb1ef9f-b087-500e-6758-0a262e71128a)
A failure was reported when trying to invoke a service application: EndpointFailure
Process Name: OWSTIMER
Process ID: 8528
AppDomain Name: DefaultDomain
AppDomain ID: 1
Service Application Uri: urn:schemas-microsoft-com:sharepoint:service:d9c6f65ff2184a85ba31abc24ef3dad6#authority=urn:uuid:f5195237866d468498fa1c2a0ef3b64e&authority=https://<appserver>:32844/Topology/topology.svc
Active Endpoints: 1
Failed Endpoints:1
Affected Endpoint: http://<appserver>:32843/d9c6f65ff2184a85ba31abc24ef3dad6/ProfileService.svc
Failure trying to synch web application 317629d1-6202-4268-b669-eacf6f38861f, ContentDB 8ab206bd-ebb8-4f96-9ebf-4b147cc7a4e9 Exception message was Microsoft.Office.Server.UserProfiles.UserProfileApplicationNotAvailableException: UserProfileApplicationNotAvailableException_Logging :: UserProfileApplicationProxy.ApplicationProperties ProfilePropertyCache does not have 74b5460c-e894-4537-acc3-2b7ebc36efe1
at Microsoft.Office.Server.Administration.UserProfileApplicationProxy.GetApplicationPropertiesFromCache()
at Microsoft.Office.Server.UserProfiles.UserProfileGlobal.GetDataUsingCurrentHttpContextAsCacheT
at Microsoft.Office.Server.Administration.UserProfileApplicationProxy.get_ApplicationProperties()
at Microsoft.Office.Server.Administration.UserProfileApplicationProxy.get_PerfmonInstanceHandle()
at Microsoft.Office.Server.UserProfiles.ContentDBSynchronizer..ctor(ELogType logType, SPContentDatabase cdb, SPJobState jobState, SyncType syncType, WSSSyncUsageEntry usage, String[] excludedAccountsRegexStrings)
at Microsoft.Office.Server.UserProfiles.WSSProfileSyncJob.Execute()
Failure during sweep synch of content database WSS_Content. Exception was UserProfileApplicationNotAvailableException_Logging :: UserProfileApplicationProxy.ApplicationProperties ProfilePropertyCache does not have 74b5460c-e894-4537-acc3-2b7ebc36efe1.
Central Admin and system pages on sites are still loading and some non-custom forms are still working but most pages are displaying the error:
Sorry, something went wrong
An unexpected error has occurred.
TECHNICAL DETAILS
GO BACK TO SITE
Also, when go onto the User Profile Service Application and click Manage a Correlation ID error is given.
I have been trying to make some lighter changes to the site as I am reluctant to follow many posts on the web to resolve the issue as they mention previous upgrades or work that has been going on within the system before these problems occurred, but we have touched anything for a while.
In the logs, the correlation id seems to point towards the same issues such as:
- Exception thrown while adding control 'ASP.SocialDataUserControl': System.NullReferenceException: Object reference not set to an instance of an object.
- Exception thrown while adding control 'Microsoft.SharePoint.Portal.WebControls.SocialNotificationControl'
- ProfilePropertyCache could not be refreshed for UPA Proxy
For the trust issues we have disconnected both APP and WFE server from the domain and readded but this did not change anything.