Problems with any Episode beyond 2.2

Results 1 to 4 of 4
  1. #1
    Registered Malazag is offline
    MemberRank
    Jun 2012 Join Date
    9Posts

    Problems with any Episode beyond 2.2

    Problems with any Episode beyond 2.2
    Hello!

    I've been trying all kinds of Ace Online Servers / Clients (I even tried to compile binaries from the EP 3.5 and 4.2 sources), but I allways struggled very much with the Pre- and Log-Server failing to connect to the DB.

    For some strange reason I somehow managed to get a EP 2.2 Server running, but nothing else Every other episode allways has the same "CPreIOCP::IOCPInit_"-Error. I've triple checked settings for:

    -ODBCs
    -SQL Server TCP/IP
    -Global.cfg
    -I tried encrypted and not-encrypted logins
    -SQL server has active mixed authentication

    ---

    In some thread I found a guy with a similar problem and @Future provided various possible solutions for this problem (http://forum.ragezone.com/f908/help-...ng-db-1152897/), but none of these work for me.

    What bugs me the most is, if I try to connect through the SQL Management studio, and just use the IP instead of "H2431283\SQLEXPRESS" I cannot connect. Which is strange, since the EP2.2 Pre- and Logserver work fine. I even played the first few missions of the FreeSKA just for testing. I've been trying around for over 4 days now, but It doesn't seem like I make any progress.

    I tried EP 3.3, EP 3.5 and EP 4.2, all of which I could find in one way or another in these forums. Neither did work.

    ---

    I can provide any logs if needed, but maybe someone would have had a similar problem before?

    ---

    Example of the Preserver log for a EP 3.5 preserver (with matching .cfg's):

    05-10 02:28:05|[Notify] elapsed time after turn on !! 0Day 3h:54m:34s
    05-10 02:28:05|Pre Server Start
    05-10 02:28:05|CVMem::AllocVMem VirtualAlloc() success, TypeSize[ 1508] PoolCnt[ 100] CommitSize[ 151552] vectorSize[1] Address Range(0x7FE80000 ~ 0x7FEA5000)
    05-10 02:28:05|CVMem::AllocVMem VirtualAlloc() success, TypeSize[ 1528] PoolCnt[ 101] CommitSize[ 155648] vectorSize[1] Address Range(0x7FE50000 ~ 0x7FE76000)
    05-10 02:28:05|CVMem::AllocVMem VirtualAlloc() success, TypeSize[ 1552] PoolCnt[15001] CommitSize[23281664] vectorSize[1] Address Range(0x7E810000 ~ 0x7FE44000)
    05-10 02:28:05| ServerGroup: Dragon, Enable(1) MGameServerID(10061)
    05-10 02:28:05| ServerGroup: Arena, Enable(0) MGameServerID(10062)
    05-10 02:28:06| [Notify] CPreGlobal::OnPacketNotifyOfSPToMPWinSoc# 10000 CWinSocket::WS_CONNECTED wParam(0)
    05-10 02:28:06| [Notify] CPreGlobal::InitServerSocket# Starting...
    05-10 02:28:06| [Notify] CPreIOCP::IOCPInit# 10000
    05-10 02:28:06| [Notify] CPreIOCP::IOCPInit# 11000 updated version files !
    05-10 02:28:06| [Notify] CPreIOCP::IOCPInit# 12000 arranged version list !
    05-10 02:28:23|[DB Error] fail to connect DBServer(CPreIOCP::IOCPInit_) !! 85.214.129.61,1433 atum2_db_account atum callweb
    05-10 02:28:26|[Error] PreServer IOCPInit Error
    05-10 02:28:27|[ERROR] CPreGlobal::OnPacketNotifyOfSPToMPWinSoc_ InitServerSocket_ error !!05-10 02:28:28| [Notify] CPreGlobal::EndServerSocket#
    05-10 02:28:28|CGlobalGameServer::EndServerSocket_1
    05-10 02:28:28|######################## Server IOCPClean ########################

    05-10 02:28:28|[Notify] CVMem::FreeAllVMem_ TypeSize[ 1508] TotalCommitedObjCnts( 100) CurrentObjCnts( 100)
    05-10 02:28:28|[Notify] CVMem::FreeAllVMem_ TypeSize[ 1528] TotalCommitedObjCnts( 101) CurrentObjCnts( 101)
    05-10 02:28:28|[Notify] CVMem::FreeAllVMem_ TypeSize[ 1552] TotalCommitedObjCnts( 15001) CurrentObjCnts( 15001)
    05-10 02:28:28|Pre Server End


    05-10 02:28:28|CGlobalGameServer::EndServerSocket_1
    I'm sorry that I have to ask for help :(


  2. #2
    Member vinleprince is offline
    MemberRank
    Feb 2015 Join Date
    45Posts

    Re: Problems with any Episode beyond 2.2

    05-10 02:28:23|[DB Error] fail to connect DBServer(CPreIOCP::IOCPInit_) !! 85.214.129.61,1433 atum2_db_account atum callweb

    your have issue with db connect right? so try check sql server setting

    1. sql server configuration / sql server network / TCP IP / IP Addresss's tab / fix it if you using wrong ip port (
    85.214.129.61 / 1433) and restart sql server.
    2. try login sql server management with that account atum password callweb (check permssion setting using admin or not)
    3. check server config global. you put same db ip/port/user/password or not. some source using XOR password.




  3. #3
    Problems with any Episode beyond 2.2 Future is offline
    LegendRank
    Dec 2011 Join Date
    2,276Posts

    Re: Problems with any Episode beyond 2.2

    As you found my posts already, I can pretty much only repeat myself.

    Try connecting to the SQL Server via the SQL Server Management Studio, not the game servers, using the exact same IP, User ID and Password you've set in the config files. If that doesn't connect, there is no chance your game servers will. + SSMS' error reporting is a ton better than masang's. You prolly get some useful information out of that.

    Otherwise, if you know how to, you can obviously also extend the error logging on server connection attempts. ODBC API error information can be read and parsed using SQLGetDiagRec, passing the respective connection handles.


    Quote Originally Posted by A Wise Man
    P-Servers are NOT dead. Bugs need squishing. Quests need fixing. Unfortunately, majority of people don't know the difference between a computer and a toaster so...

  4. #4
    Registered Malazag is offline
    MemberRank
    Jun 2012 Join Date
    9Posts

    Re: Problems with any Episode beyond 2.2

    Quote Originally Posted by Future View Post
    As you found my posts already, I can pretty much only repeat myself.

    Try connecting to the SQL Server via the SQL Server Management Studio, not the game servers, using the exact same IP, User ID and Password you've set in the config files. If that doesn't connect, there is no chance your game servers will. + SSMS' error reporting is a ton better than masang's. You prolly get some useful information out of that.

    Otherwise, if you know how to, you can obviously also extend the error logging on server connection attempts. ODBC API error information can be read and parsed using SQLGetDiagRec, passing the respective connection handles.
    After a lot of searching and grey hair, I seem to have found the issue:

    In the SQL Configuration Manager, under IPAll there was a wrong (?) dynamic port (1399), for reasons I don't know. After I changed this to 1433 too, I can connect to the server through SSMS by entering the IP. I'll try around and report back - but I think I might have gotten a step further.

    I still cannot quite understand how and why EP2.2 still worked for some reason.



Advertisement