E
Eddga
Guest
Greetings fellow Microsoft users,
I'm an ITI administrator in a medium sized company (about ~500 clients) and we're facing a problem that we seem not to be able to solve. Our servers are running Windows Server 2008R2 (6.1/7601) and Exchange 2010 (14.03.0361.001). About 1.5 years ago we exclusively were running Windows 7 x64 (6.1/7601) and Outlook 2010 x86 (as part of Office Professional Plus 2010) on our clients. In this configuration the Room Finder was/is working fine. Also we noticed that, when upgrading to Outlook 2016 x86 (part of Office Professional Plus 2016) from 2010 pre-installed (no matter if on Windows 10 or 7) the Room Finder still was working.
Now since about a year we were moving more and more clients to Windows 10 x64 (most run buildversion 1709, some still 1607) and installed Office Professional Plus 2016 x64 first. On that we noticed that the Room Finder wasn't working on a single client and switched all clients to Office x86 (currently on 16.0.4639.1000). That was when it became really weird. At first it seemed working on most clients (on some it still didn't in the first place), but after days or weeks, which was varying from client to client, the Room Finder again suddenly stopped working / appearing in Outlook. Meanwhile there are still clients running Windows 7 and Office 2010 where the Room Finder is still working.
We now could track it down to the Microsoft Exchange Add-In ( UmOutlookAddin.dll ), which was listed under "Inactive Application Add-ins" and obviously is the basis for the Room Finder to work. Activating that Add-in worked and did the trick for a while on some clients but suddenly also wasn't working anymore.
Trying to run the Microsoft Exchange Add-in in the COM Add-ins throws an Error "Load Behaviour: Not loaded. A runtime error occured during the loading of the COM Add-in."
I then tried editing/setting several registry keys:
Windows Registry Editor Version 5.00
[HKEY_CURRENT_USER\Software\Policies\Microsoft\Office\16.0\Outlook\Resiliency\AddinList]
"UmOutlookAddin.FormRegionAddin"=dword:00000001
[HKEY_CURRENT_USER\SOFTWARE\Microsoft\Office\Outlook\Addins\UmOutlookAddin.FormRegionAddin]
"LoadBehavior"=dword:00000003
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Office\Outlook\Addins\UmOutlookAddin.FormRegionAddin]
"LoadBehavior"=dword:00000003
[-HKEY_CURRENT_USER\SOFTWARE\Microsoft\Office\16.0\Outlook\Resiliency\DisabledItems]
[HKEY_CURRENT_USER\SOFTWARE\Microsoft\Office\16.0\Outlook\Resiliency\DisabledItems]
[-HKEY_CURRENT_USER\SOFTWARE\Microsoft\Office\16.0\Outlook\Resiliency\CrashingAddinList]
[HKEY_CURRENT_USER\SOFTWARE\Microsoft\Office\16.0\Outlook\Resiliency\CrashingAddinList]
[HKEY_CURRENT_USER\SOFTWARE\Microsoft\Office\16.0\Outlook\Resiliency\DoNotDisableAddinList]
"UmOutlookAddin.FormRegionAddin"=dword:00000001
which at least led to the Add-in being forced to start with Outlook but it still throws the same error. Which besides I'm not able to find anything about in the event log. I read in a forum that an old version of the UmOutlookAddin.dll could make it work but couldn't find any place to download any version of the file from. Also Outlook always changes the LoadBehaviour back to "2" on start.
Running Outlook as an administrator and enabling the Exchange Add-in didn't work either (same error).
I also read about a solution with Microsoft hotfixes but it only applied for Office 2013 and Office 2010 and I couldn't find any similar hotfixes for Office 2016.
We're out of ideas now and asking the wise Microsoft-TechNet-Community for some guidance. Any idea is welcome.
Thanks in advance for your help.
Best regards,
Eddga
Continue reading...
I'm an ITI administrator in a medium sized company (about ~500 clients) and we're facing a problem that we seem not to be able to solve. Our servers are running Windows Server 2008R2 (6.1/7601) and Exchange 2010 (14.03.0361.001). About 1.5 years ago we exclusively were running Windows 7 x64 (6.1/7601) and Outlook 2010 x86 (as part of Office Professional Plus 2010) on our clients. In this configuration the Room Finder was/is working fine. Also we noticed that, when upgrading to Outlook 2016 x86 (part of Office Professional Plus 2016) from 2010 pre-installed (no matter if on Windows 10 or 7) the Room Finder still was working.
Now since about a year we were moving more and more clients to Windows 10 x64 (most run buildversion 1709, some still 1607) and installed Office Professional Plus 2016 x64 first. On that we noticed that the Room Finder wasn't working on a single client and switched all clients to Office x86 (currently on 16.0.4639.1000). That was when it became really weird. At first it seemed working on most clients (on some it still didn't in the first place), but after days or weeks, which was varying from client to client, the Room Finder again suddenly stopped working / appearing in Outlook. Meanwhile there are still clients running Windows 7 and Office 2010 where the Room Finder is still working.
We now could track it down to the Microsoft Exchange Add-In ( UmOutlookAddin.dll ), which was listed under "Inactive Application Add-ins" and obviously is the basis for the Room Finder to work. Activating that Add-in worked and did the trick for a while on some clients but suddenly also wasn't working anymore.
Trying to run the Microsoft Exchange Add-in in the COM Add-ins throws an Error "Load Behaviour: Not loaded. A runtime error occured during the loading of the COM Add-in."
I then tried editing/setting several registry keys:
Windows Registry Editor Version 5.00
[HKEY_CURRENT_USER\Software\Policies\Microsoft\Office\16.0\Outlook\Resiliency\AddinList]
"UmOutlookAddin.FormRegionAddin"=dword:00000001
[HKEY_CURRENT_USER\SOFTWARE\Microsoft\Office\Outlook\Addins\UmOutlookAddin.FormRegionAddin]
"LoadBehavior"=dword:00000003
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Office\Outlook\Addins\UmOutlookAddin.FormRegionAddin]
"LoadBehavior"=dword:00000003
[-HKEY_CURRENT_USER\SOFTWARE\Microsoft\Office\16.0\Outlook\Resiliency\DisabledItems]
[HKEY_CURRENT_USER\SOFTWARE\Microsoft\Office\16.0\Outlook\Resiliency\DisabledItems]
[-HKEY_CURRENT_USER\SOFTWARE\Microsoft\Office\16.0\Outlook\Resiliency\CrashingAddinList]
[HKEY_CURRENT_USER\SOFTWARE\Microsoft\Office\16.0\Outlook\Resiliency\CrashingAddinList]
[HKEY_CURRENT_USER\SOFTWARE\Microsoft\Office\16.0\Outlook\Resiliency\DoNotDisableAddinList]
"UmOutlookAddin.FormRegionAddin"=dword:00000001
which at least led to the Add-in being forced to start with Outlook but it still throws the same error. Which besides I'm not able to find anything about in the event log. I read in a forum that an old version of the UmOutlookAddin.dll could make it work but couldn't find any place to download any version of the file from. Also Outlook always changes the LoadBehaviour back to "2" on start.
Running Outlook as an administrator and enabling the Exchange Add-in didn't work either (same error).
I also read about a solution with Microsoft hotfixes but it only applied for Office 2013 and Office 2010 and I couldn't find any similar hotfixes for Office 2016.
We're out of ideas now and asking the wise Microsoft-TechNet-Community for some guidance. Any idea is welcome.
Thanks in advance for your help.
Best regards,
Eddga
Continue reading...