MiCollab Client service stuck on 'Starting'

[jw00lgar]

Hi All,

We're running

MiVoice Business Express 7.1.0.55
Mitel Standard Linux 10.4.13
OVA 7.1.0.55

the MiCollab Client Service is currently stuck on 'starting'. I can stop the service successfully however it gets stuck when starting it up again. I've rebooted the virtual machine also, no change.

Any advise?

Thanks
James

[martyn]

Have you run the client integration wizard? If not, then that is one of the reasons that the service will fail to initialise.

[jw00lgar]

Hi Martyn,

I did try the Client Integration Wizard as my first port of call, however it throws up an error;

MiCollab Client Service is not Ready: MiCollab Client Service Installed = true MiCollab Client Service Licensed = true MiCollab Client Service Active = false JBoss Started = false

We're investigating a possible routing issue with port 63008 between the inside and outside interfaces, i'll reply back with the outcome

Thanks

[Tonnievt]

Hi All,

I am having the same issue running version 7.2

I previously had it working with only one interface with a NAT translation from outside to inside. However the micollab client deployment didn't like this config.
But when i connect the WAN interface the micollab gets stuck.

Someone any luck with this?
Kind regards,

Tonnie

[Mattmayn]

Stop the MBG service and the MiCollab Client service, start the MiCollab Client service and once that starts , then start the MBG service. See if that fixes it.

[martyn]

Did you end up figuring this one out? I've just fired up a new express and hitting the same issue now as well.

[martyn]

Ok, well just figured it out by the looks of it.

If it couldn't resolve DNS for the MiCollab correctly then it bombed out, but didn't tell you that on the ICW or in the logs. All the DNS records had been configured, but initially I pointed the system to 8.8.8.8 during the intial text based setup so that it would licence (as at that stage the server didn't have a route to the DNS Server), and then in the ICW I set the DNS to the internal addres, but it ignored that and continued to use 8.8.8.8.
Logging in to the server manager, setting the DNS server to the internal one (along with the route to that network), and then re-running the ICW seems to have got it past the issue.