1
Introduction and Announcements / Re: How to find my posts / threads
« on: February 18, 2021, 05:42:17 PM »
Wow I must have looked at that page 5 times.
Thanks for the direction.
Thanks for the direction.
News:
Welcome to Mitel Forums. The Mitel resource - by techies, for techies...
Show Posts
This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.
Pages: [1]
2
Mitel Software Applications / Re: Micollab Usage
« on: February 18, 2021, 05:40:32 PM »
Good point, sunspark.
If staff are not even opening/logging in that could at least be a starting point but you are right not ideal.
Any thoughts or suggestions on a log that could better show activity?
If staff are not even opening/logging in that could at least be a starting point but you are right not ideal.
Any thoughts or suggestions on a log that could better show activity?
3
Introduction and Announcements / How to find my posts / threads
« on: February 18, 2021, 02:18:49 PM »
I have looked around in my profile, on the site, the help section, search online but can't seem to find out how to list my posts.
Eg on other forums I can filter to show my posts or other posts I have flagged for notify but here I have to manually find them?
What am I missing?
Eg on other forums I can filter to show my posts or other posts I have flagged for notify but here I have to manually find them?
What am I missing?
4
Mitel Software Applications / Re: Micollab Usage
« on: February 18, 2021, 01:52:12 PM »
I agree this would be very helpful.
I wonder if the View Logs area has a report in there, t hey only seem to go back one week but guessing that could be extended or exported to a syslog server. Just need to find the right report for MiCollab connections and there are tons of reports in there.
I wonder if the View Logs area has a report in there, t hey only seem to go back one week but guessing that could be extended or exported to a syslog server. Just need to find the right report for MiCollab connections and there are tons of reports in there.
5
Mitel Software Applications / Re: Micollab Client 9.1.3.2.0.2 Blank page loading after installation
« on: February 17, 2021, 04:09:05 PM »
thanks Sunspark for the update.
I am new to these forums, what is kms?
I am new to these forums, what is kms?
6
Mitel Software Applications / Re: Micollab Client 9.1.3.2.0.2 Blank page loading after installation
« on: February 17, 2021, 02:48:15 PM »
We just moved to new servers that host the virtual desktops with Nvidia T4 grid cards but on the old servers the virtual desktops didn't have any video cards.
Maybe I am not following your question?
Maybe I am not following your question?
7
Mitel Software Applications / Re: Micollab Client 9.1.3.2.0.2 Blank page loading after installation
« on: February 17, 2021, 02:00:26 PM »
Anyone have any updates on this issue?
8
Mitel Software Applications / Re: Micollab Client 9.1.3.2.0.2 Blank page loading after installation
« on: January 21, 2021, 05:50:42 PM »
Yes we are running Citrix XenDesktop (XD) v2012.0.0.28021 for most staff.
I am not sure this is a VDA issue and it's not limited to v2012 as my XD is running an older version of the VDA 2006.0.0.26.44. This seems more like a user profile issue.
For profile management, we currently are using MS FsLogix which removes the need for syncing, each staff gets the exact same as if there were on a physical computer. We haven't used Citrix profile management in 18+ months but some of the staff that were having the CRASH issue on launch were previously using Citrix profile management but not all the staff from then are affected.
What I have found out with a bunch of testing is, we narrowed down the area in %appdata% causing the app to crash on load.
C:\Users\[UserName]\AppData\Local\Microsoft\, if we delete this folder the MiCollab app will load correctly. We could probably narrow the exact folder down with more testing but I have spoken to a Mitel support person and provided them with a bunch of info on this as well.
I am not sure this is a VDA issue and it's not limited to v2012 as my XD is running an older version of the VDA 2006.0.0.26.44. This seems more like a user profile issue.
For profile management, we currently are using MS FsLogix which removes the need for syncing, each staff gets the exact same as if there were on a physical computer. We haven't used Citrix profile management in 18+ months but some of the staff that were having the CRASH issue on launch were previously using Citrix profile management but not all the staff from then are affected.
What I have found out with a bunch of testing is, we narrowed down the area in %appdata% causing the app to crash on load.
C:\Users\[UserName]\AppData\Local\Microsoft\, if we delete this folder the MiCollab app will load correctly. We could probably narrow the exact folder down with more testing but I have spoken to a Mitel support person and provided them with a bunch of info on this as well.
9
Mitel Software Applications / Re: automatic micollab invitation
« on: January 20, 2021, 05:52:16 PM »
There is also a setting to turn off all emails for the MiCollab login and TUI basic emails, if you were referring to that email. Under MiCollab Client Service--Welcome tab, enable/disable.
10
Mitel Software Applications / Re: automatic micollab invitation
« on: January 20, 2021, 05:48:38 PM »
If you are manually adding phones to existing users I think if you set the Deployment Profile: Do Not Deploy and uncheck the "Send Deployment Email" it will not send. Then you can manually deploy them manually later from the "Manage MiCollab Client Deployment".
11
Mitel Software Applications / Re: MiCollab 9.2.104 softphone says "Registration Failed"
« on: January 19, 2021, 01:32:08 PM »
Can also see this if their deployment has expired, try to redeploy them.
12
Mitel Software Applications / Re: Micollab Client 9.1.3.2.0.2 Blank page loading after installation
« on: January 19, 2021, 01:24:17 PM »
Win10 20h2
I have a similar issue, some users (not all 10-15%) the MiCollab app (same version as above) will open with a white screen and the systray app appears then the MiCollab app crashes and the systray icon disappears.
No change if user has local admin rights but if I delete their user profile it works fine for that user.
Also another user can open the app successfully on the same computer, even the same session with RunAs
---Event Viewer---
1st error
Application: MiCollab.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
2nd Error
Faulting application name: MiCollab.exe, version: 9.1.363.1, time stamp: 0x5eeb92d1
Faulting module name: KERNELBASE.dll, version: 10.0.19041.746, time stamp: 0x197b16c5
Exception code: 0xe0434352
Fault offset: 0x0012a842
Faulting process id: 0x2b90
Faulting application start time: 0x01d6ee8689dcde21
Faulting application path: C:\Program Files (x86)\Mitel\MiCollab\MiCollab.exe
Faulting module path: C:\Windows\System32\KERNELBASE.dll
Report Id: c0f56ecd-a930-417b-b31c-97a5e012c52a
Faulting package full name:
Faulting package-relative application ID:
---CEF-Debug-Log---
[0119/093631.858:ERROR:gpu_process_transport_factory.cc(990)] Lost UI shared context.
[0119/093633.509:ERROR:viz_main_impl.cc(184)] Exiting GPU process due to errors during initialization
---UcaLog0---
[62 2021-01-19 11:04:58.812] <D/BrowserWindow> IsForegrounded()
[63 2021-01-19 11:04:58.812] <D/BrowserWindow> IsForegrounded() res: True
[64 2021-01-19 11:04:59.421] <D/taskbar> flashing taskbar: shouldFlash: False, flags: 0, flashCount: 0, window handle: 133712
[65 2021-01-19 11:04:59.421] <E/Application> 1st chance exception (type=FileNotFoundException): sender(Name:MiCollab.exe
There are no context policies.
), exception=Retrieving the COM class factory for component with CLSID {E5B8E079-EE6D-4E33-A438-C87F2E959254} failed due to the following error: 8007007e The specified module could not be found. (Exception from HRESULT: 0x8007007E)., stack= at System.Device.Location.GeoCoordinateWatcherIntern al.CreateHandler(Object state)
[66 2021-01-19 11:04:59.421] <E/Application> AppDomain exception (type=FileNotFoundException): sender(Name:MiCollab.exe
There are no context policies.
), exception=Retrieving the COM class factory for component with CLSID {E5B8E079-EE6D-4E33-A438-C87F2E959254} failed due to the following error: 8007007e The specified module could not be found. (Exception from HRESULT: 0x8007007E)., stack= at System.Device.Location.GeoCoordinateWatcherIntern al.CreateHandler(Object state)
at System.Threading.QueueUserWorkItemCallback.WaitCa llback_Context(Object state)
at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
at System.Threading.QueueUserWorkItemCallback.System .Threading.IThreadPoolWorkItem.ExecuteWorkItem()
at System.Threading.ThreadPoolWorkQueue.Dispatch()
at System.Threading._ThreadPoolWaitCallback.PerformW aitCallback()
I have a similar issue, some users (not all 10-15%) the MiCollab app (same version as above) will open with a white screen and the systray app appears then the MiCollab app crashes and the systray icon disappears.
No change if user has local admin rights but if I delete their user profile it works fine for that user.
Also another user can open the app successfully on the same computer, even the same session with RunAs
---Event Viewer---
1st error
Application: MiCollab.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
2nd Error
Faulting application name: MiCollab.exe, version: 9.1.363.1, time stamp: 0x5eeb92d1
Faulting module name: KERNELBASE.dll, version: 10.0.19041.746, time stamp: 0x197b16c5
Exception code: 0xe0434352
Fault offset: 0x0012a842
Faulting process id: 0x2b90
Faulting application start time: 0x01d6ee8689dcde21
Faulting application path: C:\Program Files (x86)\Mitel\MiCollab\MiCollab.exe
Faulting module path: C:\Windows\System32\KERNELBASE.dll
Report Id: c0f56ecd-a930-417b-b31c-97a5e012c52a
Faulting package full name:
Faulting package-relative application ID:
---CEF-Debug-Log---
[0119/093631.858:ERROR:gpu_process_transport_factory.cc(990)] Lost UI shared context.
[0119/093633.509:ERROR:viz_main_impl.cc(184)] Exiting GPU process due to errors during initialization
---UcaLog0---
[62 2021-01-19 11:04:58.812] <D/BrowserWindow> IsForegrounded()
[63 2021-01-19 11:04:58.812] <D/BrowserWindow> IsForegrounded() res: True
[64 2021-01-19 11:04:59.421] <D/taskbar> flashing taskbar: shouldFlash: False, flags: 0, flashCount: 0, window handle: 133712
[65 2021-01-19 11:04:59.421] <E/Application> 1st chance exception (type=FileNotFoundException): sender(Name:MiCollab.exe
There are no context policies.
), exception=Retrieving the COM class factory for component with CLSID {E5B8E079-EE6D-4E33-A438-C87F2E959254} failed due to the following error: 8007007e The specified module could not be found. (Exception from HRESULT: 0x8007007E)., stack= at System.Device.Location.GeoCoordinateWatcherIntern al.CreateHandler(Object state)
[66 2021-01-19 11:04:59.421] <E/Application> AppDomain exception (type=FileNotFoundException): sender(Name:MiCollab.exe
There are no context policies.
), exception=Retrieving the COM class factory for component with CLSID {E5B8E079-EE6D-4E33-A438-C87F2E959254} failed due to the following error: 8007007e The specified module could not be found. (Exception from HRESULT: 0x8007007E)., stack= at System.Device.Location.GeoCoordinateWatcherIntern al.CreateHandler(Object state)
at System.Threading.QueueUserWorkItemCallback.WaitCa llback_Context(Object state)
at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
at System.Threading.QueueUserWorkItemCallback.System .Threading.IThreadPoolWorkItem.ExecuteWorkItem()
at System.Threading.ThreadPoolWorkQueue.Dispatch()
at System.Threading._ThreadPoolWaitCallback.PerformW aitCallback()
Pages: [1]