Errors with new DB 1751 and server 1752 install

[Huppy]

After grabbing the svn updates with the new DB (1751), I did a completely
clean install of both server (1752) and DB. No errors on compile or when
sourcing db, etc.

I got the following errors when trying to login with SoD client.

Error in CreateAccount query ' INSERT INTO account SET name='huppy' status=0, lsaccount_id=2, time_creation=UNIX_TIMESSTAMP();' #1054 Unkown column 'time_creation' in 'field list'

[Debug] [WORLD_CLIENTLIST_ERR] Error adding local account for LS login: 'huppy', duplicate name?

[Debug] [WORLD_CLIENT_ERR] NOCLE: Bad/Expired session key '2'

Then I tried to source in the 1711 fix and got this error;

[Err] 1060 - Duplicate column name 'account_time_required'
[Err] ALTER TABLE `altadv_vars` ADD `account_time_required` INT UNSIGNED DEFAULT '0' NOT NULL AFTER `clientver`;
[Msg] Finished - Unsuccessfully

[joligario]

Did 1711 finish? It looks like you only have the first sql entry that ran.

[Huppy]

No, it did not finish, thats as far as it went. I ran this update before with the
1667 db and it sourced no problem.

[joligario]

If it fails the script, I would run the timestamp line seperately just to get it in.

[Huppy]

I ran this by itself, no such luck

UPDATE `account` SET `time_creation` = UNIX_TIMESTAMP() WHERE `time_creation` = 0;

[joligario]

What's the error message now?

[Huppy]

[Err] 1054 - Unknown column 'time_creation' in 'where clause'
[Err] UPDATE `account` SET `time_creation` = UNIX_TIMESTAMP() WHERE `time_creation` = 0;
[Msg] Finished - Unsuccessfully

[lerxst2112]

ALTER TABLE `account` ADD `time_creation` INT UNSIGNED DEFAULT '0' NOT NULL AFTER `suspendeduntil`;

Your table doesn't have the field yet, so you can't change it. Did the line above run successfully? It is line 2 of the 1711 update.

[Huppy]

That was just trying out the last line by itself, none of it will source, which
ever way it is done

[Huppy]

Ok, I removed the first ALTER TABLE line and the rest sourced in without an error

[Huppy]

Just logged in with client, no problem

[Rykeau]

For what its worth I'm having nothing but issues with the 1751 database :mad:

I've compiled source 3 separate times, started with a clean DB each time, and validated the eqemu_config.xml and eqemulogin.ini files are setup exactly as they were before the upgrade. I can get to the character select screen, after selecting the character I get kicked off the server and back to a blank server select screen.

Restarting the client, I can get to the character select screen but the cycle repeats. Quite frustrating. Any suggestions on what to look at?

My setup has been working for months without issue until this compile/DB update.

Rykeau

[Huppy]

Rykeau > When I had the login problem, I never got past the server select
screen. It was the world.exe window that gave me the errors.
I ended up trying to source in the 1711 sql update, but before it would
source properly, I had to remove the first (top) line (ALTER) from it.
Otherwise, the server could not create an account in the account table.

[Rykeau]

I'm seeing a lot of World client errors. I am using EQEmuLoginServer in case it matters. Here is a sample of what I'm seeing:

[Debug] [WORLD__CLIENT_ERR] 1920: 5e 30 5e 35 38 5e 30 5e - 0a 37 33 5e 37 5e 30 5e | ^0^58^0^.73^7^0^
[Debug] [WORLD__CLIENT_ERR] 1936: 34 5e 38 5e 2e 37 35 5e - 35 0d 0a 35 38 32 5e 31 | 4^8^.75^5..582^1
[Debug] [WORLD__CLIENT_ERR] 1952: 31 35 33 30 38 35 5e 2e - 35 5e 31 2e 33 2e 38 31 | 153085^.5^1.3.81
[Debug] [WORLD__CLIENT_ERR] 1968: 0a 35 36 5e 32 35 5e 2e - 31 2e 38 0d 33 30 30 5e | .56^25^.1.8.300^
[Debug] [WORLD__CLIENT_ERR] 1984: 31 2e 38 36 31 31 37 30 - 5e 35 38 35 36 37 5e 30 | 1.861170^58567^0
[Debug] [WORLD__CLIENT_ERR] 2000: 34 35 0d 0a 31 38 5e 31 - 2e 32 32 35 33 30 30 5e | 45..18^1.225300^
[Debug] [WORLD__CLIENT_ERR] 2016: 5e 2e 30 37 0d 0a 36 5e - 33 5e 2e 33 39 35 0d 0a | ^.07..6^3^.395..
[Debug] [WORLD__CLIENT_ERR] 2032: 0a 34 32 5e 38 5e 31 30 - 35 5e 31 2e 35 5e 31 2e | .42^8^105^1.5^1.
[Debug] [WORLD__CLIENT_ERR] 2048: 5e 31 30 32 2e 36 38 33 - | ^102.683
[Debug] Unable to convert EQ opcode 0x0924 to an Application opcode.
[Debug] [WORLD__CLIENT_ERR] Rykeau: Received unknown EQApplicationPacket
[Debug] [WORLD__CLIENT_ERR] [OpCode OP_Unknown (0x0924) Size=1]
[Debug] [WORLD__CLIENT_ERR] 0000: 30 - | 0
[Debug] [WORLD__CLIENT] Rykeau: Attempting autobootup of poknowledge (202:0)
[Debug] [WORLD__ZONE] [5] Setting to 'poknowledge' (202:0)
[Debug] [WORLD__CLIENT] Rykeau: Entering zone poknowledge (202:0)
[Debug] [WORLD__ZONE] [5] [poknowledge] Broadcasting a world time update
[Debug] [WORLD__ZONE] [5] [poknowledge] Setting to 'poknowledge' (202:0)
[Debug] [WORLD__CLIENT] Rykeau: Sending client to zone poknowledge (202:0) at xxx.xxx.xxx.xxx:7004
[Debug] [WORLD__CLIENT] Rykeau: Client disconnected (not active in process)

If anybody can point me to an older database I'd like to try that. Unfortunately I'm not able to locate anything but the 1751 database on the PEQ site.

Feeling lost and frustrated... <sigh>

[trevius]

Those errors in your log there are all normal. They are just logging packets that we don't currently have handling for, and aren't really needed (at least not at this time).

[Shiny151]

Rykeau; if you're still looking for an older database I believe I can hook you up. I have 1667 on my server somewhere. PM me and I'll link you over the weekend.

[freakydeekey]

ok i just did my first ever install of a server, everything went through fine, few errors which i was able to fix but i am having the same problem with the fact that accounts will not be created in my DB. I looked in my DB and manually added the lsaccount_id # manually and i was then able to connect (noone else can though cause i have to do it manual so this needs fixed still) but once i create a charachter and try to log in, it sends info to the zone then disconnects, no error. Im going to recreate it all and do screenshots in a min.

Any Idea why it will not create ls accounts and why it wont connect to zone server?

[lerxst2112]

Look in the logs. They will usually tell you exactly why something isn't working.