Perl Enabled Zone.exe Crashes???

[jdoyle1983]

Okay, the problem I am having is this:

I'm using 5.6 Server, w/ Perl enabled zone.exe. Everything loads just fine (No error outputs). Perl is installed, followed guide and got it al done with no errors. Everytime I try to login to the server, zone.exe crashes. Did I overlook somthing somewhere?

btw, I get the whole xp crash "Zone.exe needs to close....", can get to character select, it's just when I try to zone.

Tried using default.pl, crashes, got a whole bunch of working quests, crashes, and using absolutly no quest, crashes...any ideas???

--EDIT--

World.exe:

[Status] CURRENT_WORLD_VERSION:EQEMu 0.5.6
[Status] Loading variables..
[Status] Loading zones..
[Status] Loading items..
[Status] EMuShareMem loaded
[Status] Loading items from database: count=28633, max id=69173
[Status] ./LoginServer.ini read.
[Status] Loading guild ranks..
[Status] Loading ./addon.ini..
[Status] Loading EQ time of day..
[Status] Reboot zone modes ON
[Status] Deleted 0 stale player corpses from database
[Status] Deleted 0 stale player backups from database
Breaking bards...done
TCP listening on: dhcp024-210-082-102.columbus.rr.com:9000
World server listening on: dhcp024-210-082-102.columbus.rr.com:9000
Connected to LoginServer: eqlogin3.eqemulator.net:5997
40038 New TCP connection: 192.168.0.1:3237
New zoneserver: #1 192.168.0.1:3237
Zoneserver SetConnectInfo: 192.168.0.1:3237: dhcp024-210-082-102.columbus.rr.com
:7995
40929 New TCP connection: 192.168.0.1:3238
40929 New TCP connection: 192.168.0.1:3239
New zoneserver: #2 192.168.0.1:3239
New zoneserver: #3 192.168.0.1:3238
Zoneserver SetConnectInfo: 192.168.0.1:3238: dhcp024-210-082-102.columbus.rr.com
:7998
Zoneserver SetConnectInfo: 192.168.0.1:3239: dhcp024-210-082-102.columbus.rr.com
:7997
41069 New TCP connection: 192.168.0.1:3240
41069 New TCP connection: 192.168.0.1:3241
New zoneserver: #4 192.168.0.1:3241
New zoneserver: #5 192.168.0.1:3240
Zoneserver SetConnectInfo: 192.168.0.1:3240: dhcp024-210-082-102.columbus.rr.com
:7996
Zoneserver SetConnectInfo: 192.168.0.1:3241: dhcp024-210-082-102.columbus.rr.com
:7999
70502 New client from ip: 192.168.0.62 port: 2179
Logged in: FirstLogin LS#52688: jdoyle1983
[Error] Inventory::_PutItem: Invalid slot_id specified (271)
[Error] Warning: Invalid slot_id for item in inventory: acctid=6, item_id=9963,
slot_id=271
[Error] Inventory::_PutItem: Invalid slot_id specified (273)
[Error] Warning: Invalid slot_id for item in inventory: acctid=6, item_id=9962,
slot_id=273
[Error] Inventory::_PutItem: Invalid slot_id specified (279)
[Error] Warning: Invalid slot_id for item in inventory: acctid=6, item_id=9962,
slot_id=279
Received unknown opcode: 0x02ee size:0 bytes
Attempting autobootup of halas (29) for Lich
Zoneserver SetZone: dhcp024-210-082-102.columbus.rr.com:7996 halas (29)
Enter world: Lich: halas (29)
Broadcasting a world time update
Zoneserver SetZone: dhcp024-210-082-102.columbus.rr.com:7996 halas (29)

---HERE IS WHERE ZONE.EXE CRASHES---

Client disconnected
Removing client from ip:192.168.0.62 port:2179
192.168.0.1:3240: TCPConnection::RecvData(): Error: 10054
Removing zoneserver from ip:0.0.0.0 port:0 (dhcp024-210-082-102.columbus.rr.com:
7996)
Hold Zones mode is ON - rebooting lost zone
155264 New TCP connection: 192.168.0.1:3256
New zoneserver: #6 192.168.0.1:3256
Zoneserver SetConnectInfo: 192.168.0.1:3256: dhcp024-210-082-102.columbus.rr.com
:7996


--EDIT (AGAIN)--

Server ran fine w/o perl enabled zone.exe....?? Any ideas?

[jdoyle1983]

Okay, n/m turns out I can't use any characters I had before, creating a new character works fine?? Any ideas why?

[dmal0807]

the character is corrupt we have that problem often on Iron Tower

[RexChaos]

Any work arounds for corrupt characters? If this happens often, does anyone know why?

[jdoyle1983]

Yea, I also have a problem with items shifting around, and disappearing from inventories on zoneing. Could this be part of the same problem???

[Rogean]

Also, pet's are crashing zones on perl compiles. We have already found the problem and it should be fixed next release.