Debugging Issues with AcuConnect®

October 17, 2002

This document covers the basic steps to use when debugging AcuConnect issues. Following these suggestions should help to pinpoint the cause of most problems encountered when using AcuConnect.

  1. Execute the client machine runtime with a trace. In the trace file verify that the correct configuration file is being used and that the correct AcuConnect remote syntax is being used for CODE-PREFIX (i.e.,*servername, and not @servername or other).

  2. In the client machine runtime trace, check the setting of the ACUCONNECT-CONFIGURATION-FILE option and make sure it is correct. If it points to a non-existent file, the file name is misspelled or the path is incorrect the AcuConnect runtime on the server will not be able to find it and will use the cblconfig file in the /etc directory if it exists. If it does not exist the server side runtime will attempt to run without a configuration file.

  3. If running on a Windows 98 client, the runtime will ignore AcuConnect remote name notation for the ACUCONNECT-CONFIGURATION-FILE unless the fully qualified domain name for the server, on which AcuConnect is running, is used i.e:

    * ...

    If the fully qualified is not used or is set to an invalid path or file name, the Acuconnect runtime will use the cblconfig file in /etc directory on the server if it exists. If it does not exist it will attempt to run without a configuration file.


    *servername:-le path/[error file name]

    to run an AcuConnect (server side) runtime trace. Errors that are returned to the client such as file status 35 will appear in this trace.

  5. Run an AcuConnect server trace. This is done by including:

    a. -lxe errorfile_name
    b. -t3

    on the command line when starting AcuConnect i.e.:

    acuconnect -start -c /etc/server.cfg -lxe trace -t3

    connection permission errors and errors such as "AcuShare not running" will appear in this file.

Your Session will expire in 90 minutes
Notification will be shown in:
600 seconds