General Troubleshooting

If you have problems running Enterprise Server, complete the following steps:

  1. Check the system requirements.

    Make sure your system meets the minimum hardware and software requirements necessary to use the product. Refer to the system requirements for Enterprise Server in the DATABridge Installation Guide.

  2. Check log files.

    Check the Enterprise Server log files for error messages. The Start menu includes a shortcut to the Log files. For more information, see Log Files.

  3. Check the DATABridge Director settings.

    Determine whether the Director service is running and listening on the correct port. (In the DATABridge Enterprise window, click the DBDirector button. The service status is indicated below DBDirect Service Control.) Also check the Windows Event Application log for messages from Director. Possible problems include:

    • Another program is already using the specified port.
    • The Enterprise Server registry keys are missing or corrupted.
    • The Enterprise Server program is missing from the program directory.
    • The program directory has been renamed or moved.
  4. Check the Server Accessory on the mainframe.
    • Make sure that the Server Accessory is running on the primary system. If it is not running, refer to the DATABridge Host Administrator's Guide for instructions on how to start it.
    • Make sure that the Server Accessory port number to which Enterprise Server is connecting (shown in the DBEnterprise Sources pane) matches the port that the Server Accessory actually uses. If more than one copy of the Server Accessory is running, make sure they use different port numbers.
    • If Enterprise Server returns an error in interactive mode saying it could not connect, the Server Accessory may have reached its limit on the number of Workers. To resolve this, increase the limit set in the DBServer AX WORKERS configuration setting.
    • Check if DATABridge has any waiting entries. For example, DATABridge may be unable to recompile the DBSupport library because of a missing file.

  5. If the audit-available notify feature doesn't work, determine the cause.
    • Check the Windows Event log for errors.
    • Verify that Director initiates a copy of Enterprise Server to respond to the notification.
    • Confirm that the username and password associated with the notification batch file are valid.
    • If multiple copies of the Server Accessory are running, make sure that they use different notification filenames. (See the DATABridge Host Administration Guide for details.)

  6. Check if Windows Task Manager shows copies of DBEnterprise.exe running after replication has finished.

    If Enterprise Server encounters errors during replication, it may be displaying a dialog box prompting you to display the log.

  7. Contact your product distributor or technical support.
    • If you cannot identify and solve the problem without assistance, contact your product distributor. Call from a location where you have access to the problem MCP server.
    • Troubleshoot the problem using information available from Attachmate Technical Support at http://www.attachmate.com/support/. This service directly links you to our internal help desk system, 24 hours a day, 7 days a week.