Error 109, start refused.

Error 109 indicates a problem starting MadeGuard. See our guide for ways to help.

Error 109, start refused.
Fantom_Wolf
Nov 13, 2024

What is error 109 ?

Error 109 concerns an anomaly related to the file name. The system expects the file to be specifically named “MadeGuard_Starter/Pro/Business.” If the name is different, it triggers error 109.

Why is this error happening ?

There may be several reasons for this:

  • The file name was not correctly named “Madeguard_Starter/Pro/Business.”
  • Errors in the serveur.cfg file.
  • Anomalies related to the location of MadeGuard in the resource file.
  • Missing or corrupt files.
  • An outdated version of MadeGuard.

How do I resolve error 109 ?

  • Make sure the file has the name “MadeGuard_Starter/Pro/Business.”
  • Check the serveur.cfg to make sure that “MadeGuard_starter/Pro/Business” is correctly located in the resource file.
  • Check the MadeGuard version and make sure it's up to date.
  • Verify that there are no missing files and that all are intact.
  • If the error persists, consider reinstalling your version of MadeGuard.
To ensure the optimal functioning of MadeGuard, be sure to position it directly in the “resources” folder, without including it in an intermediate subfolder.
Make sure MadeGuard is properly referenced in your server.cfg: “ensure MadeGuard_Starter/Pro/Business”. For its proper functioning, put it at the top of the list so that it starts first.

Recommended steps

If you have a problem with MadeGuard related to error 109, we recommend that you carefully review your serveur.cfg, ensure that the file has the name “MadeGuard_Starter/Pro/Business”, consider updating or reinstalling MadeGuard and, if the difficulty remains, ask our helpdesk.