System Errors - Audit Notification Server Messages

This topic describes the error messages that the translator may write to the Audit Log and the Windows Event Log on behalf of the Audit Notification Server.

The following table describes the error messages generated by the Sterling Gentran:Server® Audit Notification Server.

Table 1. System Errors - Audit Notification Server Messages
Msg ID Message Text Explanation Your Action
2 ANServer startup error [error explanation] in function [function of the program in which the error took place] The system writes this error only to the Windows Event Log.

This error indicates that Audit Notification was unable to start due to errors initializing business logic, such as logging into the database, reading a table, or reading a value from the registry.
  • Depending on the explanation represented by the error explanation, take the appropriate action to determine what caused the error.
  • Use Control Panel/Services to verify the ID that the service uses to login.
  • Check the Windows Event Log for more details.
  • Call support if restarting doesn't work.

For example, if the error is a database error, verify that SQL is started and verify that the database login for the service is correct.
3 ANServer shutdown error [error explanation] in function [shutdown function in which the error took place] The system writes this error only to the Windows Event Log.

This error indicates that an error occurred when Audit Notification was stopping. On shutdown, Audit Notification saves values into the registry. The system may have encountered an error writing to the registry.

 Call support.
4 Service error: [error explanation] The system writes this error only to the Windows Event Log.

This error indicates that Audit Notification was unable to start due to a system error such as "handler not installed" or "bad service request."

 Call support.
9 Error writing message [message number] to Audit Log: [error explanation] The system writes this error only to the Windows Event Log.

This error indicates that Audit Notification encountered an error writing the designated message to the Audit Log.
  • Depending on the error message, take appropriate action.

    For example, if the system could not write the message because the database was down, restart the services.

  • Check the Audit Log and Windows Event Log to determine if the system wrote other related errors.
  • Call support.
10 Error writing notification: [notification name] to Notification Log: [error explanation] The system writes this error only to the Windows Event Log.

This error indicates that Audit Notification encountered an error writing an entry to the Notification Log.
  • Depending on the error message, take appropriate action.

    For example, if the system could not write the notification because the database was down, restart the services.

  • Check the Audit Log and Windows Event Log to determine if the system wrote other related errors.
  • Call support.
11 ANServer error [error explanation] in function [area of the system in which the error occurred] The system writes this error only to the Windows Log.

This error indicates a general type of processing error. This error may occur when a user has modified an audit message, operator, or notification and the system cannot update its internal table due to a database error.

 Analyze the error and take corrective action, if appropriate. You can restart the service. If the service does not start successfully, check the Audit Log and Event Log, and call support.

For example, if the database went down, restart the service.
12 Error generating Notification:(HR=[system error code]) [error explanation]. Notification: [notification name] Action: [notification action such as e-mail or page] Operator: [name of notification recipient] Audit Notification writes this message to the Audit Log and the Windows Event Log when it cannot generate a user-directed notification successfully. Analyze the error and take corrective action, if appropriate. You can restart the service. If the service does not start successfully, check the Audit Log and Event Log, and call support.

For example, if the database is down, restart the database and then the Sterling Gentran:Server services. If the error continues, check the Audit Log and Event Log and call support.
13 Error generating Notification [notification name] Scheduler Event: [name of the Notification Type Scheduler event that Audit Notification was attempting to start] Audit Notification writes this message to the Audit Log and the Windows Event Log when it cannot generate a Notification Type Scheduler event.

This error indicates that Audit Notification was unable to generate a Notification Type Scheduler event. (The system starts the event by sending an RPC-based request to the Executive service.)

 Check the Audit Log for messages generated by the Executive service that indicate what error occurred starting the event, and take appropriate action or call support.
200 [action being attempted]\r\n\r\nError returned by ANServer:[system error code]\r\n[error explanation] The Audit Context object generates this message. The Audit Context handles program requests to write to the Audit Log by forwarding the requests to Audit Notification. If Audit Context cannot communicate successfully with Audit Notification, it writes this error to the Windows Event Log on the client machine of the program requesting the Audit Log entry.

For example: The action being attempted may be "Unable to create EventIDServer object from ANServer".

This error also may occur due to a network issue.

 Verify that the Audit Notification System is running and has not encountered any errors (check the Audit Log and the Windows Event Log on the Audit Notification server). If there are errors, restart Audit Notification and the other Sterling Gentran:Server services. Then retry whatever client action was being attempted when the 200 error generated.

For network issues, verify that the client machine can connect to the server (use Windows Explorer or Network Neighborhood, or contact your System Administrator to verify connectivity).

If the problem still occurs after you have restarted the services and verified network connectivity, call support.
201 Audit Log call failed. Error returned by ANServer: [system error code]\r\n[error explanation]\r\nAudit Log data:\r\n[formatted text of the message that the program was attempting to write to the Audit Log] The Audit Context object generates this message. The Audit Context handles a program request to write to the Audit Log by forwarding the request to Audit Notification. If the Audit Notification System returns an error indicating that it could not process the request, then Audit Context writes this message to the Windows Event Log on the client machine of the program requesting the Audit Log entry.

For example: In a distributed system, if you open the Mailbox Server client on a machine that is not the same server where the Audit Notification Server and the Mailbox Server are installed, the Mailbox user interface attempts to write an Audit Log message indicating that you started the client. The user interface program requests that Audit Context write the Audit Log entry.

However, Audit Context receives an error back from Audit Notification when it requests that the entry be written. Audit Context then writes this error message to the Windows Event Log on the local machine.

 Check the Audit Log and the Windows Event Log (on the Audit Notification server, not the client machine) for errors issued by Audit Notification. Depending on the error, restart the Audit Notification System. If the problem still occurs, call support.