User Area > Advice
Typical error message appearing in a dialog box in LUSAS Modeller on attempting to load a model:
***fatal database error*** detected in routine
MDLUSE
This is very unusual and but the most common causes for errors of this
nature are:
- Lack of space available for temporary files
- Data corruption in model file
Model
files (*.MDL) are binary and therefore quite large.
They are opened quickly by LUSAS Modeller, but can be susceptible
to corruption. There is
unfortunately little that can be done to salvage a corrupted binary file
and so it is essential to keep backups. More on electronic
filing
Before reverting to the most recent backup
of the model, try rebooting the PC and reloading the
model. There may be more than one copy of LUSAS Modeller running inadvertently
which may cause
file handling conflicts. It would also be
advisable to check disk & memory issues for Modeller, since PC settings may cause temporary files to clash
with virtual memory, or the disk may be full
-
Relocate
or expand PC virtual memory
-
Relocate
LUSAS temporary files
-
Relocate
Windows temporary files
-
Clear
temporary files
Model corruption can occur as a result of
- Saving the MDL file with insufficient
disk space to complete the process
- Running low on disk space in the working
and/or scratch disk areas when manipulating the model
- Internal software problems as a result
of manipulating a model substantially over a lengthy period
- General electric discharge which can
corrupt areas of hard disks rendering the file unreadable
- Physical disk problems that cause bad
sectors to occur on a disk
- Saving the MDL file subsequent to MODELLER
reporting internal or system errors
- Disk errors when copying the file across
a network or, more often, from a backup tape/disk
|
