akira6968

UPDATE: Here's what I have learned! The TDB_Full is dated for 09/16/2012 The SQL Update folder within the git'd Trinity folder is chock full of SQL, each file name beginning with a date. The oldest of them is....yep, 09/16/2012. So they DO all need to be applied. As for why I was getting errors: The first time I tried to load all them many SQL queries, i highlighted all of them and opened them, then started 'running' them in no particular order, not realizing exactly what that does. I remember reading about applying updates in order from oldest to newest, and now I believe it to be the cause of the errors! Especially since, in HeidiSQL, the 'query tabs' that you use to run the sql will order from oldest to newest, bottom to top. Something like that. I'm still not positive as to what rhyme or reason Heidi has for sorting the query tabs. I'm gonna guess this problem is solved, and hopefully I've answered in a noob-friendly enough way to help others lol. We can't even figure out what a SQL is....you devs are gods/goddesses among men lol FINAL UPDATE!! That sh*t worked!

Getting a similar error, also. Just followed that wonderfully written WIKI How To:WIN, this is what I get: ************************************************************************************************************************************************************************ Realm running as realm ID 1 Using World DB: TDB 335.49 Will clear `logs` table of entries older than 1209600 seconds every 10 minutes. Using DataDir ./ VMap support included. LineOfSight:1, getHeight:1, indoorCheck:1 PetLOS:1 VMap data directory is: ./vmaps Loading Trinity strings... >> Loaded 947 Trinity strings from table trinity_string in 22 ms Initialize data stores... >> Initialized 96 data stores in 3262 ms Using enUS DBC Locale as default. All available DBC locales: enUS Loading spell dbc data corrections... >> Loaded spell dbc data corrections in 3 ms Loading SpellInfo store... >> Loaded spell custom attributes in 113 ms Loading SkillLineAbilityMultiMap Data... >> Loaded 10219 SkillLineAbility MultiMap Data in 3 ms Loading spell custom attributes... >> Loaded spell custom attributes in 42 ms Loading GameObject models... >> Loaded 2321 GameObject models in 74 ms Loading Script Names... >> Loaded 2010 Script Names in 6404 ms Loading Instance Template... >> Loaded 83 instance templates in 14 ms Loading instances... >> Loaded instances in 141 ms Loading Localization strings... [1054] Unknown column 'Id' in 'field list' Your database structure is not up to date. Please make sure you've executed all queries in the sql/updates folders. ************************************************************************************************************************************************************************ This is a fresh install on a fresh Windows 7 Ultimate VM (made copies for easier fixes if I screwed up lol). I used MySQL 5.1.51 (full dev), but when compiling I unchecked the use of included libraries, so it would look for and use the ones I already had (that was my understanding, anyway, per the wiki instructions). If I'm understanding it correctly, it looks like what we're doing (assuming wiki instructions followed correctly) is: -Git'ing the source for the server, which also comes with SQL updates for those who are updating their server (not me, i'm all freshness) -Compiling it and all that magic stuff -"Installing" a fresh TDB_Full, which should be current up to and including above mentioned updates. Once done, I'm actually able to authenticate from a remote WoW client (it tells me bad password, of course.....but I think that means it's at least connecting and looking?). Almost forgot- I also tried to go ahead and load those updates, but got many errors. Which is what lead me to believe what I stated above (we're already up to date). After getting the errors, I started over with another copy of my VM at the "configuring the conf" section of the guide. Still stuck, of course. Wish I knew more about this, but thanks for any help anyone! BTW, OP, if you figure it out, PLEASE post what you did!! I found another topic w/ exact same error i have, and the OP came on and said "fixed it, nevermind". DANG IT!!! lol I'm just guessing here, but... -OP's log shows that his 'localization strings' loaded some number of things -There are SQL entries (tables?) in the World DB called 'locales_x' -When selected (using HeidiSQL), the data shows as empty in every one of them. Should there be something there? locales_acheeve locales_creature locales_creature_text etc...all empty Hooray! OK, so I guess the DB_Full DOES need to be updated? Since my log gave me the error right after trying to "Loading Localization strings..", I went into the updates folder and looked specifically for any updates containing the text 'loc' in their name, based on a guess that "Loading Localization strings.." was referring to "Locales" tables in the DB. Sure as shit, it changed the names of some columns when I executed the SQL updates, and my World Server moved right on past "Loading Localization strings.." OP, there's a table in the DB called "Conditions", look for it's update Despite the errors, I'm guessing we should try to run all those updates, just skipping the ones that throw out errors? If a dev-genius (no sarcasm, you guys are friggin awesome) would come on and say yea or nay to skipping the error-throwing updates, I'd be tickled pink!