In the following chapters we will give you some hints in case of problems with the usage of the software. Problems regarding the installation and the licensing are described in the Administration Manual.


Before you send to use your data, please minimize your input data-file.

To minimize the SSD project files and SOFiPLUS drawings is the most important strategy to find and eliminate input errors. Please delete every SSD-task, structural elements, program blocks, load cases, etc. which are not involved with your problem. Now you have a small and clear project, which can be checked easily. In almost every case you will find out where the problem occurs and also you will be able to solve it by yourself.

Please use this strategy also if you can’t find the problem and send your minimized project file with your support request via Email to

General Strategy#

Please keep in mind the following points in case you encounter some incomprehensible errors:

  • The probability that an error has been caused by wrong input is significantly large. The observation of warnings at any stage during the analysis or the installation can supply valuable hints.

  • All programs, even those of SOFiSTiK, contain errors as long as the are used. They will show up most likely if you are in hurry and start treating some completely new application area of the programs. You should therefore first examine how the program behaves, using small examples. One of the most frequent causes of such errors is a misleading interpretation of the manual or the implemented theory.

  • If the system was still working yesterday, think about what has changed since then (new computer, new operating system, other inputs etc.)

  • In some cases an error message may not describe the real cause of the error, although this is highly unlikely. It might occur when the error was not correctly detected in a previous module. The programs do not stop at the first error they encounter, but try to continue and to detect as much errors as possible.

  • Rather than searching for hours, sent a support request via Email to SOFiSTiK Support or your local supporter. Even if you may be charged for extensive services, it usually will be more economical as SOFiSTiK has better possibilities to locate the error.

Problems with Database#

Error messages of the Database CDBASE can occur for the following reasons:

  • Due to an abnormal termination of programs the file gets disorganized. If only the locks are not released you may remove them with a special button or with the command:

    database_tools_large ‘’Database Tools’’ Clean Locks


    1. click via right-mouse-button right_mouse_button_small onto .CDB file

    2. from context menu select SOFiSTiK 2023

    3. Clean Locks

  • Saving the data base periodically is quite wise especially for working with large projects.

Input Error in TEDDY Datafile#

In case of a wrong input in the TEDDY file, the program gives you an error message. If you open the report_browser_small ‘’Report Browser’’ output and go to the ECHO print, the error message is plotted directly after the incorrect input line. Also the error message gives you some hints what should be the correct input. This will help you in most cases to find and eliminate the wrong input.

Error in System Generation with SOFiPLUS#

If you run into errors while meshing your SOFiPLUS drawing you may use a very simple algorithm to locate the problem. First mark randomly half of your structure and delete it. Now start the meshing again. If the problem occurs again, mark the next half of your structure,delete it, mesh again and so on. If the problem does not occur, go back and mark the other half of your structure, delete it and mesh again. With this principle of deleting stepwise half of the structure you will minimize your system. Probably you will find the error by yourself and can solve it. If the problem is solved you go back to your complete system and solve the problem there as well.

If you can’t solve the problem please send your minimized drawing to our support.

Error during Calculation#

Normally we face two major problems in case the analysis will be aborted with an error message. Either the system is instable or no convergence was found during a non linear analysis.

  • System instable:

    In case you use the program ASE for the analysis and have an instable system, the program calculates Eigenvalues using a numerical trick. Now you can check the displacements of the Eigenvalues with the program fea_viewer_small FEA Viewer. Then you will see very quick, what causes the instability. Normally the instability problems occur in large 3D systems with lots of hinges and kinematic constraints. Therefore we recommend the following procedure: Create your system Step by Step and avoid to define any hinges and kinematic constraints in the first Steps. Now define a load case self weight and start the linear analysis. If you get some reasonable results go further on and start to define the first few hinges. Now export your system and start the linear analysis again. If everything works fine, go on with this procedure until everything is defined. If you work Step by Step, you always know the last changes and can easily go back. Possible input errors will be found very fast.


    In case you can’t find the problem, please send your minimized file to

  • Non-linear analysis

    The most common problem during a non linear analysis is, that no convergence will be reached. Either the structure is to weak for the applied loads, or the chosen algorithm has some numerical problems. In the first case you may change dimensions and therefore enforce the structure. In the second case you may change the iteration method. In both cases the program gives you detailed information about possible changes in your non linear analysis. With this hints you may solve the problem. In other cases please reduce your system to one single load case and delete everything, which is not necessary to reproduce the convergence problem. Sent this reduced file to

  • Problem with results

    The interpretation of the results may cause some questions. Every manual contains a chapter ‘’Theoretical Principles’’. Inside this chapter the basics of the design algorithms are explained so that a manual check of the design results will be possible.

    In case you have additional questions related to the design results. you may send a support request to our technical support team via E-Mail to

    To answer your questions as soon as possible we need additional information and data files from you:

Standard Warnings and Error Messages#

The story of an analysis is stored in a protocol file of the file type .PRT. In all special situations (program error or user error) this file must be examined. The execution of the analysis is automatically stopped if such an error occurs. Regular errors or Warnings have the form:

  • Warnings, the program prints the message:

    ++++ WARNING NO. nnnnn IN PROGRAM xxxx

    as well as one or more lines of explanations.

    • The analysis continues.

    • Calculation status is set with icon wps_warning_small.

  • User or data error, the program prints the message:

    ++++ ERROR NO. nnnnn IN PROGRAM xxxx

    as well as one or more lines of explanation.

    • The analysis continues or stops.

    • Calculation status is set with icon wps_error_small.

Finally, each program writes the number of warnings and errors in the .PRT File. If the program has been aborted this will also be visible in this file.

In some modules, warnings can be switched off with the CADINP input:

CTRL OPT WARN VAL <warning_number>