using a non-US charset in Postgres, causes a challenge when upgrading to GMS18

  • 7022483
  • 20-Dec-2017
  • 20-Dec-2017

Environment

GroupWise Mobility Service 18

Situation

If anyone who does not use a US character set on their Postgres then before running:
/opt/novell/datasync/tools/pgUpdate.sh
edit it and change the reference to en_US.UTF-8 to your locale, in this case en_GB.UTF-8
 
Do the same edit for /opt/novell/datasync/tools/pgUpdate94to96.sh" if you are going to run that for a SLES12SP3 upgrade.
 
It has been found that the actual GMS18 upgrade failed saying that "GroupWise Maintenance was not stored. This may cause problems. Please consult the readme."
When this happened it was found that the  "systemctl start gms" worked fine and one could could log in but got an unattractive and uninformative admin error page.
 
The issue seems to be that /opt/novell/datasync/update.sh did not read and store the GroupWise 18 license information correctly
 
Running:
python /opt/novell/datasync/syncengine/connectors/mobility/cli/validateGroupWiseAdmin.pyc -sl "GW Admin IP Address" "9710" "GW Admin Login" "GW Admin Password"
Then running
python /opt/novell/datasync/syncengine/connectors/mobility/cli/validateGroupWiseAdmin.pyc -ca "GW Admin IP Address" "9710" "GW Admin Login" "GW Admin Password"
fixed this for several customers.

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