Trouble shooting in The following four points of the optimization process are known to be the most frequent in which an error might occur:
For a more detailed description of the program sequence, see the figure in Program Sequence and Data Flow of Tosca Structure. When the program is started, the configuration is first loaded and the licenses are checked. Information regarding this can be found in the protocol file authorization.log (see also Special Logfiles). Afterwards, the Tosca Structure
control program will be started. Protocol information will be printed
to the display and to the file ![]() The sequence of configuration
files that are read in the beginning of the optimization will be logged
to ![]() For each module that
is started by the control program and finishes, an entry with information
concerning the running time of the module can be found. For example,
in ![]() The course of the
individual processes and cycles can be seen in the following figure and can be followed in the protocol file Several points should be checked depending on where the program stop occurred. These are illustrated in the diagram below together with the protocol files where the error messages are saved. Different error messages, their causes, and possible ways of correcting these errors are also described in the following section. A description of which files contain error messages is also given. |