F-SECURE INTERNET GATEKEEPER WINDOWS 2000-2003 SERVER 6.61 Administrator's Manual page 401

ID Severity Trap
510 Error Ungraceful
Message Pump
Quit
520 Fatal Error Unable to Register
in Message
Broker
530 Fatal Error Unable to Register
in Configuration
Handler
535 Error Network Request
Broker
Unreachable
536 Error Database Update
Handler
Unreachable
Message When/Why
Quit the message Unexpected problem
pump with error: %1. during product operation.
Registration in Can be issued by any
F-Secure Message component if there is
Broker failed due to something wrong with
error: %1. F-Secure Management
Agent. This alert can also
mean that the component
with the same OID is
already running.
Registration with Can be issued by any
F-Secure Configuration component if there are
Handler failed due to problems with F-Secure
error: %1 Configuration Handler, a
component of F-Secure
Management Agent.
Network Request When the Database
Broker (NRB) cannot Update Handler fails to
be reached to send a register/unregister with the
request. Network Request Broker.
Database Update The F-Secure Content
Handler cannot be Scanner Server daemon
reached to send a fails to register to the
request. Database Update Handler.
APPENDIX H
Error Codes
Solution
Usually this alert can be
ignored. If the alert is
continuously reported, try to
restart the product or reboot
the system.
Check that F-Secure
Management Agent is
correctly installed and
running. Restart the product
or reboot system.
Reboot the system. If the
problem persists after
reboot, contact F-Secure
Technical Support.
Make sure the F-Secure
Network Request Broker
service is up and running.
Try to enable or disable (if
needed) automatic polling
for new database updates
from the Web Console of
F-Secure Policy Manager
Console.
If this alert occurs,
database updating is not
possible. Check if the
Database Update Handler
is running. Restart the
product or reboot the
system.
401