Jump to content

Recommended Posts

Posted

SYSERR: Apr 20 15:11:53 :: ChildLoop: AsyncSQL: query failed: Out of range value for column 'part_main' at row 1 (query: UPDATE player SET job = 2, voice = 0, dir = 0, x = 959759, y = 272556, z = 0, map_index = 41, exit_x = 959759, exit_y = 272556, exit_map_index = 41, hp = -26550, mp = 5162, stamina = 1170, random_hp = 3876, random_sp = 2142, playtime = 14483, level = 103, level_step = 1, st = 5, ht = 74, dx = 119, iq = 125, gold = 366409249, exp = 377371262, stat_point = 0, skill_point = 102, sub_skill_point = 81, stat_reset_count = 0, ip = '33.33.112.2', part_main = 41030, part_hair = 0, last_play = NOW(), skill_group = 2, alignment = 15, horse_level = 21, horse_riding = 0, horse_hp = 35, horse_hp_droptime = 1398186740, horse_stamina = 120, horse_skill_point = 0, skill_level = '0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000

 

SYSERR: Apr 20 15:12:35 :: ChildLoop: AsyncSQL: query failed: Incorrect string value: 'xF1as_ba...' for column 'szName' at row 1 (query: REPLACE INTO quest (dwPID, szName, szState, lValue) VALUES(2320, 'arañas_bajar_ala_primera_planta', '__status', 1290640410) errno: 1366) 

 

Gracias de antemano.

Posted

La de part_main ya lo solucione pero este sigue..

SYSERR: Apr 20 15:12:35 :: ChildLoop: AsyncSQL: query failed: Incorrect string value: 'xF1as_ba...' for column 'szName' at row 1 (query: REPLACE INTO quest (dwPID, szName, szState, lValue) VALUES(2320, 'arañas_bajar_ala_primera_planta', '__status', 1290640410) errno: 1366)

  • Dilong locked this topic
Guest
This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...

Important Information

This site uses cookies to enhance your browsing experience and provide relevant content. By continuing to browse, you agree to our We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue. and Terms of Use. For more information on how we protect your data, please check our Privacy Policy.