|
Author |
Thread Statistics | Show CCP posts - 77 post(s) |
Marlakh
Bene Gesserit ChapterHouse Sanctuary Pact
81
|
Posted - 2012.03.13 14:01:00 -
[1] - Quote
CCP Donut Golem wrote: Were you running version 1.04 or 1.05? If you're at 1.04, please restart the Launcher to receive an update, which may fix this issue.
The patching I did was unsuccessful. Here's what happened:
1. After the initial patch to get the launcher (v 1.04), I clicked "Play" from the launcher.
2. The client launched and showed that it was incompatible. A dialog box appeared with the message "The update has been downloaded. The client will not close and the update process begin."
3. The Update Setup dialog box appeared but once it was finished a warning message appeared "Multiple instances of the launcher cannot be run from the same directory. This instance will now close".
4. Clicking on the "Play" from the launcher (still v1.04) resulted in the same process repeating itself (steps 2 to 3).
5. Running the repair tool from the Eve client folder ended with the message "Completed successfully. The Eve Online client was successfully repaired". Starting the Launcher showed that it remained at v1.04
6. Directly starting eve using the eve.exe application resulted in steps 2 to 3 repeating.
7. Starting the Launcher did not auto-patch it to v1.05 like CCP Donut said earlier.
My Eve folder resides on a different drive than my windows 7 drive. Not sure if its relevant, just saying.
Any help would be appreciated! Thanks!
|
Marlakh
Bene Gesserit ChapterHouse Sanctuary Pact
81
|
Posted - 2012.03.14 12:50:00 -
[2] - Quote
@CCP: I'm still having problems installing the new patch, one day after it came out Unfortunately I'm far from alone in this.
My original post is here. Main difference is that I've managed to patch the Launcher to v1.09 but everything else is the same. Using Win 7 Professional 64 bit
Tried again today:
1. After patching the launcher (v 1.09), I clicked "Play" from the launcher.
2. The client launched and showed that it was incompatible. A dialog box appeared with the message "The update has been downloaded. The client will not close and the update process begin."
3. The Update Setup dialog box appeared but once it was finished a warning message appeared "Multiple instances of the launcher cannot be run from the same directory. This instance will now close".
4. Clicking on the "Play" from the launcher (still v1.09) resulted in the same process repeating itself (steps 2 to 3).
5. Running the repair tool as administrator from the Eve client folder ended with the message "Completed successfully. The Eve Online client was successfully repaired". This was repeated as advised, including several reboots.
6. Directly starting eve using the eve.exe application resulted in steps 2 to 3 repeating.
7. Did a complete new install today (ver 349998), but the above problems persist.
My Eve folder resides on a different drive than my windows 7 drive. Not sure if its relevant, just saying.
Any help would be appreciated! Thanks! |
Marlakh
Bene Gesserit ChapterHouse Sanctuary Pact
81
|
Posted - 2012.03.15 14:19:00 -
[3] - Quote
Ok, continuing my story, following Day 1 and Day 2, here is Day 3:
1. Downloaded the latest repair tool as read from the news: http://community.eveonline.com/news.asp?a=single&nid=4930&tid=1
2. Copied the downloaded repair.eve into the Eve client folder, and double clicked it. New repair tool then ran and appeared to update itself.
3. Opened Eve Launcher as admin. Client updated itself automatically to version 350962.
4. Opened Eve Launcher as admin and clicked "Play".
5. Once client has launched, Incompatible (Protocol) message appeared beside the login text fields. Dialog box appeared titled "Ready to Update" and said "the update has been downloaded. The client will now close and the update process begin". Clicked ok.
6. Update setup progress dialog box appeared and appeared to finish with no errors.
7. Opened Eve Launcher again and clicked "Play".
Steps 5 to 6 repeated itself, again and again, even with multiple reboots between supposed "patches".
Nearly at wit's end. Please help! |
Marlakh
Bene Gesserit ChapterHouse Sanctuary Pact
81
|
Posted - 2012.03.15 15:12:00 -
[4] - Quote
Jaden Plymoth wrote: I've been having this same problem over the last 3 days. The Launcher randomly will decide to patch every now and then, but its back at its antics today. I've had a friend send me the most recent .patch file in an effort to force the launcher to patch, but the import function appears to be broken as well. I suspect the launcher is either timing out when calculating if an update is needed due to certain security functions through internet connections (Settings which are well out of our control, I might add). Still waiting on CCP to answer my previous question to confirm.
After writing my last post, my launcher downloaded patch 351477 which finally worked! Just check if your launcher is v1.09 and that it downloads this version of the client.
Good luck! |
Marlakh
Bene Gesserit ChapterHouse Sanctuary Pact
81
|
Posted - 2012.03.16 13:21:00 -
[5] - Quote
Day 1 Day 2 Day 3
At the end of Day 3, I successfully installed patch 351477, which allowed the client to launch and login successfully. I thought my troubles were finally over. Boy, was I wrong!
Day 4:
I fired up the client, and the Launcher proceeded to revert 351477 back to 350962! What happened afterward was Days 1 to 3 all over again! In other words:
1. Opened Eve Launcher as admin and clicked "Play".
2. Once client has launched, Incompatible (Protocol) message appeared beside the login text fields. I noticed that the client version on the top left read 350962. The Dialog box appeared titled "Ready to Update" and said "the update has been downloaded. The client will now close and the update process begin". Clicked ok.
3. Update setup progress dialog box appeared and appeared to finish with no errors.
4. Opened Eve Launcher again and clicked "Play".
Steps 1 to 3 then repeated itself, just like Days 1 to 3. As of this writing, the Launcher version still read v1.09. I hope v1.11 (which is supposed to be out today) addresses the problem.
Grroooooaaaannnnn.....
|
Marlakh
Bene Gesserit ChapterHouse Sanctuary Pact
81
|
Posted - 2012.03.16 15:40:00 -
[6] - Quote
Jaden Plymoth wrote: I very nearly had this problem last night when my client crashed and I attempted to relaunch the launcher. The problem once again lies in win_launcherinfoTQ_inc.txt. When it calls ClientUpdate: BuildNumberInfoFile: The value it is receieving back is the value for the old patch, where as its supposed to be the new patch. If you change the URL it calls with the same file, only with the right information on a seperate server and still have the .patch file for 350962 to 351477, you can fool your launcher into needing an update. The update process will fail, but the 'import' tool will work and you can import the .patch file to get your client up and running.
Well, I couldnt locate the win_launcherinfoTQ_inc.txt file, but I did import the 350962 to 351477 patch file again, which forced the Launcher to reverse the reversion (lol) back to 351477. But then it also updated itself to v1.11. The client launched successfully after both actions, so not sure which was the one that solved it.
In any case, thanks for the tip. Just keeping my fingers crossed that there's no Day 5 of my problems |
|
|
|