Mobility Service error: Cannot connect to GroupWise administration to veify license.

  • 7023501
  • 06-Nov-2018
  • 21-Feb-2020

Environment

GroupWise 18
GroupWise Mobility Service 18

Situation

You have moved your existing GroupWise system on a new server and existing GMS complains about it and that there are few days till administration gets locked.
You install new GMS or upgrade existing ones and during the installation & configuration part you get this error and cannot finish properly the installation process.

During the upgrade process this error displays when verifying the GroupWise server and credentials of the Primary domain:

Successfully validated GroupWise Server and credentials.

Problem validating GroupWise server and credentials. Exception: HTTPSConnectionPool(host='hostname.domain.com', port=9710): Max retries exceeded with url: /gwadmin-service/domains?domainType=primary (Caused by SSLError(SSLError("bad handshake: Error([('SSL routines', 'tls_process_server_certificate', 'certificate verify failed')],)",),))

Failed to validate GW Admin

Please check the entries and try again

Resolution

A root cause of this problem is that during installation of GroupWise on original server, the system certificates were created using a host name of the server which now does not match new server. Or you have some mismatch in the GroupWise system certificates.
Follow steps bellow to recover from such situation:

1. Stop GMS service and go into /var/lib/datasync/mobility directory -> delete from there gwadmin_ca.pem file.

2. On a GW server running your primary, stop gwadminservice.

3. Go into /opt/Novell/GroupWise/certificates. There will be a system GUID directory -> rename it into old or delete it.

4. From a terminal, generate new system directory by:

gwadminutil ca -d /<path to primary> -g -f

5. Start gwadminservice again.

6. Start gwadminconsole and connect to the primary domain -> MTA object -> SSL Settings tab, here delete and regenerate system certificates if you were using self-signed system ones before.

7. On a GMS server mount the GMS ISO image again that you were using for the installation of GMS recently and re-run the install again. That shall go over without any complains now.

Since you regenerated new system CA certificates and MTA SSL settings, you will need to download tgise new CA files on any remote GW server and regenerate certificate for agents that run on it. Check the procedure in the TID 7024374.

Feedback service temporarily unavailable. For content questions or problems, please contact Support.