- #WINDOWS 10 MICROSOFT OUTLOOK 2016 KEEPS STOPPING WINDOWS 10#
- #WINDOWS 10 MICROSOFT OUTLOOK 2016 KEEPS STOPPING SERIES#
The data field contains the error number.Īpplication pool SecurityTokenServiceApplicationPool has been disabled.
#WINDOWS 10 MICROSOFT OUTLOOK 2016 KEEPS STOPPING SERIES#
The process id was '24976'.Īpplication pool '96eb1b47a3694bbd99fd7d148ab4151d' is being automatically disabled due to a series of failures in the process(es) serving that application pool.Ī process serving application pool '96eb1b47a3694bbd99fd7d148ab4151d' suffered a fatal communication error with the Windows Process Activation Service.
This is probably more a Gmail settings question then an Outlook question but here goes. Outlook 2016 in Microsoft Office and 365.
#WINDOWS 10 MICROSOFT OUTLOOK 2016 KEEPS STOPPING WINDOWS 10#
I found the following error logs in event viewer:Ī process serving application pool '96eb1b47a3694bbd99fd7d148ab4151d' failed to respond to a ping. On that front, I have also tried the free app that comes with Windows 10 and get the same results as with Outlook. NET Framework SDK documentation and inspect the server trace logs. For more information about the error, either turn on IncludeExceptionDetailInFaults (either from ServiceBehaviorAttribute or from the configuration behavior) on the server in order to send the exception information back to the client, or turn on tracing as per the Microsoft. User Profile Application Proxy failed to retrieve partitions from User Profile Application: .UserProfileApplicationNotAvailableException: UserProfileApplicationNotAvailableException_Logging :: UserProfileApplicationProxy.ApplicationProperties ProfilePropert圜ache does not have d9eb0a1a-25ca-44b5-a553-d45f572e12dcĪt .UserProfileApplicationProxy.get_ApplicationProperties()Īt .UserProfileApplicationProxy.get_PartitionIDs()Īt .UserProfileApplicationProxy.IsAvailable(SPServiceContext serviceContextĪpplication error when access /dept/TO/DC/_vti_bin/client.svc, Error=The server was unable to process the request due to an internal error. The only thing which i found in uLS logs was:
0 kommentar(er)
