MiCollab 7.3 stuck at idle and wont start after domain name change

[Saltrock23]

MiCollab 7.3 stuck at idle and wont start after domain name change

Also when i try to run diagnostics it comes back with
"Well, That shouldn't happen"

[dilkie]

changing domain names, or the host name even, after everything is configures is generally a bad idea. Lots of internal things rely on it and may not always adjust correctly to a change.

install a fresh copy with the correct configuration from the start.

[acejavelin]

MiCollab 7.3 stuck at idle and wont start after domain name change

Also when i try to run diagnostics it comes back with
"Well, That shouldn't happen"

Just one service like MiCollab Client, or the entire MiCollab server won't boot up?

We had a similar issue where a sudden shutdown corrupted a configuration file relating to hostnames and had to re-run the configuration wizard from putty, but it never took and AWC would never start. Tech support had to go in and find the value missing in the configuration file and regenerate it from key values or something. Took several hours on the phone...

Basically I am saying run the configuration again from the command line, then reboot... if it still fails contact support. If you are out of SWA, it's a tough call, all depends how large or complex the system, might be worth it to re-enroll and give it a shot, or use use dilkie's approach and reinstall, your call.

Just an FYI... 7.3.0.X prior to .204 had a some weird bugs, we had to upgrade a couple times at one site for all sorts of issues but .204 has been pretty stable now. Not saying to upgrade while the system is not functioning properly (that might break it more). Just thought I would throw that out there...

[theblarney]

Had a similar issue and it turned out to be DNS, I think I set the DNS servers to be ones used on internal network but set to resolve locally.

I wouldn't normally do this but seemed to work on this occasion.