These forums have been archived and are now read-only.

The new forums are live and can be found at https://forums.eveonline.com/

Issues, Workarounds & Localization

 
  • Topic is locked indefinitely.
 

My client will not launch
Author
Previous Topic Next Topic
Stephan Seethmore
Seethmore Mercenary Group
#1 - 2014-01-14 22:08:47 UTC
I've submitted a ticket over this but haven't received a response yet so I thought I'd pick the community's brain.

I cannot launch the game. I can launch the launcher, but after logging in, when I hit play it says "Launching" but after a few moments it returns to "Play", and the game has not launched.

I've tried launching both the launcher as administrator, as well as launching the game itself through the exefile as administrator. Didn't work.

I also cannot launch the "tools" thing (cog wheel in the upper right corner of the launcher). When I click it absolutely nothing happens.

I've also noticed that when I click launch, the exefile shows up in the task manager for about 2-3 seconds before disappearing.

I've run the repair tool, it didn't fix it.

I've searched for others having this problem, and haven't found any results similar since 2009-2010.

I'm playing on a PC with Windows 7
Stephan Seethmore
Seethmore Mercenary Group
#2 - 2014-01-14 22:11:54 UTC
I've also tried both disabling anti virus (AVG) and including the launcher and exefile in the exceptions.
Stephan Seethmore
Seethmore Mercenary Group
#3 - 2014-01-14 22:26:59 UTC
I've just noticed this error showing up at the bottom of the repair tool log. Not sure what it means.


Warning:
Traceback (most recent call last):
File "zsync\zsync.pyc", line 732, in ChecksumFiles
File "checksum.pyc", line 384, in Sync
File "shelve.pyc", line 169, in sync
File "bsddb\__init__.pyc", line 347, in sync
File "bsddb\dbutils.pyc", line 68, in DeadlockWrap
DBRunRecoveryError: (-30974, 'DB_RUNRECOVERY: Fatal error, run database recovery -- PANIC: fatal region error detected; run recovery')
(3/7) Downloading recipes: Initializing ...
(3/7) Downloading recipes: 100.0%, 25.16 KB/25.16 KB, 5.03 KB/s, 00m00s
(4/7) Calculating patch: Initializing ...
(4/7) Calculating patch: 100.0%, 00m03s
Complete
Total Runtime: 0h03m20s
seth Hendar
I love you miners
#4 - 2014-01-15 10:21:26 UTC
can you try to launch the game the "old" way, bypassing the launcher?

to do so, instead of using a link to "%evedir%\EVE Online Launcher", try using "%evedir%\bin\exefile.exe"

this will launch the game like it was before this crap of a launcher came by, and should allow you to play.

in my corp, we stopped using the launcher since it came, and so far, no issues launching the game except when a bad update hit, wich has happened only one since if memory serves.


seriously CCP, get id of this launcher, it is around for months and ppl STILL struggle with the vary same issues they had since day one of the launcher!
Lamon Nunya
University of Caille
Gallente Federation
#5 - 2014-03-30 11:25:11 UTC
I have this same issue it appears for about 2 weeks now. I can not launch from the bin .exe file either.

I have removed eve and reinstalled twice now. I have ran the repair program with no success I did install McAfee antivirus since I picked up a virus AVG would not remove but Eve had failed before both of these issues.

I have looked over the forums and sometimes the questions asked are over my head technically so please hand hold me through any help provided.
Sturmwolke
#6 - 2014-03-30 12:52:01 UTC  |  Edited by: Sturmwolke
The launcher runs several functions (from update checks, passwd hashing, client checksum checks, and automated error logging) over SSL (port 443) and connects to multiple servers for those functions.
It's also a mini web browser that can deal targeted advert as they so wish. All in all, it's a complex piece of middleware that isn't graceful nor robust when little things break (to put it mildly).

From my experience, two things matter when you try to start EVE via the launcher, your connection's congestion state i.e. don't run a heavy torrent in the background when starting the launcher and an uncorrupted client checksum file (which can rebuild if you suspect it's corrupted). This assumes you'd eliminated the obvious issues like permissions, firewall etc.

While researching a different issue, I also found an article that that reported a slow SSL performance caused by a specific router that has "IP Spoofing Check" enabled, which is rather odd ( http://www.geekzone.co.nz/forums.asp?forumid=49&topicid=15230 ). If you Google up, slow SSL performance issue looks to be be fairly commonplace. Bearing in mind how the launcher runs on SSL .... well ... make your own conclusions. For a quick read, try http://blog.cloudflare.com/how-cloudflare-is-making-ssl-fast and pay atttention to the paragraph "What Makes SSL Slow?".

P.S As per post #4, run the client directly. If that fails, then it isn't a launcher issue per se.