Common Errors

Commonly encountered errors when setting up ElectronMS

This page contains plausible solutions for common issues faced during set-up.

---

Issue: Large number of build errors encountered

Especially when the errors logged include numerous illegal start of expression errors.
Example:

Solution:

• Double check your encoding is set to x-windows-949

Related FAQs:

• Do I need to set the encoding?
• Can I use Netbeans instead of IntelliJ for IDE?

---

Issue: SQL Error along the lines of Out of range value for column 'lastlogin'

Example:

This typically occurs if you used AzureMS's pre-populated database initialisation scripts.

Solution:

• Delete the offending entry from the database
• Or, just ignore the error

Related FAQs:

• Which SQL script should I use?

---

Issue: WZ-related NPEs

Example:

This is the result of the program not being able to find the WZ folder using relative paths.
You should not need to re-dump, since the WZ-dump are already a part of the repository.

Solution:

• Make sure you cloned the repository properly
• Double check that the configuration of the project are similar to what you see here and here

---

Issue: FileNotFoundException: property\ServerSettings.properties

Example:

This is the result of the program not being able to find the properties file using relative paths.

Solution:

• Make sure you cloned the repository properly
• Double check that the configuration of the project are similar to what you see here and here

---

Issue: (Maven) Command execution failed

Example:

[ERROR] Command execution failed.
org.apache.commons.exec.ExecuteException: Process exited with an error: 1 (Exit value: 1)
    at org.apache.commons.exec.DefaultExecutor.executeInternal (DefaultExecutor.java:404)
    at org.apache.commons.exec.DefaultExecutor.execute (DefaultExecutor.java:166)
    at org.codehaus.mojo.exec.ExecMojo.executeCommandLine (ExecMojo.java:982)
    at org.codehaus.mojo.exec.ExecMojo.executeCommandLine (ExecMojo.java:929)
    at org.codehaus.mojo.exec.ExecMojo.execute (ExecMojo.java:457)
    at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo

Note that Maven delegation on first run is only so that you can let Maven grab all the dependencies automatically for you.
In practice, due to namespace issues, Maven might not be able to build/run the project properly (for some users) - an issue inherited from AzureMS.

Solution:

• Turn off Maven delegation
  1. Go to File -> Settings...
  2. Search for runner
  3. Deselect Delegate IDE build/run actions to Maven