eValid™ -- Automated Web Quality Solution Browser-Based, Client-Side, Functional Testing & Validation, Load & Performance Tuning, Page Timing, Website Analysis, and Rich Internet Application Monitoring.

Introduction
This page describes facilities built into eValid that are used to capture, report on, and communicate about a wide range of unusual or incorrect behavior.

eValid is a very stable and well-behaved product which only very rarely will cause an operating system problem. Some types of eValid usages that tend to cause problems include:

• Monitoring mode, in which many copies of eValid are running simultaneously and when each copy has possibly conflicting use of script file and log files.
• Server loading mode, in which many copies of eValid (usually the THIN eValid engine) are running simultaneously and sharing script files.
• Site analysis mode, when more than one scan is being performed in parallel.
• Any type of operation that involves very long playbacks, or a very large number of repeated playbacks. In such cases each eValid instance's RAM allocation grows with time to the point where the machine overallocates memory and has to resort to use of virtual memory.
• Playbacks of web applications that make very heavy use of JavaScript/VBScript -- AJAX applications for example -- when the likelihood of script errors is high.

What Is Reported
When runtime problems arise they are nearly always traced to one or more of these causes:

• Conflicting User Settings
  There are a number of eValid settings that can conflict with each other during playback. In some cases these conflicts result in a runtime exception. The preventive is to modify the user-settable parameters so that the reason for the conflict is eliminated.

• License Violation
  If eValid senses a problem with the local license, e.g. you have asked eValid to perform an action that is not allowed from your current eValid feature key set, eValid will disallow the operation and terminate.

• File Sharing Violation
  If two eValid copies both attempt to open the same script at the same time this often results in a "File Sharing Violation" from which recovery is not possible.

• Unsupported Operation Violation
  In some cases, due to conflicts within the current eValid playback script, eValid will attempt an unsupported operation, and terminate.

• Insufficient RAM Violation
  eValid's footprint is like that of the IE browser, and it is possible that when too many eValid copies are operating the Windows operating system will be unable to allocate sufficient resources, and an exception results. The solution is to obtain and install additional RAM or reduce the number of eValid launch requests.

• Out Of Memory Violation
  If the available RAM is insufficient for eValid to continue operating then this may be the result of an "out of memory" situation. For example, we do know that certain JavaScript-based systems show very rapid growth in the eValid footprint, particularly when one eValid instance is run many times.

• Failed to Create Document
  This message is normally seen when the eValid instance is launched in a context which will exceed machine resources.

• Other Violation
  Other violations may occur and are reported by eValid in the same way.

Actions Taken
When any kind of exceptions occurs, eValid takes actions that differ depending on the playback mode:

• Foreground (Interactive) Mode
  eValid intercepts the exception and displays this information to the user. Only exceptions detected by eValid are handled by the eValid exception handler; exceptions that occur outside eValid, or during eValid launch and setup, are handled by the corresponding Windows exception handler. Foreground mode exceptions are not recorded in the exception log.

• Batch (Background) Mode
  If an exception occurs BEFORE eValid has completed loading then these exceptions are caught by the Windows operating system and are not reported in the evalid exception log.

• Batch (Background) Mode
  eValid intercepts the exception and logs the information into the exception file (see below). Only exceptions detected by eValid are handled by the eValid exception handler; exceptions that occur outside eValid, or during eValid launch and setup, are handled by the corresponding Windows exception handler.

Exception Log Description
When an exception occurs that causes eValid to terminate operation as much information as possible is included in the eValid exception log.

• Exception Log Name/Location
  The eValid exception log is named ~00eVexp. This file is located in the eValid installation folder in the ../eValid/Program/Docs/Session/ folder.

• Sample Exception Log Entry
  A sample exception log entry is shown below. The entry includes details about the eValid version, a timestamp of the time of the incident, details about what script was running, the specific exception code (and associated message), and characterization of the execution environment.

  ## Unhandled Exception Information # Timestamp: 07:45:34 Pacific Daylight Time, 11 January 2012 # Build: V9 Build #280 # Mode: Browser Batch # Script filename: "use10.evs" # Number of eValid instances running: 7 # Last System Error Code: 0 # Exception Code: C0000005 (EXCEPTION_ACCESS_VIOLATION) # Exception Flags: 0 # Fault Address: 0x7c168f1d # Process working size (peak): 12427264 (15024128) bytes (11.85 MB (14.33 MB)) # Process pagefile usage (peak): 8978432 (9015296) bytes (8.56 MB (8.60 MB)) # Available physical memory: 51896320 / 199544832 bytes (49.49 MB / 190.30 MB)