--- Sjoerd Hooft's InFormation Technology ---

User Tools

Site Tools


Recently Changed Pages:

View All Pages

View All Tags


WIKI Disclaimer: As with most other things on the Internet, the content on this wiki is not supported. It was contributed by me and is published “as is”. It has worked for me, and might work for you.
Also note that any view or statement expressed anywhere on this site are strictly mine and not the opinions or views of my employer.

Pages with comments

View All Comments


Notes, Tips & Tricks: GroupWise

This is a notes page, extended with tips & tricks. This page is not really documentation, just stuff for me to remember. Sometimes things will get removed from these pages and turned into real documentation, sometimes not. You might find these notes to come in hand, maybe not. For me, it's just things I don't want to forget.

GroupWise on OES Tips And Tricks

ConsoleOne and GroupWise Snapins

  • First install ConsoleOne
    • Downloading the latest version from Novell Support
    • Install by extracting the archive and run the c1-install script
  • Then install the GroupWise administrative rpm
    • This one is located on the CD and in the SDD, under the directory admin
    • For GroupWise 7 SP3 HP1 this file is named novell-groupwise-admin-7.0.3-20080609.i386.rpm
    • Install by typing “rpm -i novell-groupwise-admin-7.0.3-20080609.i386.rpm”
  • If you receive this error: no gwadj2 in java.library.path follow the hints in this TID so solve this:
    • Open /usr/ConsoleOne/bin/ConsoleOne
    • Add this line:
      • “export C1_JRE_HOME=/usr/lib/jre/”
    • Modify this line:
      • D_LIBRARY_PATH=“/usr/lib:$LD_LIBRARY_PATH”
        • to
      • LD_LIBRARY_PATH=“/usr/lib:/usr/ConsoleOne/bin:$LD_LIBRARY_PATH”

And ConsoleOne will work.

Starting ConsoleOne Through CygWin

In case the GroupWise server starts in init 3, thirst issue the command “init 5”, and then start ConsoleOne with the command:


Of course you'll need a working CygWin - X op Windows environment for this.

Starting and stopping GroupWise agents

GWOES:/tmp/gw/admin # /etc/init.d/grpwise stop
Shutting down [gwpo.gwdom]                                      done

Shutting down [gwdom]                                           done

GWOES:/tmp/gw/admin # /etc/init.d/grpwise status
Checking status [gwpo.gwdom]                                    unused
Checking status [gwdom]                                         unused
GWOES:/tmp/gw/admin # /etc/init.d/grpwise start
Starting [gwpo.gwdom]                                           done
Starting [gwdom]                                                done
GWOES:/tmp/gw/admin # /etc/init.d/grpwise status
Checking status [gwpo.gwdom]                                    done
Checking status [gwdom]                                         done

In case groupwise agents won't start, you can also start them manually:

/opt/novell/groupwise/agents/bin/gwpoa @gwpoa.poa
/opt/novell/groupwise/agents/bin/gwmta @gwdom.mta

The config files are loaded from the default location (see below).

File locations

  • GroupWise Agents
    • /opt/novell/groupwise/agents/bin
  • GroupWise Agents config files
    • /opt/novell/groupwise/agents/share
  • Default location logfiles
    • /var/log/novell/groupwise/gwpo (name of the post office)

GroupWise Errors

C037 The database facility reported error [C037] on userxxx.db.
Memory error.
Retry the operation that caused the error. If it occurs again, restart GroupWise. If it occurs again, it might be necessary to run GroupWise in an environment with more available memory.
C042 The database facility reported error [C042] on userxxx.db.
Read consistent view of record not available.
Generally, the error is transitory and will go away when the operation is retried. Make sure that others are not doing updates to the database, and retry the action. If the problem persists, validate and rebuild the database as necessary.
C057 The database facility reported error [C057] on userxxx.db.
GroupWise Database Mainenance in progress.
Exit groupwise client, check for locks on the filesystem and or by the backup software and retry (or wait). If the error is persistent, check here for more solutions.
D023 User account is expired
D039 Attachment errors. When this error is reported by the POA it can almost always be ignored. Only when reported by an user proper actions should be taken. Most likely, the user has received a corrupted attachment.
E816 The database facility reported error [E816] on dmddxxxx.db.
Insufficient rights to perform operation
F00B The database facility reported error [F00B] on userxxx.db.
Unknown switch in search command
F007 The database facility reported error [F007] on userxxx.db.
End of command reached unexpectedly.
Transitory, probably a cancelled Quickfind command.

Logfile errors:

13 Databases with structural problems.................     1

Will list in the logfile like:

Problem 13- Structural problem found in database GWSERVER/GW:\path\to\userdb\userxxx.db
You could leave a comment if you were logged in.
groupwiseoes.txt · Last modified: 2021/09/23 22:24 (external edit)