Micollab 7.3 & Windows 10

[RFB23]

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. 

[Magpye]

There were a number of issues with Windows 10 and Micollab 7.3 when the Windows 10 feature releases came out.

I think Mitel fixed most of them in the later releases, It may be worth getting the 7.3.0.402 client from Mitel and running this on a few test users to see if it improves it?

[CraigB]

We are running the MiCollab 7.3.0.402 client on Windows 10 1803/1903 and everything seems to work properly.  No reported issues.

[scott_87]

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.

We seem to be having the exact same issue with our 7.3 users also. Gone down the route of reinstalling .net, running DISM repair, ensuring both Windows Updates & Dell Updates are fully upto date but still seeing random crashes from a handful of users. Did you get any further with this issue? Did you report to Mitel?

Below is a snap shot of the error we see in event viewer - we are running MiCollab 7.3.0.402

Faulting application name: UCA.exe, version: 7.3.0.402, time stamp: 0x5bf3fdf0
Faulting module name: clr.dll, version: 4.8.3928.0, time stamp: 0x5d3900c0
Exception code: 0xc0000005
Fault offset: 0x001a094b
Faulting process ID: 0x287c
Faulting application start time: 0x01d56ae5bec84b0c
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: a1f26b1d-1960-4abf-80a8-8bbea1d02368
Faulting package full name:
Faulting package-relative application ID:

[Gambler]

I too am having issues with 7.3 and Win 10.

Users are on a Surface Pro running WIN 10 build 1903
Read where is is not supported but it crashes on other non-Surface Pro users also

All Users are using the softphone on the client in an ACD environment  that is integrated to the Ignite Application on PC.
Call would come in, ring the user, call handled, user hangs up, client crashes (unresponsive).

Tried installing 7.3.0.404 (Mitel sent) still  having issue.

Logs are show same information (referencing .NET)
Have made sure  .NET 3.5,4.0,4.5, are installed.

Any ideas?

[griam01]

Mitel is aware of the issue and working on a diagnostic patch which should be available soon (per support).  We were told to back down to .net 4.7 if possible.  We also found that changing from Minet to SIP softphone seemed to do the trick, but if you need ACD or Call recording, it isn't supported with SIP.

[scott_87]

Mitel is aware of the issue and working on a diagnostic patch which should be available soon (per support).  We were told to back down to .net 4.7 if possible.  We also found that changing from Minet to SIP softphone seemed to do the trick, but if you need ACD or Call recording, it isn't supported with SIP.

After thorough testing we also found .net 4.8 was the issue which was included in KB4486153.

Since rolling back this seems to have resolved our issues. We are still awaiting the official word from the Mitel Helpdesk. 

[PFIT]

Anyone have any update on this or know if Mitel has issued an update? Having several users with this issue. At first disabling .Net 4.8 like the member above mentioned fixed the issue but now they are experiencing crashes again. Same error message in Event viewer.

[Magpye]

Mitel have release a new version of the client (7.3.0.410) which solves this.
The Client and RPM file to upload to the server are available on the Mitel Software Downloads webiste.