Symantec™ Security Gateways Reference Guide - Sawmill

Log messagesWarning messages (300-399)195301 - Unable to create ticketDescription: The Out of Band Authentication (OOBA) daemon was unable to create an authenticate ticket for this user,so the user is denied access.301 - Unable to destroy ticketDescription: The authentication ticket of a user was not destroyed, so the user is allowed through the security gateway,although the access should be denied.301 - Unable to determine interface for destination addressDescription: Unable to determine the connection destination because of a security gateway misconfiguration.301 - Unable to determine interface for destination address due to message size mismatchDescription: Unable to determine the connection destination, which is because of a security gateway misconfiguration.The size of the packet that got sent was less than what we requested.301 - Unable to find number of free bytes for fileDescription: (Microsoft Windows only) Attempts by the logservice daemon, to release disk space for logging has failed.301 - Unable to fork to make childDescription: The secure remote login (SRL) daemon is unable to create a child process to handle new connections and isrestarted. The status parameter identifies the errno variable.301 - Unable to get endpoints for securityDescription: This indicates a corrupted configuration file.301 - Unable to get security gateway(s) for instance of security policy between and Description: This indicates a corrupted configuration file.301 - Unable to initialize NAT treesDescription: This message indicates an internal software error. Please contact Technical Support by phone or online athttp://www.symantec.com/techsupp/ to report this.301 - Unable to load security policyDescription: A component is unable to load a security policy (gwcontrol). The security policy may have a problem thatcould become more serious. The administrator needs to recreate the security policy and resume theprocess.301 - Unable to load security policy templateDescription: The configuration file is corrupted. To correct the problem, reconfigure and save the information.