Welcome!

Join our community of MMO enthusiasts and game developers! By registering, you'll gain access to discussions on the latest developments in MMO server files and collaborate with like-minded individuals. Join us today and unlock the potential of MMO server development!

Join Today!

[DB Error] DBWorkerThreadID @PB_INIT Failed!

Newbie Spellweaver
Joined
Mar 3, 2013
Messages
14
Reaction score
0
Hi I got this problem .... how to fix this ?

Log Server :

10-25 19:16:31|[Notify] elapsed time after turn on !! 0Day 15h:40m:11s 10-25 19:16:31|Log Server Start


10-25 19:16:31|CVMem::AllocVMem VirtualAlloc() success, TypeSize[ 1552] PoolCnt[10002] CommitSize[15523840] vectorSize[1] Address Range(0x7E3C0000 ~ 0x7F28E000)
10-25 19:16:31| [Notify] CLogGlobal::InitServerSocket# Starting...
10-25 19:16:31|CAtumDBManager::AtumDBWorker_ DWWorkerThread, ThreadID( 4536, 0x11B8)
10-25 19:16:31|CAtumDBManager::AtumDBWorker_ DWWorkerThread, ThreadID( 4124, 0x101C)
10-25 19:16:32|CAtumDBManager::AtumDBWorker_ DWWorkerThread, ThreadID( 1684, 0x694)
10-25 19:16:32|CAtumDBManager::AtumDBWorker_ DWWorkerThread, ThreadID( 4416, 0x1140)
10-25 19:16:32|CAtumDBManager::AtumDBWorker_ DWWorkerThread, ThreadID( 3504, 0xDB0)
10-25 19:16:32|CAtumDBManager::AtumDBWorker_ DWWorkerThread, ThreadID( 2664, 0xA68)
10-25 19:16:32|CAtumDBManager::AtumDBWorker_ DWWorkerThread, ThreadID( 4552, 0x11C8)
10-25 19:16:32|CAtumDBManager::AtumDBWorker_ DWWorkerThread, ThreadID( 4948, 0x1354)
10-25 19:16:32|CAtumDBManager::AtumDBWorker_ DWWorkerThread, ThreadID( 2268, 0x8DC)
10-25 19:16:32|CAtumDBManager::AtumDBWorker_ DWWorkerThread, ThreadID( 4972, 0x136C)
10-25 19:16:32|CAtumDBManager::AtumDBWorker_ DWWorkerThread, ThreadID( 3664, 0xE50)
10-25 19:16:33|CAtumDBManager::AtumDBWorker_ DWWorkerThread, ThreadID( 4080, 0xFF0)
10-25 19:16:33|CAtumDBManager::AtumDBWorker_ DWWorkerThread, ThreadID( 1668, 0x684)
10-25 19:16:33|CAtumDBManager::AtumDBWorker_ DWWorkerThread, ThreadID( 3208, 0xC88)
10-25 19:16:33|CAtumDBManager::AtumDBWorker_ DWWorkerThread, ThreadID( 4740, 0x1284)
10-25 19:16:33|######################## Server IOCPInit ########################
10-25 19:16:33| [Notify] CLogGlobal::InitServerSocket# Started
10-25 19:16:33|CIOCP::Worker_ WorkerThread, ThreadID( 1688, 0x698)
10-25 19:16:33|CIOCP::Worker_ WorkerThread, ThreadID( 3116, 0xC2C)
10-25 19:16:33|CIOCP::Writer_ WriterThread, ThreadID( 2500, 0x9C4)
10-25 19:16:33|CIOCP::Listen_ ListenerThread, ThreadID( 776, 0x308)
10-25 19:16:33|CIOCP::Worker_ WorkerThread, ThreadID( 4868, 0x1304)
10-25 19:16:33|CIOCP::Worker_ WorkerThread, ThreadID( 3996, 0xF9C)
10-25 19:16:33|CIOCP::Writer_ WriterThread, ThreadID( 1116, 0x45C)
10-25 19:16:33|Socket Connect SocketIndex[ 0] PeerIP[ 10.240.0.3] Port[52754]
10-25 19:16:33|Socket Connect SocketIndex[ 1] PeerIP[ 10.240.0.3] Port[52756]
10-25 19:16:33|Socket Connect SocketIndex[ 2] PeerIP[ 10.240.0.3] Port[52757]
10-25 19:16:33|Socket Connect SocketIndex[ 3] PeerIP[ 10.240.0.3] Port[52758]
10-25 19:16:33|Socket Connect SocketIndex[ 4] PeerIP[ 10.240.0.3] Port[52759]
10-25 19:16:33|Socket Connect SocketIndex[ 5] PeerIP[ 10.240.0.3] Port[52760]
10-25 19:16:33|Socket Connect SocketIndex[ 6] PeerIP[ 10.240.0.3] Port[52761]
10-25 19:16:33|Socket Connect SocketIndex[ 7] PeerIP[ 10.240.0.3] Port[52755]
10-25 19:16:33|Socket Connect SocketIndex[ 8] PeerIP[ 10.240.0.3] Port[52752]
10-25 19:16:33|Socket Connect SocketIndex[ 9] PeerIP[ 10.240.0.3] Port[52753]
10-25 19:16:39| [Notify] OnReceived T_FL_LOG_START_FIELD_SERVER !
10-25 19:16:39|[DB Error] DBWorkerThreadID( 4416) hstmt(0xF7C038): @PB_INIT Failed!
 
[emoji848]
Legend
Joined
Dec 3, 2011
Messages
2,232
Reaction score
1,518
create DB neme PB?

wtf? no...

Contents of PB_INIT
Code:
ALTER PROCEDURE [dbo].[PB_INIT]
	@nGameID int		-- GameSvr ID
AS
-- 2007-01-29 by cmkwon, ServerGroupID ÃʱâÈ­
UPDATE atum2_db_account.dbo.td_account 
SET ConnectingServerGroupID = 0
WHERE ConnectingServerGroupID = @nGameID

This looks like a cleanup procedure for the connected game server groups on td_account once a server connects. The server uses his server group (as configured in global.cfg) as parameter to execute this procedure. Looks like this procedure aims to make sure no accounts are connected to the server group already before the server launches and uses them.

So an idea would be double checking the server group stuff in your global.cfg
 
Upvote 0
Back
Top