Login crashes world.exe

[wwunate]

After setting up a server using the 3.1 installer with all the defaults (db, public login, etc) I can start the world and launcher. From there I can see the server as ready to be logged into on the public site. When I connect to that server, I get the annoying windows error "World.exe has encountered an error ... blah blah blah"

Here's the error from event viewer:
Event Type: Error
Event Source: Application Error
Event Category: None
Event ID: 1000
Date: 4/19/2006
Time: 9:40:59 AM
User: N/A
Computer: DOC
Description:
Faulting application world.exe, version 0.0.0.0, faulting module ntdll.dll, version 5.1.2600.2180, fault address 0x00018fea.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 41 70 70 6c 69 63 61 74 Applicat
0008: 69 6f 6e 20 46 61 69 6c ion Fail
0010: 75 72 65 20 20 77 6f 72 ure wor
0018: 6c 64 2e 65 78 65 20 30 ld.exe 0
0020: 2e 30 2e 30 2e 30 20 69 .0.0.0 i
0028: 6e 20 6e 74 64 6c 6c 2e n ntdll.
0030: 64 6c 6c 20 35 2e 31 2e dll 5.1.
0038: 32 36 30 30 2e 32 31 38 2600.218
0040: 30 20 61 74 20 6f 66 66 0 at off
0048: 73 65 74 20 30 30 30 31 set 0001
0050: 38 66 65 61 0d 0a 8fea..

This happens even if I'm trying to login from another box.

Here are my world / eqlauncher startups (this is everything i see up until the login crash):

world.exe
[Status] Using database 'emusp3' at localhost:3306
[Status] EMuShareMem loaded
[Status] Loading items from database: count=54535

eqlauncher.exe
[Debug] Starting Log: logs/eqemu_debug_0328.log
[Debug] [LAUNCHER__INIT] Loading server configuration..
[Debug] [LAUNCHER__INIT] Starting main loop...
[Debug] [NET__WORLD] Connected to World: 127.0.0.1:9000
[Debug] [LAUNCHER__WORLD] World told us to start zone dynamic_01.
[Debug] [LAUNCHER__WORLD] World told us to start zone dynamic_02.
[Debug] [LAUNCHER__WORLD] World told us to start zone dynamic_03.
[Debug] [LAUNCHER__WORLD] World told us to start zone dynamic_04.
[Debug] [LAUNCHER__WORLD] World told us to start zone dynamic_05.
[Debug] [LAUNCHER__ERROR] World told us to start zone dynamic_01, but it is alre
ady running.
[Debug] [LAUNCHER__ERROR] World told us to start zone dynamic_02, but it is alre
ady running.
[Debug] [LAUNCHER__ERROR] World told us to start zone dynamic_03, but it is alre
ady running.
[Debug] [LAUNCHER__ERROR] World told us to start zone dynamic_04, but it is alre
ady running.
[Debug] [LAUNCHER__ERROR] World told us to start zone dynamic_05, but it is alre
ady running.
[Debug] [LAUNCHER__STATUS] Starting zone dynamic_01
[Debug] [LAUNCHER__STATUS] Zone dynamic_01 has been started.
[Debug] [LAUNCHER__STATUS] Waiting 20000 milliseconds before booting the second
zone.
[Debug] [LAUNCHER__STATUS] Starting zone dynamic_02
[Debug] [LAUNCHER__STATUS] Zone dynamic_02 has been started.
[Debug] [LAUNCHER__STATUS] Waiting 2000 milliseconds before booting the next zon
e.
[Debug] [LAUNCHER__STATUS] Starting zone dynamic_03
[Debug] [LAUNCHER__STATUS] Zone dynamic_03 has been started.
[Debug] [LAUNCHER__STATUS] Waiting 2000 milliseconds before booting the next zon
e.
[Debug] [LAUNCHER__STATUS] Starting zone dynamic_04
[Debug] [LAUNCHER__STATUS] Zone dynamic_04 has been started.
[Debug] [LAUNCHER__STATUS] Waiting 2000 milliseconds before booting the next zon
e.
[Debug] [LAUNCHER__STATUS] Starting zone dynamic_05
[Debug] [LAUNCHER__STATUS] Zone dynamic_05 has been started.
[Debug] [LAUNCHER__STATUS] Waiting 2000 milliseconds before booting the next zon
e.

Thanks in advance for all your help.

[sdabbs65]

Originally Posted by wwunate

After setting up a server using the 3.1 installer with all the defaults (db, public login, etc) I can start the world and launcher. From there I can see the server as ready to be logged into on the public site. When I connect to that server, I get the annoying windows error "World.exe has encountered an error ... blah blah blah"

Thanks in advance for all your help.

I found it crashes also when a client trys to connect
and it don't know what version it is.
still troubleshooting the error.

[Doughnutz]

Yeah, I'm looking through the debug logs, we'll see if I come out with anything.

The way it has been working for me is the world.exe will randomly crash actually. I can have people connect and be on just fine, it's just I will have completely random (or it seems to be) crashes.

~Annihilation~

[sdabbs65]

THIS IS THE PROBLEM.

whensomeone trys to log in with the 0.6.1 patch. this happenes.

[Debug] [NET__IDENT_TRACE] 68.32.79.99:3841: Tried patch 6.2_world, and it did n
ot match.
[Debug] [NET__IDENT_TRACE] 68.32.79.99:3841: First opcode 0x1f7b did not match e
xpected 0x2ec9
[Debug] [NET__IDENT_TRACE] 68.32.79.99:3841: Tried patch 6.2_zone, and it did no
t match.
[Debug] [NET__IDENT_TRACE] 68.32.79.99:3841: First opcode 0x1f7b did not match e
xpected 0x4dd0
[Debug] [NET__IDENT_TRACE] 68.32.79.99:3841: Tried patch Titanium_world, and it
did not match.
[Debug] [NET__IDENT_TRACE] 68.32.79.99:3841: First opcode 0x1f7b did not match e
xpected 0x7213
[Debug] [NET__IDENT_TRACE] 68.32.79.99:3841: Tried patch Titanium_zone, and it d
id not match.
[Debug] [NET__IDENT_TRACE] 68.32.79.99:3841: First opcode 0x1f7b did not match e
xpected 0x1f5e
[Debug] [NET__IDENT_TRACE] 68.32.79.99:3841: Tried patch Live_world, and it did
not match.
[Debug] [NET__IDENT_TRACE] 68.32.79.99:3841: First opcode 0x1f7b did not match e
xpected 0x7213
[Debug] [NET__IDENT_TRACE] 68.32.79.99:3841: Tried patch Live_zone, and it did n
ot match.
[Debug] [NET__IDENTIFY] Unable to identify stream from 68.32.79.99:3841, no match found.



<-Then the World Crashes->

[rojadruid]

Originally Posted by sdabbs65

THIS IS THE PROBLEM.

whensomeone trys to log in with the 0.6.1 patch. this happenes.

[Debug] [NET__IDENT_TRACE] 68.32.79.99:3841: Tried patch 6.2_world, and it did n
ot match.
[Debug] [NET__IDENT_TRACE] 68.32.79.99:3841: First opcode 0x1f7b did not match e
xpected 0x2ec9
[Debug] [NET__IDENT_TRACE] 68.32.79.99:3841: Tried patch 6.2_zone, and it did no
t match.
[Debug] [NET__IDENT_TRACE] 68.32.79.99:3841: First opcode 0x1f7b did not match e
xpected 0x4dd0
[Debug] [NET__IDENT_TRACE] 68.32.79.99:3841: Tried patch Titanium_world, and it
did not match.
[Debug] [NET__IDENT_TRACE] 68.32.79.99:3841: First opcode 0x1f7b did not match e
xpected 0x7213
[Debug] [NET__IDENT_TRACE] 68.32.79.99:3841: Tried patch Titanium_zone, and it d
id not match.
[Debug] [NET__IDENT_TRACE] 68.32.79.99:3841: First opcode 0x1f7b did not match e
xpected 0x1f5e
[Debug] [NET__IDENT_TRACE] 68.32.79.99:3841: Tried patch Live_world, and it did
not match.
[Debug] [NET__IDENT_TRACE] 68.32.79.99:3841: First opcode 0x1f7b did not match e
xpected 0x7213
[Debug] [NET__IDENT_TRACE] 68.32.79.99:3841: Tried patch Live_zone, and it did n
ot match.
[Debug] [NET__IDENTIFY] Unable to identify stream from 68.32.79.99:3841, no match found.



<-Then the World Crashes->

Yup thats what I am getting on my server as well. I have been loading up 6.6 when at work so as the server stays up.

[typhoon]

My world has been crashing all day. Every time it crashes I am getting that message Unable to identify stream in the log before it pukes. I tired patching to live to see if I could reproduce it but it makes the live.conf so that didn't crash it. Think I will copy the client off of one of my older discs to confirm what others posted. But it sure sounds like it is the cause of the problem.