1
Mitel Software Applications / Micollab 7.3 & Windows 10
« on: September 03, 2019, 04:43:36 PM »
I have a few users experiencing issues with the Micollab 7.3, these users are running either 1809 or 1903 Windows 10 versions. When there is an incoming call the popup to answer the call just vanishes, they will still hear the call ringing with no way to answer it. The other issue, is where the call will just drop randomly and they will see a Micollab error popup named "Micollab Client Problem Reporting", see attached screenshot for that. I did some troubleshooting by checking logs and though I had nailed it down to .NET as the cause. I tried reinstalling .NET, Micollab, tried different user profiles, uninstalled some .NET updates, nothing seems to fix the issue. There is a Windows error log in Mitel folder that contained the following:
Analysis symbol:
Rechecking for solution: 0
Report Id: 817e3627-5f1c-41ad-92c7-fe4621770d16
Report Status: 268435456
Hashed bucket: 172435098f9a06a6fafbe72eef252d28
Cab Guid: 0
=== Application Error (8/29/2019 11:38:39 AM)
Faulting application name: UCA.exe, version: 7.3.0.104, time stamp: 0x58f49389
Faulting module name: clr.dll, version: 4.8.3815.0, time stamp: 0x5cdb7147
Exception code: 0xc0000005
Fault offset: 0x000e4401
Faulting process id: 0xa84
Faulting application start time: 0x01d55e87feefbf7e
Faulting application path: C:\Program Files (x86)\Mitel\Unified Communicator Advanced 7.3\UCA.exe
Faulting module path: C:\Windows\Microsoft.NET\Framework\v4.0.30319\clr.dll
Report Id: 817e3627-5f1c-41ad-92c7-fe4621770d16
Faulting package full name:
Faulting package-relative application ID:
=== .NET Runtime (8/29/2019 11:38:39 AM)
Application: UCA.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an internal error in the .NET Runtime at IP 6DBA4401 (6DAC0000) with exit code 80131506.
I did think I had it nailed down to .NET, but I tried all the available fixes to no avail. Has anyone experienced this with Micollab 7.3? Any help here is much appreciated.
Analysis symbol:
Rechecking for solution: 0
Report Id: 817e3627-5f1c-41ad-92c7-fe4621770d16
Report Status: 268435456
Hashed bucket: 172435098f9a06a6fafbe72eef252d28
Cab Guid: 0
=== Application Error (8/29/2019 11:38:39 AM)
Faulting application name: UCA.exe, version: 7.3.0.104, time stamp: 0x58f49389
Faulting module name: clr.dll, version: 4.8.3815.0, time stamp: 0x5cdb7147
Exception code: 0xc0000005
Fault offset: 0x000e4401
Faulting process id: 0xa84
Faulting application start time: 0x01d55e87feefbf7e
Faulting application path: C:\Program Files (x86)\Mitel\Unified Communicator Advanced 7.3\UCA.exe
Faulting module path: C:\Windows\Microsoft.NET\Framework\v4.0.30319\clr.dll
Report Id: 817e3627-5f1c-41ad-92c7-fe4621770d16
Faulting package full name:
Faulting package-relative application ID:
=== .NET Runtime (8/29/2019 11:38:39 AM)
Application: UCA.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an internal error in the .NET Runtime at IP 6DBA4401 (6DAC0000) with exit code 80131506.
I did think I had it nailed down to .NET, but I tried all the available fixes to no avail. Has anyone experienced this with Micollab 7.3? Any help here is much appreciated.