Topic:
Error displaying picture; could not build fault data list, db_e_ntrp_flt_path_read

Description:
Error displaying picture
interpretation rendering failed
could not build fault data list
error during read operation on specified fault
status: db_e_ntrp_flt_path_read
error reading from display file

The above message will be listed in an IESX error window that pops up when
SeisDV attempts to display a portion of seismic data that contains (within
the extent of the requested display) corrupt fault data ("bad" contacts, cuts,
and/or traces).

It may occur when using the scroll bars within SeisDV, when selecting a new
line within SeisDV (Display > Seismic Line), or when sending a new line from
Basemap to SeisDV. 

Solution:
Identify and delete the corrupted portion of the fault contact(s), trace(s)
and/or cut(s).  

These errors occur when some portion of the fault interpretation is corrupt. 
Additional messages may be included in the above error message list or other
operations within IESX applications may return error messages that indicate 
the fault data type that is causing the problem.

This problem is tough and its resolution may be require a great deal of 
manual intervention.  At some point during your efforts, you might want to 
consider restoring the project from a backup made prior to experiencing the
problem.

Often, a single contact, cut or trace is corrupt and is in the group most
recently created.  Try deleting fault interpretation beginning with the most
recent (DataManager > Interpretation Delete).

Or, you may be able to resolve the problem by exporting the interpretation to
ASCII files, deleting the interpretation in the project, and then importing the
interpretation from the ASCII files.

Or, create a clone and merge in only the interpretation that you wish to
preserve.  Merge in a single type (and subset of that type) of interpretation 
at a time and check for the errors.  Remember that the errors occur only when
the spatial extent of the seismic display includes the corrupt interpretation. 
Continue iterative merging/checking and delete the most recently merged when 
the errors are encountered (that deleted will have to be reinterpreted).

Or, consider running iesx_util.csh options 23, 24, and/or 25 to delete duplicate
fault contacts, cuts, and/or traces.  This will SOMETIMES resolve the problem.
The execute time for these options is proportional to the amount of
interpretation and may be significant.  For projects with a large amount of 
interpretation and when running on slow systems, these operations can run for
several hours.

Possible Actions:

1) Check disk space
2) Check permissions on all DSLs associated with project and interp files.
Reorder interpretation DSL.
3) New session
4) iesx_util #41 - any missing files?
5) Rebuild indexes
6) Rebuild interpretations
7) Delete traverses with long descriptions, use less than 49 characters.
8) Touch missing files
9) Check the navigation data
10) Patch project (cp .da to .da.sav, iesx_util #3 to remove data area, cp
.da.sav to .da, patch project)
11) Delete user's iesx_config directory with iesx_util #3.
12) On 2d lines, look at sp numbers. Try renumbering the line(s).





Last Modified on: 26-APR-00