- #Error 10054 proxifier how to
- #Error 10054 proxifier install
- #Error 10054 proxifier rar
- #Error 10054 proxifier software
- #Error 10054 proxifier code
So if you wake up one morning and it's a particularly beautiful day, you'll know we made it. I'll try and bug report this if it occurs again - are CCP interested only in SISI bug reports, or will TQ data suffice? Oddly though the problems with my connection have only occurred whilst the EVE Client has been running. I've been suffering from socket closed errors for some time now (Dec 08 roughly) although I've always assumed it has been my internet connection.
#Error 10054 proxifier rar
Make sure you compress it using zip or rar if the file is bigger than 2MB.Īny information you can provide us via both the logserver log files and your bug report will ensure that we can resolve this issue as quickly as possible.Īh excellent, glad CCP are looking into this. Attach the logserver log file you created in the above steps. In the Reproduction Steps field write what you did roughly around the time the socket closed error occurred happened as well as how long it took for the error to occur.ħ. In the description field, write a detailed description of what you were doing in game while you disconnected.Ħ. In the ôServer/Buildö section, make sure ôSingularityö is chosen and insert your build number.ĥ. Select ôTechnicalö from the Category field.Ĥ. Put "Socket closed error" in the Title field.ģ. Select "File" -> "Save workspace as." and save the workspace in a place you'll be able to find it again.Ģ. When you have reproduced the issue, switch to the logserver window again. Start Eve like you would normally do and play.Ħ. Select "File" -> "New Workspace" (or ctrl + w).Ĥ. Be sure you launch the logserver before you launch EVE.ģ. Find "logserver.exe" (it should be in your main EVE directory) and launch it.
#Error 10054 proxifier install
The default install location is C:\Program Files\CCP\EVE.Ģ. Find your Eve folder in Windows Explorer. To minimize any issues, we recommend you either restart your computer or check your Windows Task Manager processes list for any unresponsive instances of Eve.exe.ġ. The following information from your logserver logs is needed from the point where you start the client to when you receive the socket closed error.
#Error 10054 proxifier how to
Information on how to access Singularity can be found in the following thread. To help us gather information, we ask that you log onto SiSi with the test client. We recently enabled proxy logging on SiSi which should be able to help us better correlate a specific disconnect with client logs.
#Error 10054 proxifier code
Sisi has been updated to include code that logs disconnections more thoroughly but we need those of you that repeatedly have the problem to connect in order to get a real data set with no artificial anomalies. Some of the reports we have received however hinted at other possibilities that we want to explore fully before completely closing the door on this.
#Error 10054 proxifier software
The only way we have been able to do that so far is by artificially creating packet loss of 30% or higher, this would indicate an issue with the userÆs connection as opposed to our software or hardware. Regardless, we needed to have this issue reproduced in-house so that we could better understand what is happening and, if possible, determine how to resolve it. The fact that this has been happening for the same people over and over again suggested that this had something to do with their connection to the Internet. Based on this and our connection graphs it is clear that this issue has affected a small number of users from different parts of the world. Less than 40 bug reports have been received with the information we have requested. The bug reports were then gathered into the ticket mentioned above. On 9 December 2008 we replied to a forum thread asking those who were experiencing this issue to send us information about their Internet connection (ping plotter results) and client logs (logserver). The reports, however, kept trickling in and these workarounds did not resolve the issue for everyone. Many users reported that restarting/resetting their router had resolved the issue, while others reported that downloading third-party programs helped them. The first ticket was opened on 25 November 2008 in our internal defect tracker, and since late December we have been diligently investigating the issue. Reports of a socket closed began arriving via petitions and bug reports towards the end of November last year. What have we been doing to resolve this issue? Thread Statistics | Show CCP posts - 12 post(s) » Click here to find additional results for this topic using Google Investigating Socket Closed Errors - How You Can Help EVE Search - Investigating Socket Closed Errors - How You Can Help
0 kommentar(er)
