ezAudit has been designed to be as trouble-free as possible and has been thoroughly tested. However, not every usage scenario can be anticipated. This section is intended as a starting point diagnosing and solving problems, but should not be viewed as an all-encompassing source of problem resolution.
If the difficulty you’re experiencing is not covered here, contact the dealer who provided you with ezAudit first. Alternatively, you can contact dcsTools.com - see the topic on technical support.
Application Bugs or Errors
Bugs and errors generally fall into one of two categories - a bug, which is the application not doing something as you might have predicted it would, or; an error, which is the failure of the application to run or perform a specific task altogether.
If you find a bug, report it. Every effort is made to ensure ezAudit performs as expected, but there may be circumstances that were not predicted in the development of the software. See the section on Technical Support for information on reporting a bug.
If you encounter an error, you will get an error message indicating a severe failure and ezAudit may terminate. Provisions are made to "catch" such errors and log the error information to a file in the ezAudit application directory. The filename is ezAudit.ELF or ezAudit.EL, depending on the version of ezAudit you are using. Again, report any application errors you encounter. You may be asked to send the appropriate log file for analysis.
Quick Links to Specific Problems & Troubleshooting Tools
Basic Troubleshooting Steps
Before getting too far down the road in trying to find your problem, check these items to be sure your environment for running ezAudit is correct.
1.Make sure your PC (the one on which you are running ezAudit) meets the minimum hardware requirements for this application. See the section on hardware requirements for more information.
2.Make sure your PC is functioning properly. This is a broad statement, but suffice it to say that if your PC is suffering from "blue-screens" or is "locking up" for no apparent reason, the PC may be a part of the problem.
3.Ensure that the pathway to retrieving audit files is correct and "reachable" from your PC. If you are retrieving audit files from a LAN (local area network), make sure you are correctly connected to the LAN and can "see" the host file server. The logged-in user must have at a minimum "Read" privileges in the folder containing audit data files.
4.Make sure that you have a default printer assigned in your operating system. Some functions in ezAudit might fail if you have no printers defined. These problems may at first seem unrelated to printing. Some of the dialogs in ezAudit offer print capability and automatically check for a printer when the dialog is opened.
