Micolab Client boot error

[dlessard]

Hi,

Since saturday we updated our MAS and some clients had experienced a problem when they try to open micolab client. On the uc.log we have :

mitel.communication.app - UC is running in a console session

and the application never finish to open.

Our actual setup version:

MiCollab Applications Services
ServiceLink   V10.1-34.0   installed   ServiceLink for Mitel Standard Linux   
SAS                   V6.0.122.0   installed   Suite Applications Services   

MiVoice Border Gateway
MiVoice Border Gateway   V8.1.23.0   installed   A secure gateway for VoIP traffic and associated Mitel applications   

MiCollab Client Service
MiCollab Client Service   V6.0.424.0   installed   MiCollab Client Service

and we run the client on Windows 8.1 and Windows 7

Someone can help me?

[dlessard]

Forgot it...

We need to never use : * on extension number and special character on password for the sip client and the MBG.

David

[irongladiator]

Hi dlessard,
We kind of have a similar incident where one users MiCollab client freezes upon startup, as well as when attempting to start manually, in short this user cannot even open the MiCollab Client. When we look in the logs we also find the "UC is running in a console session." What's weird here though is that when I have this user logon to the MiCollab Client on a different machine using their credentials, it opens up and is fine. So this is only happening on this users machine. We thought maybe a bad install, so we uninstalled and reinstalled the MiCollab Client with no luck. I should say that this user had no issues, this just suddenly stopped working.

Not sure if you're able to offer any insight or assist but any info would be appreciated.

Thanks,
-Iron

[VolatileTech]

@irongladiator

We had a similar issue with one user.  They could not successfully launch the MiCollab Client on one specific computer.  The splash screen would appear and then freeze.  The client never opened.  Turned out that it was actually the Microsoft .NET Framework that was causing the issue.

The user had Microsoft .NET Framework 4.5.3 installed on their system.  Uninstalling it and downgrading to Microsoft .NET framework v4.0, as listed in the UCA Quick Reference Guide, half fixed the problem.  After installing 4.0, the MiCollab Client would successfully open but it would not accept any login credentials.

We installed Microsoft .NET Framework 4.5.1 on the user's system instead and after that everything started working. 

Hope that helps!

LINKS:

Microsoft .NET Framework 4 (Web Installer)
http://www.microsoft.com/downloads/en/details.aspx?FamilyID=9cfb2d51-5ff4-4491-b0e5-b386f32c0992&displaylang=en

Microsoft .NET Framework 4.5.1 (Web Installer)
http://www.microsoft.com/en-gb/download/details.aspx?id=40773