![]() In other instances of profile creation, we would receive the warning “You must restart Outlook for these changes to take effect”. Upon further investigation of the event logs, we would see OLMAPI32.DLL was the faulting module. Errors such as, “Windows Shell Common DLL has stopped working”Ĭlicking “Close Program” would then be followed by an error reporting that “System resources are critically low”.Ĭlicking O K would then prompt Outlook to close. Other Outlook clients continued to operate without incident.įor some Outlook clients, we would receive errors when creating a brand new profile in Outlook. ![]() When we cut over our DNS to the new VIP some of our Outlook clients started to receive the errors below. We upgraded the Kemp to the latest firmware and created a new Exchange 2016 VIP using the latest templates from Kemp. ![]() The customer had an existing Kemp Load Balancer they had been using for Exchange 2010. I encountered this recently while upgrading a customer from Exchange 2010 to Exchange 2016. Disabling TLS 1.0 may cause Outlook to crash for some of your clients.
0 Comments
Leave a Reply. |