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.

E0230: Gproxy, terminates on non-critical TCP error events

Product: Host Links, Gproxy
Platform: Any
Status: Closed, fixed in 5.01.
Last updated: 1997-04-16 16:56:34

Whenever a TCP error event is posted to Gproxy, the program
writes an error message in the log-file and terminates. An
example of such a non-critical TCP error, is a TCP error that
occurs in the middle of a Glink (to Ggate) connection request
(applicable when doing load balancing).

The corrected Gproxy only reports the error in the log and
continues processing.

(c) Copyright 1982-2018 Gallagher & Robertson AS. Webmaster: webmaster@gar.no

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