MEGMS logo - go to the home page

  1. Home

    1. MEGS_Log

      1. MEGS_Log Downloads

      2. MEGS_Log Documentation

        1. MEGS_Log version 3.3 Help

          1. Copyright notice and licence agreement

          2. How to contact MEGS_Log support

          3. What's new in MEGS_Log 3.3

          4. Concepts in MEGS_Log

          5. How to carry out common tasks within MEGS_Log

          6. Menus and commands

          7. Window elements and dialogs

          8. List of appendices

            1. MEGS_Log error messages

              1. Info 0: No error

              2. Error 1: Unable to open filename

              3. Error 2: Unexpected end of file

              4. Error 3: Bad config file

              5. Error 4: Incorrect configuration file version

              6. Error 5: Format problem with configuration file

              7. Error 6: Name not found

              8. Error 7: Unrecognised element type

              9. Error 8: Bad bitmap

              10. Error 9: Unrecognised colour

              11. Error 10: Unrecognised boolean value

              12. Error 11: An attempt to create a new thread failed

              13. Error 12: Error reading file

              14. Error 13: Prolog file does not look like a prolog file

              15. Error 14: Unrecognised section in config file

              16. Error 15: Duplicate sections in LAS file

              17. Error 16: Unrecognised key in LAS file

              18. Error 17: Format problem with LAS file

              19. Error 18: Missing section in las file

              20. Error 19: No samples

              21. Error 20: Unable to understand the sample number format

              22. Error 21: Borehole consistency check failure

              23. Error 22: Internal error

              24. Info 23: Cancelled

              25. Error 24: Depth or thickness values are inconsistent

              26. Error 25: Unit too thin

              27. Error 26: Bad record type

              28. Error 27: Name expected

              29. Error 28: Unexpected end of file

              30. Error 29: Unsupported characters

              31. Error 30: Configuration file not found

              32. Error 31: Valid licence not found

              33. Error 32: Licence request generation failed

              34. Error 33: Licence update failed

              35. Error 34: Too many fields in schema

              36. Error 35: No depth fields in schema

              37. Error 36: Schema has no rocktype field

              38. Error 37: Depth or thickness values missing

              39. Warning 38: Schema not used

              40. Error 40: Demo mode

              41. Warning 40: Demo mode

              42. Error 41: Unrecognised integer

              43. Error 42: Error creating directory

              44. Error 43: Unexpected exception

              45. Error 44: Error copying file

              46. Error 45: Bad line style

              47. Error 46: Bad vector definition

              48. Error 47: Unknown file extension

              49. Error 48: Duplicate name

              50. Error 49: Invalid file conversion attempted

              51. Error 50: Mismatched schema

              52. Error 51: Invalid parameter

            2. Registry key reference

            3. Frequently asked questions

            4. List of short-cut keys

            5. Command line options

          9. MEGS_Log version 3.3 Help Index

    2. CoalLog tools

    3. Fortran Tools

    4. Contact Us

  2. Site map

"Let's model me a mine"

M.E.G.M.S.

Mining & Exploration Geological Modelling Services

Previous topic Parent topic Home topic Next topic

Error 30: Configuration file not found

A valid configuration file could not be found during MEGS_Log startup.

A MEGS_Log configuration file is always named MegsLogConfig.txt. MEGS_Log looks for the configuration file in the following directories in order:

Depending on your operating system version and your installation configuration, the directory names may be different to those given as examples.

To resolve the error, locate a valid configuration file and copy it into one of the above directories. Alternatively, re-install MEGS_Log. The MEGS_Log installation process places a configuration file in the MEGS_Log program files directory that contains default configuration.

Previous topic Parent topic Home topic Next topic