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

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

EVE General Discussion

 
  • Topic is locked indefinitely.
Previous page12
 

Client update was unsuccessful

First post
Author
Previous Topic Next Topic
Ayaya Matsura
Viziam
Amarr Empire
#21 - 2012-03-13 13:30:31 UTC  |  Edited by: Ayaya Matsura
client update failed @ 15% when building the .patch . running laucher 1.04

my launcher debug.log shows

[0313/212734:ERROR:proxy_resolver_winhttp.cc(79)] WinHttpGetProxyForUrl failed: 12167


launcher.exe.log shows

Exception in thread Thread-1:
Traceback (most recent call last):
File "threading.pyc", line 530, in __bootstrap_inner
File "threading.pyc", line 483, in run
File "zsync\readFromUrl.pyc", line 117, in DownloadPart
File "zsync\readFromUrl.pyc", line 136, in _DownloadPart
File "zsync\zsync.pyc", line 1020, in callback
File "core_utils.pyc", line 191, in exc_plus
AttributeError: 'Thread' object has no attribute '__bootstrap'

Exception in thread UpdaterProcessThread:
Traceback (most recent call last):
File "threading.pyc", line 530, in __bootstrap_inner
File "threading.pyc", line 483, in run
File "lib\update.pyc", line 532, in Update
File "core_utils.pyc", line 191, in exc_plus
AttributeError: 'Thread' object has no attribute '__bootstrap'

Exception in thread Thread-1:
Traceback (most recent call last):
File "threading.pyc", line 530, in __bootstrap_inner
File "threading.pyc", line 483, in run
File "zsync\readFromUrl.pyc", line 117, in DownloadPart
File "zsync\readFromUrl.pyc", line 136, in _DownloadPart
File "zsync\zsync.pyc", line 1020, in callback
File "core_utils.pyc", line 191, in exc_plus
AttributeError: 'Thread' object has no attribute '__bootstrap'

Exception in thread UpdaterProcessThread:
Traceback (most recent call last):
File "threading.pyc", line 530, in __bootstrap_inner
File "threading.pyc", line 483, in run
File "lib\update.pyc", line 532, in Update
File "core_utils.pyc", line 191, in exc_plus
AttributeError: 'Thread' object has no attribute '__bootstrap'

Exception in thread Thread-1:
Traceback (most recent call last):
File "threading.pyc", line 530, in __bootstrap_inner
File "threading.pyc", line 483, in run
File "zsync\readFromUrl.pyc", line 117, in DownloadPart
File "zsync\readFromUrl.pyc", line 136, in _DownloadPart
File "zsync\zsync.pyc", line 1020, in callback
File "core_utils.pyc", line 191, in exc_plus
AttributeError: 'Thread' object has no attribute '__bootstrap'

Exception in thread UpdaterProcessThread:
Traceback (most recent call last):
File "threading.pyc", line 530, in __bootstrap_inner
File "threading.pyc", line 483, in run
File "lib\update.pyc", line 532, in Update
File "core_utils.pyc", line 191, in exc_plus
AttributeError: 'Thread' object has no attribute '__bootstrap'
CCP Donut Golem
C C P
C C P Alliance
#22 - 2012-03-13 13:49:26 UTC
Eugene Spencer wrote:
I don't understand. I patch my client, fire it up and I get a client update like the old way. Wasn't the launcher supposed to change all that?


Confusingly, we have several methods of performing updates. The first version of the Launcher is designed to replace the old patching system used for delivering major releases.

The "Client Update" system you mention is used for delivering code-only changes. We agree that it's silly for you to have to restart your client after having just patched! This is one of the first things that we'll be tackling in subsequent versions of the Launcher.

The general idea is to streamline the entire process until you live in a bright, restart-less future, something we'll achieve incrementally Big smile.
Ayaya Matsura
Viziam
Amarr Empire
#23 - 2012-03-13 15:46:36 UTC
no response?
cubause ause
Center for Advanced Studies
Gallente Federation
#24 - 2012-03-13 17:06:41 UTC  |  Edited by: cubause ause
I am having this same issue.

with the update being unsuccessful at around 15% and getting an window to pop up with "exception".
Scion Lex
LEX Investments
#25 - 2012-03-13 19:35:47 UTC  |  Edited by: Scion Lex
Went through the normal patch process. New 'launcher' came up and starting doing its thing. Note it reminds me of the wow laucher *shudder*. Then im told 'client update unsuccessful'. I should have posted the "exception", but I went straight to repair out of instinct....which is doing its thing now. Come on CCP your better than this.


...about 5 min later.

In CCP's defense it does appear my client is damaged as I am 'missing' blocks of data resulting in roughly 45m of downloading through the repair tool. I have no idea what cause one to be missing information, but im hoping this is the root of the issue.
CCP Donut Golem
C C P
C C P Alliance
#26 - 2012-03-13 19:51:08 UTC
*Cross-posting from the Crucible 1.5 Issues Thread*

Just to update everyone on the situation:

We're aware of the permissions issues plaguing some of our users. We're actively working on a fix for this.

In the mean-time, please do the following:
1. Restart your computer
2. Run the Repair Tool without starting any other EVE-related process (ie Client, Launcher, etc) beforehand.
3. Navigate to EVE/bin/ and run ExeFile.exe directly.
4. Please reply to this thread confirming this work around, if it is, in fact, successful.

A few caveats about this approach. If you encounter permission errors on files during the Repair process, they may not have been completely updated to their latest versions. Therefore, you may not be running a completely sane client, but you might be able to get in-game.

Thank you for bearing with us while we sort these issues out.
Scion Lex
LEX Investments
#27 - 2012-03-13 20:55:06 UTC
running repair + running eve from the exe solved the problem. Ty and cheers CCP.P
Previous page12