Jump to content
  • 0

[help] can't see characters


Question

Posted

Hello,

I have helbound server running on COEP and I have problem with characters on accounts.

When I log in to server, I can't see any char, when I trying to make new, I got message "Name alredy exist" (I tried many names)

When I look to db, I see that characters are created.

In CacheD server I have this:

07/27/2011 20:35:17.572, Error sql: EXEC lin_GetUserDataByCharId 1 (0)
07/27/2011 20:35:17.573, Error 42S22:[Microsoft][sql Native Client][sql Server]Invalid column name 's37'.
07/27/2011 20:35:17.573, [.\User.cpp][4243] undefined (or unregistered) char Id[1]
07/27/2011 20:35:17.573, --- call stack ---
07/27/2011 20:35:17.573, [0] void IOThread_common(void *arglist)
07/27/2011 20:35:17.573, [1] static bool CreateCharacterPacket(CSocket* pSocket, const unsigned char* packet)
07/27/2011 20:35:17.573, [2] CUserSP CUserDb::GetUser(int nUserId, bool bLoadIfNotExist)
07/27/2011 20:35:37.226, Error sql: EXEC lin_GetUserDataByCharId 2 (0)
07/27/2011 20:35:37.226, Error 42S22:[Microsoft][sql Native Client][sql Server]Invalid column name 's37'.
07/27/2011 20:35:37.226, [.\User.cpp][4243] undefined (or unregistered) char Id[2]
07/27/2011 20:35:37.226, --- call stack ---
07/27/2011 20:35:37.226, [0] void IOThread_common(void *arglist)
07/27/2011 20:35:37.226, [1] static bool CreateCharacterPacket(CSocket* pSocket, const unsigned char* packet)
07/27/2011 20:35:37.226, [2] CUserSP CUserDb::GetUser(int nUserId, bool bLoadIfNotExist)
07/27/2011 20:35:44.623, Error sql: EXEC lin_GetUserDataByCharId 3 (0)
07/27/2011 20:35:44.623, Error 42S22:[Microsoft][sql Native Client][sql Server]Invalid column name 's37'.
07/27/2011 20:35:44.623, [.\User.cpp][4243] undefined (or unregistered) char Id[3]
07/27/2011 20:35:44.623, --- call stack ---

 

Anybody know, what I need to change to make it correct? Thx for advices.

2 answers to this question

Recommended Posts

  • 0
Posted

had something like that on off server. restarted and i was able to see chars again.

hmm restart didn't help, I think it could be some wrong sql, but I don't know, because it's downloaded from coep and that should be ok, I know many servers on coep which works ok and they didn't change anything...

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


  • Posts

    • Added: Server monitoring has been added to the protection dashboard, available for Premium+ plans. Each entry displays: Account — game login. HWID — hardware ID. GSID — the game server the entry belongs to. IP — the player's address. Country — determined by IP, with flag and name. Useful for SEO promotion, do you know where more players come from Status — "Banned" or "OK". Extra windows — how many additional windows are allowed for this HWID beyond the global limit. Last seen — time of last activity.   At the top — a summary: total entries, number banned, time of the last report, and an Online/Offline indicator (based on how fresh the data from the protection is).   Filters and search Search by account, HWID, or IP. Country — select from countries actually present in the data. Game server (GS) — filter by GSID. Period — by last activity date (from / to). Banned only — quick filter for violators. Grouping — collapse data by HWID, IP, or account: one row per key with counts of accounts/HWIDs/IPs and number of entries. Handy for catching multi-accounters (many accounts from one HWID) and suspicious IPs.   Ban / Unban — banning by HWID blocks all accounts on that hardware. The protection will pick up the command within a minute; until applied, a "Pending…" status is shown. Grant windows — set additional windows (+N) for a specific HWID via a convenient selector. Single token per account to link the protection with the dashboard: Generate / Reissue token in one click. Show token — view the current value at any time. The token is stored encrypted. Don't share it with anyone — if compromised, simply reissue it and the old one stops working immediately. In the protection config, you can enable monitoring, insert the token, and change how often data is sent to the protection dashboard.
    • Dear BarbieQ server. https://www.mediafire.com/file/lfimqw9c63xd6l5/L2DAMAGE_MUST_BE_STOPPED_in_L2_Server_support_%26_problems_-_Page_1_of_-_l2topzone.com.pdf/file
  • Topics

×
×
  • Create New...

Important Information

This community uses essential cookies to function properly. Non-essential cookies and third-party services are used only with your consent. Read our Privacy Policy and 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..