MiCollab Client Service failed and JBOSS process is not running

[ulforv]

Hi, I have a system with the error messagen "MiCollab Client Service failed and JBOSS process is not running" showing up in the licensing information.
system is a MiVoice Business Express 7.2.2.14. I have tried to reset the app record id but no difference.

system is running in VMWare and have been working before.

Greatful for any tip.

Regards UO

 

[kwbMitel]

Check the Status

Is the system in sync with the AMC?

If not, has it been more than 186 days since last sync?

**********************************************
What's most important is that you realise ... There is no spoon.

 

[ulforv]

Hi,

yes system is in sync with AMC, i do think it is some license issue but, system up and running so this is a trouble that came up today. Last sync is tonight (swedish) time.

//UO

 

[kwbMitel]

Backup and reboot?

**********************************************
What's most important is that you realise ... There is no spoon.

 

[Billz66]

Have you tried to restart just the micollab blade ?
select micollab client service from Left hand menu , then change action to stop and perform the action , then once its stopped repeat with the action set to start

obviously if its already stopped then just try and start it.

If it was working before ( and licensed properly) then its probably not AMC related

if you haven't try that first , if that doesn't work then restart the lot ( after backup )like kwb suggested


If I never did anything I'd never done before , I'd never do anything.....

 

[ulforv]

Hi.

The MiCollab blade says Active, when i try to stop the service it dont work and when I try to start the server say that it is already running. strange. Yes it has been up and running so this happened after a reboot and then it did not come up again. I also dont think it is a licens issue longer.
I have also tried to install a new ova on the vmware host and restore from a backup but same problem.

I will put a ticket to the Teck support at Mitel. Thanks for your help.

Regards UO

 

[Jemson]

Had this before and from memory the solution was (as unlikely as it sounds) to stop the MiCollab Client Service, stop the MBG service, restart MiCollab wait until it is completely up and users can login, then restart the MBG service. I believe it was a known issue in MiCollab 6.x - 7.0 that sprang up in some cases.

 

[ulforv]

I have tested the tip above. but that did not help. I have sent this to Mitel and also test on a nother vmware host but same problem.

Regards UO

 

[tlpeter]

Did the server name change?


BAZINGA!

I'm not insane, my mother had me tested!

 

[ulforv]

Hmm.. What server name do you have in mind?

the latest instans i restored from another running system. so it should be the same.

//UO

 

[tlpeter]

The full server name including domain on the right top of the webinterface.
I haf had an issue where i installed a certificate and the FQDN for that was differen than the server FQDN (name and domain)
After fixing that it worked again.
So perhaps you have the same issue now.

BAZINGA!

I'm not insane, my mother had me tested!

 

[jpruder]

Is this server in a supported role?