[Help] ConnectServer Error. goeh's files.

Status
Not open for further replies.
Newbie Spellweaver
Joined
Feb 17, 2004
Messages
40
Reaction score
0
Hello Everyone.

sometimes i get this error in the CS:
Error Thread : GetQueueCompletionStatus() (183, The network connection was aborted by the local system.


but the CS is still working and ppls can still connect to the server.

and sometimes it also DC everyone from the server and no one can connect again.
(i'm still stay connected)

NOTE:
i have router.
 
I got the same problem as you ColdAxe. Have you already solved your inssue?


PS: I'vent got a router.
 
Last edited:
Upvote 0
I have this problem also. With CZF ConnectServer i've obtained same bug (CZF writes different text, but problem is the same). Dunno, how to fix this. '(
 
Upvote 0
I have this problem also. With CZF ConnectServer i've obtained same bug (CZF writes different text, but problem is the same). Dunno, how to fix this. '(

Well, man, I'll try to use CzF ConnectServer, but I have some duties now and can't test it at all. As soon as I get back, I'll try to solve this f*cking problem. Then I'll put the solution here for further searches.

If you get it solved, please, post.


Bye
 
Upvote 0
i am a victim of this problem also! CZF or normal CS, they both crash.. czf has diff error but same simptoms.. i really have NO IDEA what can be causing thing.. someone must help us with a solution if he knows. and i got this error on any version i use

thx
 
Upvote 0
so no one in this whole forum had this problem and fixed it? this is already annyoing.. here's what i've tried to do to stop this error: changed 3 mu versions, changed sql, different firewalls, different connectservers, formating pc 2 times, changing no-ip domain.. im out of ideas.. WHAT IN THE HELL IS CAUSING THIS PROBLEM!!!! IM FUCKED UP ALREADY WITH IT!!!!!!!!!!!!:mad_1::mad_1::mad_1::mad_1:
 
Upvote 0
so no one in this whole forum had this problem and fixed it? this is already annyoing.. here's what i've tried to do to stop this error: changed 3 mu versions, changed sql, different firewalls, different connectservers, formating pc 2 times, changing no-ip domain.. im out of ideas.. WHAT IN THE HELL IS CAUSING THIS PROBLEM!!!! IM FUCKED UP ALREADY WITH IT!!!!!!!!!!!!:mad_1::mad_1::mad_1::mad_1:


Which Windows are you using? I'll try to use XP in my dedicated, cuz with 2003, this problem is still on.
 
Upvote 0
Well, i think it is not server problem. We tried to do all possible things, but nothing. We think, it can be client problem (we'll check launcher and main).

We haven't this problem after server restart, only after 10-12 hours. And this problem has certain people (in random order), not everyone (we think after long AFK, people will have this problem after relogin).

So if it was server problem, all of our players would have this problem always after relogin.

I'll start my tests today.
 
Upvote 0
Nope, it isn't the server files, it's in the windows, some configuration. I haven't got it before, but when I change my dedicated server, it appears. Let's continue seaching our solution, guys.
 
Upvote 0
im using windows vista.. but that's not the problem because i had the server like 2 weeks, then i formatted pc.. the problem apeared.. i formatted again, same problem.. the solution i found that seems to keep my server alive is this: use czf connectserver and enable autorestart at connectserver every 20 minutes..

MuServerStartup

Example:

[needrestart]
v0v=NO
v1v=NO
v2v=NO
v3v=YES
v4v=NO
v5v=NO
v6v=NO
v7v=NO
v8v=NO
v9v=NO
[main]
enableautorestart=1
restartinterval=20
ipadd=127.0.0.1

v3v is the CS, hope this helps

but im still thinking, win2003 and win vista are using the same kernel, but i bet other had problems on XP also.. so i really dont think it's windows problem.. few q to you guys.. did you use ? maybe it's their service problem.. or what bios are you using? im using AMI bios
 
Upvote 0
im using windows vista.. but that's not the problem because i had the server like 2 weeks, then i formatted pc.. the problem apeared.. i formatted again, same problem.. the solution i found that seems to keep my server alive is this: use czf connectserver and enable autorestart at connectserver every 20 minutes..

MuServerStartup

Example:



v3v is the CS, hope this helps

but im still thinking, win2003 and win vista are using the same kernel, but i bet other had problems on XP also.. so i really dont think it's windows problem.. few q to you guys.. did you use ? maybe it's their service problem.. or what bios are you using? im using AMI bios



I did tried to use MuStartUp, but it fixes the ConnectServer's error, but the message "Socket_invalid" in GameServer.exe still appears. :/ And disconnect users in server.
 
Upvote 0
I did tried to use MuStartUp, but it fixes the ConnectServer's error, but the message "Socket_invalid" in GameServer.exe still appears. :/ And disconnect users in server.

i really wonder what can be causing this problem, and none of the "big" muonline developers are willing to help
 
Upvote 0
Nope, it isn't the server files, it's in the windows, some configuration. I haven't got it before, but when I change my dedicated server, it appears. Let's continue seaching our solution, guys.

Maybe you changed your SQL Server version? Or maybe we have troubles with System DSN? You created same config at your new server? What OS do you have? I'll try SQL 2005 this weekend (now i'm busy with my job).
Changing IP in main.exe not helped me... Other launcher versions too.

I have the same problem, but the difference is that no one is disconnected from server, they can't enter in game, after they logged off ("You are already connected"). Changing stored procedures not helped! Well, guides for this problem solution really sucks for now... =/
 
Upvote 0
Well, a friend of a friend of mine, told me that I must uninstall Service 2003 Server Pack. He told me that it must solve my problem. Well, it has a kinda sense, because before changing from DataCenter, I haven't got this problem, cuz I have never updated Windows before, but now, I updated it and the fucking problem appeared.

This problem is in Windows, not in MuServers, it's something like in its setting, in Winsock, which is responsible by the Connections.
 
Upvote 0
Well, a friend of a friend of mine, told me that I must uninstall Service 2003 Server Pack. He told me that it must solve my problem. Well, it has a kinda sense, because before changing from DataCenter, I haven't got this problem, cuz I have never updated Windows before, but now, I updated it and the fucking problem appeared.

This problem is in Windows, not in MuServers, it's something like in its setting, in Winsock, which is responsible by the Connections.

I have Windows 2000. The same problem. Maybe i' ll setup WinXP now (without SP2). It's kinda good.
 
Upvote 0
Status
Not open for further replies.
Back