Jump to content
For maintenance and updates, the community will be offline on 31 December 2022 ×
  • 0

Connection error after adding Cheque System


narcisxb

Question

Hi! I have the following issue after adding Cheque System. 

Every time I try to log in with a wrong user or password I get "Wrong user or pswd" error BUT when I actually log in with my account (any correct account) I get "Error while connecting to the server".

Client syserr is empty.

Server syserr:

SYSERR: Sep 18 17:59:09 :: pid_init: 
Start of pid: 961

SYSERR: Sep 18 17:59:11 :: Boot: shop table size error
SYSERR: Sep 18 17:59:11 :: SpawnEventHelper: cannot get map base position 1
SYSERR: Sep 18 17:59:11 :: SpawnEventHelper: cannot get map base position 3
SYSERR: Sep 18 17:59:11 :: SpawnEventHelper: cannot get map base position 23
SYSERR: Sep 18 17:59:11 :: SpawnEventHelper: cannot get map base position 43
SYSERR: Sep 18 17:59:11 :: pid_deinit: 
End of pid

"Boot: shop table size error" seems to come from "tables.h" in source after adding wons in there. But if I remove that snippet of code I get connection refused in my console.

Promblem code seems to be here:

typedef struct SShopItemTable
{
	DWORD		vnum;
	BYTE		count;

    TItemPos	pos;			// PC 상점에만 이용
	DWORD		price;	// PC, shop_table_ex.txt 상점에만 이용
	#ifdef ENABLE_CHEQUE_SYSTEM
	DWORD		cheque;
	#endif
	BYTE		display_pos; // PC, shop_table_ex.txt 상점에만 이용, 보일 위치.
} TShopItemTable;

Pls help. xD 

EDIT: Main problem seems to be here:

db syserr:

SYSERR: Sep 18 20:02:37 :: pid_init: 
Start of pid: 932

SYSERR: Sep 18 20:02:37 :: Start: TABLE_POSTFIX not configured use default
SYSERR: Sep 18 20:02:51 :: Process: FDWATCH: peer null in event: ident 23
SYSERR: Sep 18 20:02:51 :: Process: FDWATCH: peer null in event: ident 24
SYSERR: Sep 18 20:02:51 :: Process: FDWATCH: peer null in event: ident 21
SYSERR: Sep 18 20:02:52 :: Process: FDWATCH: peer null in event: ident 22

db syslog:

...
Sep 18 20:02:48 :: HEADER_GD_SET_EVENT_FLAG : No Changed CClientmanager::SetEventFlag(oxevent_status 0) 
Sep 18 20:02:50 :: HEADER_GD_SET_EVENT_FLAG : No Changed CClientmanager::SetEventFlag(oxevent_status 0) 
Sep 18 20:02:50 :: HEADER_GD_SET_EVENT_FLAG : No Changed CClientmanager::SetEventFlag(oxevent_status 0) 
Sep 18 20:02:50 :: HEADER_GD_SET_EVENT_FLAG : No Changed CClientmanager::SetEventFlag(oxevent_status 0) 
Sep 18 20:02:51 :: HEADER_GD_SET_EVENT_FLAG : No Changed CClientmanager::SetEventFlag(oxevent_status 0) 
Sep 18 20:02:51 :: Connection closed. (host: 127.0.0.1)
Sep 18 20:02:51 :: ItemIDRange: returned. 60000001 ~ 70000000
Sep 18 20:02:51 :: ItemIDRange: Build: 60000001 ~ 70000000 start:60000001
SYSERR: Sep 18 20:02:51 :: Process: FDWATCH: peer null in event: ident 23
Sep 18 20:02:51 :: Connection closed. (host: 127.0.0.1)
Sep 18 20:02:51 :: ItemIDRange: returned. 80000001 ~ 90000000
Sep 18 20:02:51 :: ItemIDRange: Build: 80000001 ~ 90000000 start:80000018
SYSERR: Sep 18 20:02:51 :: Process: FDWATCH: peer null in event: ident 24
Sep 18 20:02:51 :: Connection closed. (host: 127.0.0.1)
Sep 18 20:02:51 :: ItemIDRange: returned. 40000001 ~ 50000000
Sep 18 20:02:51 :: ItemIDRange: Build: 40000001 ~ 50000000 start:40000160
SYSERR: Sep 18 20:02:51 :: Process: FDWATCH: peer null in event: ident 21
Sep 18 20:02:52 :: Connection closed. (host: 127.0.0.1)
Sep 18 20:02:52 :: ItemIDRange: returned. 20000001 ~ 30000000
Sep 18 20:02:52 :: ItemIDRange: Build: 20000001 ~ 30000000 start:20000339
SYSERR: Sep 18 20:02:52 :: Process: FDWATCH: peer null in event: ident 22
Sep 18 20:02:52 :: [      150] return 0/0/0 async 0/0/0
Sep 18 20:02:57 :: [      200] return 0/0/0 async 0/0/0
Sep 18 20:03:02 :: [      250] return 0/0/0 async 0/0/0
Sep 18 20:03:05 :: AUTH_LOGIN id(1) login(admin) social_id(1234567) login_key(156667313), client_key(793739589 212857159 1929999058 1901163518)
Sep 18 20:03:07 :: [      300] return 0/0/0 async 0/0/0
Sep 18 20:03:12 :: [      350] return 0/0/0 async 0/0/0
Sep 18 20:03:17 :: [      400] return 0/0/0 async 0/0/0
...

Ideeas?

Edited by narcisxb
Link to comment
Share on other sites

  • Answers 2
  • Created
  • Last Reply

Top Posters For This Question

Top Posters For This Question

2 answers to this question

Recommended Posts

  • 0

You probably made a wrong addition somewhere. I do not know exactly.

Boot: shop table size error also means:
This error will occur if more than 40 items have been added to a 40-slot market. If you did something like this, fix it back.

Link to comment
Share on other sites

  • 0
19 hours ago, blaxis said:

You probably made a wrong addition somewhere. I do not know exactly.

Boot: shop table size error also means:
This error will occur if more than 40 items have been added to a 40-slot market. If you did something like this, fix it back.

Well yeah, but where... thats why I asked. Also there s no way more than 40 items have been aded to a 40 slot market. (tbh I really doubt that s where that error stems from, I think it s more like if you overflow a variable type; like you ve got an short and you try to store 33000 something in it).

Need helps pls.

Edited by narcisxb
Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now


  • Activity

    1. 992

      [40250] Reference Serverfile + Client + Src [15 Available Languages]

    2. 3

      Biologist Manager (C++ & LUA)

    3. 3

      Visual studio 2022 compiling issue

    4. 63

      Metin2 | Mount System Renewal

    5. 58

      Metin2 2004 Beta Client

    6. 0

      🔥Paradise2 PVP SERVER GLOBAL!! EN-ES-PT 🕐📢Apertura 11 de diciembre 21 horas de España!

    7. 0

      Please help here ( Sush system problem )

  • Recently Browsing

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

Important Information

Terms of Use / Privacy Policy / Guidelines / 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.