I'm wondering about this error

[palaxe]

Everytime I start my server I get this error. Everything seems to run right. Is this patch error normal or is there somthing I did wrong?

***[Status] Using database 'eq2' at localhost
[Status] CURRENT_WORLD_VERSION:EQ2EMu 0.6.5 Developer Alpha
[Status] ./LoginServer.ini read.
[Status] Connecting to Update Server..
[Status] Connected to Update Server: updates.eq2emulator.net:9103
[Status] Checking for updates.
[Status] Found Updates.
[Status] Processing Updates.
[Error] Error in updating tables query '
update revive_points, zones set zone_id=zones.id where zones.description = zone_
name': #1267: Illegal mix of collations (latin1_swedish_ci,IMPLICIT) and (latin1
_general_ci,IMPLICIT) for operation '='
[Error] Attempting to update database table 'revive_points' ... FAILED!
[Status] Table Update complete.
[Status] Processing Data Updates.
[Status] Attempting to update database table 'revive_points' data ... SUC
CESS!
[Status] Data Update complete.
[Status] Loading opcodes..
[Status] Loading structs..
[Status] Loading command list..
[Status] Loaded 21 entity command lists.
[Status] Loaded 115 NPC(s).
[Status] Loaded 0 Object(s).
[Status] Loaded 0 GroundSpawn(s).
[Status] Loaded 0 Widget(s).
[Status] Loaded 0 Sign(s).
[Status] Loading ground spawn items..
[Status] Loading loot data..
[Status] Loaded 1 loot tables.
[Status] Loaded 1 loot drops.
[Status] Loaded 3 spawn loot lists.
[Status] Loading Transporter Information..************************************************************************************************************************************************
Also when you log in it says v0.0.4 not 0.6.5,I can't seem to find were in the data base I need to change this.
Thanks for all the help.

[LethalEncounter]

John had the same problem. It is related to the collations of the zones and revive_points tables. I'm not sure what he did to fix it as it was unique to his (and apparently your) setup.

[John Adams]

Edit your `zones` table properties, and change the collation to "latin1_swedish_ci". The problem is that the newer `zones` table did not have a collation specified in the CREATE, so it used whatever collaton LE's server(s) are set to (latin1_general_ci) since that table got dropped and recreated after our new Zones info went live... The zones data I believe was made on my server, who's default collation is latin1_swedish_ci. Text fields expected to update from one table to another will fail on STRICT server setups.

LE is "loosey goosey" in his MySQL configuration, so he never has the problem - nor will most people. Only those who set up MySQL to "Act as Traditional Database" or whatever that option was. Linux users will not see it unless they specifically go into my.cnf and set the mode to STRICT ALL TABLES. Thus, low risk.

[palaxe]

Well, My zones is set to latin1_swedish_ci. So any other idea's.

[John Adams]

Yeah, change all your tables to have the same collation, or remove the sql-mode = "STRICT_ALL_TABLES" setting from your my.cnf.

[palaxe]

Thanks I'll give that a shot

[palaxe]

ya I switch them all to genral still get the error so I'm putting them back to swed. I wish there was a way to do it all in one shot and not one at a time LOL.. so are we missing anything by having this error? it seems to run ok?

[John Adams]

If you have no revive_points set up, then no. You are not missing anything. What that query is trying to do is apply a change we made a while back where we dropped zone "name" (text) references to zones and replaced them with more efficient zone "id" values instead. So it's trying to find anything in revive_points where the current field value of zone_name = zones.description, and add the zone_id value to the row where it finds a match.

To really stop the error from happening, you can bump the value in table_versions to match what the updater is looking for. To do this, edit your LoginServer.ini and set "autotableverbose = true" so you can see the full process. Re-run EQ2World.exe and note the lines that say something like:

[Error] Login reports that the latest version of the 'revive_points' is 5, you are using 0. The query that will run to update your table is:

What this is saying is, WE expect values to be 5. Your table_versions for 'revive_points' says 0. Change your revive_points to 5, and you will stop trying to receive this update - which you do not need anyway if you have no revive_point values.

Note: the values for release 0.6.5 are all 65000 ot greater for most tables - see the other post about the update server for more details.

Hope that made sense.

[palaxe]

Totally makes sence. Thanks for posting that, I know you guys are very busy. I guess I'm like you if something isn't running just right it bugs me. LOL. Right now I'm not using revive points but I think I'll try and change the point anyway just for learning xp. I'm on level 2 with data base xp and a long way to go. It's very cool to have a Dev team that will take a second out of there hard work to answer questions for us all. Thanks John.