GroupWise Error Codes

Now that you have some observation tools in your scientific-method toolbox, you need to know what the error codes mean. Most problems reported by GroupWise components are accompanied by some kind of a four-character error code, such as 8201 or C05D. These codes map to certain kinds of problems. Rather than memorizing the individual mappings, however, it is useful to learn the families, or classes, of error codes.

82xx Errors

The 82xx class of errors indicates some sort of file access or file I/O problem. Perhaps the POA is trying to access a database at a given path, but the database is not there (8209, path not found). A possibility is that file-system rights have not been granted to a message transfer agent (MTA) that is attempting to poll a remote post office (8201, access denied).

89xx Errors

You will generally see 89xx errors in conjunction with TCP/IP communication problems. For example, if a POA goes down, the GroupWise client will report an 8908 error. If the MTA times out on a communication with a POA, it might report an 8912 or an 8913 error. The 89xx error suite also includes many errors outside of the realm of TCP/IP communications, but the non-TCP/IP errors do not crop up as often.

Cxxx Errors

The Cxxx errors typically point to database structural integrity problems. For example, a user receives C022 errors when creating any item in GroupWise. The error means that database integrity has been compromised. The C04F error indicates that the database checksum did not add up correctly. In either case, you know from the error class that a GroupWise store file has structural damage.

There are two Cxxx-class errors that are a little bit different: C05D and C067. Both of these errors indicate structural damage to the information/message store, rather than just to one store file. This means that one or more store files are not correctly registered in the GroupWise guardian database. C05D indicates a registered store file that could not be found. C067 indicates that a store file could not be created, because an unregistered version exists on disk.

Dxxx Errors

The Dxxx class of errors points to database content problems. The problem might be a missing record, which will return a D107 error. A missing user record (when the POA tries to deliver to a user who does not exist in the address book) might flag a D101 error. The problem might not be that a record is missing, though. It might simply be that the data does not match what the GroupWise component was expecting to see, such as when the entered password does not match the one required (D109, access denied).

Exxx Errors

The Exxx class of errors changes the rules a bit. Instead of mapping to a database problem or an I/O problem, E-class error messages indicate that the problem was found while using a document-management feature. The error state might actually indicate a normal situation, such as when a user tries to access a document that he or she has not been given rights to (E51B). It might also indicate a content problem with the document-management databases. A missing document record will return an E811 error.

Using the Error Classes

If you know what each error class means, you will still be missing an important piece of the puzzle. Most GroupWise errors tell you what kind of a problem was encountered but do not tell you which component had the problem. For instance, if the GroupWise client is encountering structural problems working with the GroupWise archive, it will probably report a C022 or C04F error. Those are the same errors the POA would use to report problems with a message database in the post office directory. The same error can be reported by two different components, and it can be caused by a problem in any of several areas.

The only way you can know which component has the problem is to apply some of the architectural information available in the rest of the book. Here are some questions you can ask yourself that might help:

• Which component reports the error? For instance, if the POA reports a C022, you will see the error in the log. Check the log for any other information about the problem. Generally, the POA will report which database it's having a problem with.

• Which components do not report the error? Suppose the client reports an error, but the POA does not. This narrows the problem quite a bit. The databases that a client has exclusive access to that the POA does not have access to are the archive databases and the caching mode and remote databases.

• Which pieces are touched by the component(s) that report(s) the error? If you know, for instance, that the client reports an error, but the POA does not, you need to determine which pieces the client touches that the POA does not. In client/server access mode, the problem likely is the GroupWise archive. In direct access mode, the problem might be the master mailbox or the archive.

The Complete List of GroupWise Error Messages

As of this writing, Novell has not published a complete list of the error codes used by all GroupWise components. Fortunately, the more common errors have been well documented, and appear online at Novell's support connection Web site.

The Novell Support Connection

When you see an error message, you can look it up in the knowledgebase at http://support.novell.com. The odds are good that you are not the first person to see this message. This method is helpful for looking up messages one at a time, as you encounter them.

The Novell Online GroupWise Documentation

You can access the GroupWise online documentation to get a comprehensive list of most of the error codes in GroupWise. This site can be very helpful in identifying the various error messages' meanings. It is found at http://www.novell.com/documentation under the Troubleshooting Guides section.

GroupWise Magazine

The GroupWise magazine is a great tool for administrators and users alike. We also write for this magazine. To access this magazine, go to one of the following locations:

www.gwmag.com www.novell.com/coolsolutions/gwmag/

Use the Support Connection

Although the troubleshooting advice in this chapter is sound, here's the best advice of all: Don't troubleshoot if you don't have to!

Novell has a world-class support site. Use the knowledgebase at http://support.novell.com before you begin racking your brain. In most cases, the exact set of conditions you are seeing has already been documented by Novell Technical Services, and one or more ready-made solutions await you. Why reinvent the wheel?