I will Pay 100us$ to change the OS to Win2k3 SP1.. I hope it work!.:thumbup:
Printable View
I will Pay 100us$ to change the OS to Win2k3 SP1.. I hope it work!.:thumbup:
Install Windows Server 2003 SP 1, free of problems here normally use.
already installed Windows Server 2003 SP 1 and I'm getting this error.
now trying Windows Server 2003 (Without SP1)
i try them all and i have the problem again...
we dont have a slolution for this?
If you dont want to have that problem just use win2k8 with sp2. All updates are needed cuz of security reasons. And if you dont have win2k3 with sp2 you dont have all the security updates...
As far as i see (maybe i am wrong) it's about SP2 no matter what you use XP 32/64 bit,Win2k3 ... or maybe it has nothing to do with OS you use ... i have XP64 bit with SP2 and GS closes exactly after 8 hours of running, it's fucking anoying. Now i don't know if you have to run some code in the GS, or maybe it has nothing to do with it but someone can put a reliable working solution for this ?? I don't think is a data base related problem, i don't see how, it'a about connection from the server to any PC wich is connected on the server and reverse ...
one question. will the SP3 solve this problem?!
I use windows 2003 server sp1 and got the same problem running the querys, some new fixes for this?
Version: 1.05 + Season 4 SCF
This really doesn't have anything to do with DB.
Looks like either Webzen failed at proper coding the IOCP or someone fuc*ed the server with their ub3r coding skills AND only after that it could lead to generate a failure in the DB or anywhere else and then the socket is terminated.
So the only way to fix this is to search for all the places where the sockets are being closed and there just disable the output and it won't bother you, but the problem probably is that either the player closed the client by forcing to terminate the process or there was a failure in the communication for example a problem sending data or receiving or some parts of packet were lost and so on...
OMG. This post is from 2008, and this query and winsock modificactions dont work to fix that problem.
The realy fix : install win 2003 sp1
Anyone knows how to Fix without installing Windows Server 2003 Sp1 ?
If so, please reply.
Thanks :)