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.

E1229: Gspool Monitor did not write log file

Product: Gspool Monitor
Platform: All Windows
Status: Fixed for R6.6, fix available for R6.5
Last updated: 2010-11-25 10:05:11

Gspool Monitor is a Windows-only tool for tracking print reports
delivered from the mainframes to Gspool, provided Gspool uses the -hist
parameter to update the Gspool history file:


Gspool Monitor can be started from the toolbar in Gmanager or as a free-
standing application. It behaves in some ways as a Host Links server. By
default it writes a log in:


where <node> is the dsa node name of the Windows platform.

The log function was failing, due to the fact that the server logging
routines expect the directory:


to exist. These directories are normally created during the Host Links
server initialization routines, but since Gspool monitor is not a real
server it was not executing the initialization routines. Since the log
file could not be created no log was written, and also the most vital log
messages were delivered to the Windows event manager as errors in the G&R
custom log.

The work around is to create the directory:


manually, and restart Gspool Monitor.
(c) Copyright 1982-2019 Gallagher & Robertson AS. Webmaster: webmaster@gar.no

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