Common Errors

This page is intended to be a list of commonly encountered error messages, what they mean, and a set of potential resolutions. Please feel free to add any error message for which you have a good understanding of at least the solution.

World Runtime Errors

Error 1017 when connecting to world

When connecting from the login server's server list to your server's world, you receive error 1017.

This error generally means that the client was unable to talk to your world server. This can happen for many reasons.

Solution: Consider this list:

1. You client may not be compatible with your server. Please see the DoNotPatchWarning.
2. Make sure your world (and zone) servers are not bound to 127.0.0.1. This can happen in the <tcp> directive of your XML config file.
3. Make sure you do not have any firewall software preventing connections to port 9000 (and your assigned zone ports) using udp.

.. somebody add more...

Zone Runtime Errors

Memorizing a spell: spell_id range invalid

Exact text of the message still needed.

Solution: You are missing the spells_us.txt file from your everquest directory in your eqemu starting directory.

Mysql server has gone away

Exact text of the message still needed.

Solution: The mysql version your eqemu is built against is too far away from the version you have installed. You must rebuild eqemu against your version of mysql, or downgrade your version of mysql to one which better matches your eqemu build. The official builds are currently built against mysql 4.0.21.

NPCs do not respond to hails for quest.

This can be caused by many issues.
Solution: Consider this list:

1. Make sure you are using a zone which is compiled with perl support. Look for "Loading embedded perl XS" or "Loading embedded perl XS" in your zone log file.
2. Make sure you have quests, and that they are in the correct directory. By default, there will be a directory called quests (lower case), which will contain a directory for each zone with the zone's short name. It is possible to change the main 'quests' directory in your XML config file, so you might check that as well.
3. Make sure that the quest even exists. Check that there is a quest file in quests/zone_short_name/NPC_Name.pl first of all.
4. It is also possible that the quest was written for perl XS, but XS was not enabled in your build of zone. This should not affect the text portions of your quests, but may affection other functionality. If XS is enabled, you will see ""Loading embedded perl XS" in your zone log file.

Compile Errors

error LNK2001: unresolved external symbol...

error LNK2001: unresolved external symbol joe
This is saying that the function or variable joe is missing from the link. You should run a find in files to locate this function and make sure that the file it is in, is included in your project.

error LNK2001: unresolved external symbol BLAH::YAY
This is a special case of the above error, which specifies the object which the function belongs to. This should make locating the missing easier, since it is likely in BLAH.cpp.

Solution: You are missing some files from your project. Try to figure out what files are missing and add them. A common way to figure out what is missing is to open up the makefile.common file, and make sure that you have a .cpp file in your visual studio project for each .o file in the makefile.


My server appear in the list of the login server but when i try to connect , i'm back to the login page.

---

CategoryServer CategoryDevelopment