PDA

View Full Version : Cannot Enter World


antheraxx
09-08-2011, 06:23 PM
I am trying to make my own server on axclassic. I can see the server, login, and make a character. but cannot log into the actual zone. all the recommended ports are open (5999, 7000-7014, and a few other ones). This is the error that I am getting

[Debug] [NET__IDENT_TRACE] 65.191.199.45:55004: Tried patch 6.2_zone, and it did
not match.
[Debug] [NET__IDENT_TRACE] 65.191.199.45:55004: First opcode matched 0x4dd0 and
length matched 464
[Debug] [NET__IDENTIFY] Identified stream 65.191.199.45:55004 with signature Tit
anium_world
[Debug] [WORLD__CLIENT] Checking inbound connection 65.191.199.45 against Banned
IPs table
[Debug] [WORLD__CLIENT] Connection 65.191.199.45 PASSED banned IPs check. Proce
ssing connection.
[Debug] [WORLD__CLIENT] forestofpower: Logged in. Mode=(CharSel)
[Debug] [WORLD__CLIENT] forestofpower: LS Account #5003133
[Debug] Unable to convert EQ opcode 0x6a5f to an Application opcode.
[Debug] [WORLD__CLIENT_ERR] forestofpower: Received unknown EQApplicationPacket
[Debug] [WORLD__CLIENT_ERR] [OpCode OP_Unknown (0x6a5f) Size=8]
[Debug] [WORLD__CLIENT_ERR] 0000: 49 66 5a 06 2c 66 5a 06 -
| IfZ.,fZ.
[Debug] Unable to convert EQ opcode 0x6a5f to an Application opcode.
[Debug] [WORLD__CLIENT_ERR] forestofpower: Received unknown EQApplicationPacket
[Debug] [WORLD__CLIENT_ERR] [OpCode OP_Unknown (0x6a5f) Size=8]
[Debug] [WORLD__CLIENT_ERR] 0000: 41 66 5a 06 2c 66 5a 06 -
| AfZ.,fZ.
[Debug] [WORLD__CLIENT] forestofpower: Attempting autobootup of kaladimb (67:0)
[Debug] [WORLD__ZONE] [5] Setting to 'kaladimb' (67:0)
[Debug] [WORLD__CLIENT] forestofpower: Entering zone kaladimb (67:0)
[Debug] [WORLD__ZONE] [5] [kaladimb] Broadcasting a world time update
[Debug] [WORLD__ZONE] [5] [kaladimb] Setting to 'kaladimb' (67:0)
[Debug] [WORLD__CLIENT] forestofpower: Sending client to zone kaladimb (67:0) at
65.191.199.45:7004
[Debug] [WORLD__CLIENT] forestofpower: Client disconnected (not active in proces
s)

any ideas on how to fix this?

lerxst2112
09-08-2011, 07:41 PM
Look at your zone logs. I am not familiar with axclassic, but the symptom you describe is usually a missing sql update.

You'll probably get more specific help in the axclassic forums.