GroupWise Custom Dictionary (Speller) loses saved additions after upgrading to GroupWise 2012

  • 7010336
  • 28-Jun-2012
  • 11-Jun-2013

Environment

Novell GroupWise 8
Novell GroupWise 2012

Situation

After upgrading client workstations from GroupWise 8 to GroupWise 2012, custom additions made to the GroupWise Speller or Custom Dictionary are lost.
Words added to the Dictionary in GroupWise 8 don't get updated after upgrading to GroupWise 2012.

Resolution

Fixes were placed into GroupWise 2012 Sp1 to help improve the importing and conversion of the speller file.

Workaround:
It should be noted that the XX portion of the WT61XX.UWL, is the language version of the speller being used.

To force a re-import:
  1. Close the client
  2. WT61XX.UWL Must be in:
    • Windows7 - C:\Users\USERNAME\AppData\Local\Novell\GroupWise
    • WindowsXP - C:\Documents and Settings\YOURUSER\Local Settings\Application Data\Novell\GroupWise
  3. Delete the *.GQC and *.GWD from:
    • Windows7 - C:\Documents and Settings\YOURUSER\Application Data\Novell\GroupWise
    • WindowsXP - C:\Users\USERNAME\AppData\Roaming\Novell\GroupWise
  4. If the WT61XX.UWL is named WT61XX.UWL-back, then rename it without the "-back".
  5. Restart GW and open the speller.

If WT61XX.UWL was renamed to WT61XX.UWL-back after restarting and opening the speller, that means that the import was completed.

Additional Information

When the speller is first initialized in GW2012 it will search for it's own word list on C:\Users\USERNAME\AppData\Roaming\Novell\GroupWise, there's two files named: XX_YY.GWD and XX_YY.GQC.  Where XX_YY is the speller language and dialect. GWD is the Word List and GQC is the Quick Correct files.  Both files are text files and you can open and edit them with notepad. If those files are not present (that will be the case when you are running GW2012 the first time), it'll try to look for the GW8 World List, that's in C:\Users\USERNAME\AppData\Local\Novell\GroupWise, a file named: WT61XX.UWL

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