GroupWise 8 Resolving Common Issues

From MicroFocusInternationalWiki
Jump to: navigation, search

GroupWise 8 Best Practices

GroupWise 8 Troubleshooting

GroupWise 8 Resolving Common Issues


Hopefully this will be a great support resource as admins, users, and engineers contribute. System, administration, and client issues are listed here as long as they have solutions.

ConsoleOne issues beyond XP

The Problem:

Installing or copying the ConsoleOne files to a Windows Vista, Windows 2008, or Windows 7 system does not result in a usable instance of ConsoleOne. ConsoleOne messages reference to dll, environment, or legacy client issues.

The Solution:

ConsoleOne is only supported on these platforms for the purpose of GroupWise administration. There are several workarounds to resolve some of the issues experienced with ConsoleOne on these platforms.

See the following TIDs for help:

Installing and Running ConsoleOne on Windows Vista TID7003389

Installing ConsoleOne on Windows 7 TID7005545

Various Issues With GroupWise Snapins on Windows 2008 Server TID7005070

ConsoleOne on a remote Linux box

How do I run ConsoleOne on my Linux box if I have a Windows Workstation?

You need two applications, Putty and Xming -

Putty is a Windows SSH client. PuTTY is a free implementation of Telnet and SSH for Windows and Unix platforms, along with an xterm terminal emulator. It is written and maintained primarily by Simon Tatham. The PuTTY executables and source code are distributed under the MIT licence, which is similar in effect to the BSD licence. The web site URL is /

Xming is a Windows X-Windows server... The X Window System (commonly X or X11) is a computer software system and network protocol that provides a graphical user interface (GUI) for networked computers. It creates a hardware abstraction layer where software is written to use a generalized set of commands, allowing for device independence and reuse of programs on any computer that implements X. Xming comes in 2 flavours, the Public Domain Version released under a GPL license and the more advanced Website Edition, available for a donation.

Using X11 forwarding in SSH

The SSH protocol has the ability to securely forward X Window System applications over your encrypted SSH connection, so that you can run an application on the SSH server machine and have it put its windows up on your local machine without sending any X network traffic in the clear.

In order to use this feature, you will need an X display server for your Windows machine, such as Xming, Cygwin/X, X-Win32, or Exceed. This will probably install itself as display number 0 on your local machine; if it doesn't, the manual for the X server should tell you what it does do.

You should then tick the `Enable X11 forwarding' box in the Tunnels panel (see section 4.22) before starting your SSH session. The `X display location' box is blank by default, which means that PuTTY will try to use a sensible default such as `:0', which is the usual display location where your X server will be installed. If that needs changing, then change it.

Remember that the Xming needs to be running for you to launch X-Windows applications and if you see errors about run level 5 then this is the most likely cause of the failure.

To start ConsoleOne, open putty (with X11 enabled and Xming running) login, and then launch ConsoleOne form the command line.

/usr/ConsoleOne/bin/ConsoleOne &

Note the & at the end of the line which disconnects the X-Windows session from the console allowing you type other items without breaking the ConsoleOne.


FID Editing

The Problem:

Need to create a GroupWise user with a specific File ID (FID) for accessing an archive, or restoring a deleted user?

The Solution:

In TID3510373 it explains how to do this by using an import file and the necessary tools.

However there is another way, by using ConsoleOne, you can just edit the FID as well.

Please Note that this only works if the userXXX.db file has not yet been created – in other words it must be done imeadeatly the user is created.

  • Open the account in ConsoleOne, then click on the button left below 'Page options'.
  • Click in the 'Tabs of Pages' on 'GroupWise' and then 'Disable'.
  • Save the setting with OK/OK.

This disables the GroupWise Tab and moves the GroupWise information to the Other Tab.

Now you have to close the account (Cancel or X) and reopen it. Go to the Other Tab, and voila, the GroupWise attributes are listed as 'Leftover attributes that are not handled by custom pages'.

So to create a use with a secific FID we use the following routine:

  • With the GroupWise Snapins enabled, create a new GW User and exit.
  • Re-open the new user
  • Disable the snapins and close
  • Open the user (now with no GroupWise Snapins)
  • Open the Other page and change the FID
  • Save, close, Open renable the snapins and close once again.
  • If you now look at the GroupWise properties of the user you seen the new FID

When you now log into the GroupWise mailbox it will create the UserXXX.db file using the FID you created.

While the normal FID is 3 characters long, by using the routine above it is possible to create FIDs with 1 or 2 characters, anyone for user1.db? Happy FID-editing :-)

There are other tools to edit FID's, such as:

FID editor Archive FID editor – TID10014261

FIDIt (and CleanIT, MergeIT and CheckIT) by Email Essentials Inc. supplied by Messaging Architects.

For restoring deleted users there is the chapter of Tay Kratzer's GW65 administrator's guide free for download.

Slow POA Check List

One CoolSolutions user (Thomas Erickson) has posted an interesting Wiki entry on how to diagnose slow POA performance.

[Slow POA Checklist]

Trapping bad messages passing through the GWIA

Thomas Erickson also started a page on GWIA message troubleshooting, here is a revised version of that original.

To enable Trapping on NetWare or Windows

  1. ConsoleOne | select gateways | gwia | server directories | advanced | smtp service queues
  2. Enter new directory, for example: \\GW1\GWData\grpwise\domain\wpgate\GWIA\third
  3. Restart the gwia
  4. All incoming and outgoing will need to be manually moved to the correct queues/directories ( from \\GW1\GWData\grpwise\domain\wpgate\GWIA\third\RECEIVE for incoming and to \\GW1\GWData\grpwise\domain\wpgate\GWIA\third\SEND for outgoing).
  5. Thus one can trap incoming or outgoing messages, in simple SMTP format.

It is also possible to use the Linux method below.

Enable Trapping on Linux on Linux

This can be done in ConsoleOne or via editing the gwia.cfg file. In this example we will only indicate the editing option, however it is probably easier to use ConsoleOne

  1. Less /opt/novell/groupwise/agents/share/gwia.cfg and near the bottom of the file (below the --home entry) you may see a rt 4. This indicates 4 receive threads. Changing this value to 0 there will be no receive threads and thus the GWIA will NOT process messages to the other queues. If there is no rt 4 entry, create the rt 0.
    1. From within Less press v (this enabled vi from within a less shell)
    2. Add the insert to allow additional text and at the bottom of the file type rt 0
    3. Esc. :wq and you return to Less This is useful to ensure that the change you thought you made in vi was you did change.
  2. /etc/init.d/grpwise status
    1. Isolate the exact syntax of the gwia - This is case sensitive for example: GWIA.DomainQ
  3. /etc/init.d/grpwise stop GWIA.DomainQ
  4. /etc/init.d/grpwise stop GWIA.DomainQ
  5. Resend a message inbound (Note that it will NOT pass through your system) and examine the issue (see below)
  6. re-enabling the incoming mail
    1. Less /opt/novell/groupwise/agents/share/gwia.cfg | v | change (or delete) rt 0 to rt 4 | :wq
  7. /etc/init.d/grpwise stop GWIA.DomainQ
  8. /etc/init.d/grpwise stop GWIA.DomainQ
    1. The queues will clear down automatically
  9. Send another incoming message to verify that all is now working again.

Examination of the Trapped Messages

(Thomas Erickson original)

Now that you have the "bad message" you can feed it to your lab system without impacting the production system.

Open the bad message with a text editor and change the TO fields to match your test system.

Mine was (lets dream something up).
So, I replaced the customers TO to mine. Then I put this in my gwia receive directory. Guess what, it failed. So, I applied all the latest beta code and it still failed. See my wiki on applying GW patches on Linux .

Then, I made a copy of the bad message and started removing lines and seeing if it would process (watching POA logs or login).

Without too much trouble, I found the two lines that were causing some problems.

I used "Beyond Compare" to view the original bad message and my copied by message and moved lines over and back and forth until I came up with the right broken lines.

You will see the RED part of the message that was causing the problem. We then contacted the sender and asked them if it was easy/difficult to remove this on outgoing. It was easy for them to remove it and then the customer began to receive email from this problem domain!!

GroupWise 8.01 client crashes using address book or replies

The Problem:

When users open the address book, reply to a message, or use an application that invokes the default mail client GroupWise will crash.

The GroupWise client was upgraded to version 8.01x from version 7.0.x using setup.exe or using the client auto-update service.

The Solution:

It was determined that the Windows Messaging address book configuration was at fault. The reason is not clear as a fresh installation of the client does not produce the same address book service footprint.

New client installations result in the following address books being registered with Windows Messaging:

Novell GroupWise
Novell LDAP Address Book
Novell Personal Address Book

Upgraded client installations result in address books being registered with Windows Messaging similar to the following:

Novell GroupWise
Novell GroupWise Address Book
Novell LDAP Address Book
Novell Personal Address Book

The list may be similar to the above or slightly different. The GroupWise address book listings may vary or be missing entirely.

Removing the Novell GroupWise, Novell GroupWise Address Book, and re-adding the Novell GroupWise entry back to the address books registered with Windows Messaging resolved the crash issues.

Old signatures return from the dead

The Problem:

User has a legacy signature that keeps re-emerging after it has been removed or over written. When it re-asserts itself it may or may not be visible within the client for management. Not that it matters because it still comes back if deleted or over written.

The Solution:

The legacy signature can be viewed and deleted using the WebAccess client. Deleting the signature this way seems to resolve the issue.

Linux agents that won't load or open links


  • GroupWise Monitor reflects that a paticular GroupWise agent will not go to a good state from an unknown or bad state
  • The agent will not load on a paticular server or node
  • The agent loads successfully but will not open it's links to domains or gateways

Explanation: The most likely cause for all of these symptoms could be the same issue. Especially if your agents run in daemon mode. The likely culprit is the network stack for the agent has been left open by a crashed or restarted agent. Its not supposed to happen but it does and it is disliked.

To check for this condition put on your Linux admin gloves and prepare to look for the process at fault.


Look for three things depending on your server IP stack configuration.

  • Is the IP address used by the agent still bound or responding on cluster node?
    • Determine and resolve this using the "ip" command
ip addr

If so note the ethernet device it's bound to and remove it from remove node(s) using the ip command as well

ip addr del dev eth0 xx.xx.xx.xx/xx

(IP address and subnet mask reference. and

  • Is the Message Transfer or the agent HTTP managment port for the agent still active?
    • Use the "netstat command to determine if the HTTP management or MTP ports are still active for the agent on the target server.
netstat -ant | grep xxxx

( Use the list of standard ports from the table below. If you aren't using the standard ports replace these values with yours)

Agent Standard HTTP and MTP ports
POA 7181, 7101.
MTA 7180, 7100
GWIA 9850, 7102
WebAccess 7211, 7105

Alternatively you could evaluate the system for erroneous agent instances by using the agent type using the ps command.

ps -eaf | grep gwx

Where gwx is either gwpoa, gwmta, gwia, or gwinter

If any of the erroneous agents are loaded or their ports are active note the process ID (PID) of the first listed agent (this will be the parent PID) and terminate them using the kill command.

kill <PID>

If the target agent process(es) do not unload you may need to force it using a special signal passed to the kill command.

kill -9 <PID>

Once all instances of the erroneous agent are unloaded you should be able to load the target agent(s) successfully and it should participate in the system normally.