Fill out this form to subscribe to news, tips and information about updates.

Read more
Search known errors
From date:
To date:

Follow us
Facebook    Twitter    LinkedIn

G&R » Support » Known Errors  

Known Errors

These are the known errors in our products, logged as reported with versions and platforms affected as well as corrections and work-arounds.

This list is largely historical, since it records all problems that have been reported throughout G&R history. Only the most recently reported problems still exist, unless you are using a very old copy of the product, in which case you should update the product to the most recent version.

E0400: Gmailer stops sending and receiving mails

Product: Gmailer for Windows
Platform: All windows 16
Status: fixed for 5.0.2, patch available.
Last updated: 1998-04-05 20:13:02

Gmailer could stop sending and receiving messages in some cases when an
incoming call is received at exactly the same time as an outgoing call.
The loophole here is very small, but has been observed to happen
occasionally when a Gmailer is heavily loaded with very frequent
connections. If debugging is turned on, this can be seen by the multiple
SET_NODE_EVENT messages preceded by a "$$xxx: Set parameters OK."
messages. The SET_NODE_EVENT messages are the last messages in the

[1998/03/30 11:29:32] COMM_RECEIVE
[1998/03/30 11:29:32] $$TCP: Set parameters OK.
[1998/03/30 11:49:35] SET_NODE_EVENT Mailbox event received for PARIS
[1998/03/30 11:59:47] SET_NODE_EVENT Mailbox event received for ROME
[1998/03/30 12:10:30] SET_NODE_EVENT Mailbox event received for LONDON
[1998/03/30 12:30:44] SET_NODE_EVENT Mailbox event received for PARIS
[1998/03/30 15:01:08] SET_NODE_EVENT Mailbox event received for LONDON

A similar problem (generally the same symptoms, but without the  "$$xxx:
Set parameters OK.") message may also be observer with Gmailer for Windows
16-bit versions on Windows for Workgroups when using certain versions of
the Microsoft TCP stack (observed with Microsoft Socket Driver Version
2.2a). This may occur is symbolic IP names are used instead of IP
addresses. The workaround here is to use the numeric IP addresses form, or
upgrade the TCP drivers.
(c) Copyright 1982-2018 Gallagher & Robertson AS. Webmaster: webmaster@gar.no

URL: http://www.gar.no/support/errors