| Pages: [1] 2 :: one page |
| Author |
Thread Statistics | Show CCP posts - 2 post(s) |

Ausser
Bubba Gump ORE Corp.
|
Posted - 2009.12.21 16:19:00 -
[1]
I had trouble downloading the full installer (2.7GB @20kB/s = 30h+ download time ). I've found a solution where you only need to download ~160MB to patch from TQ-120813 to SISI-121200.
Since there is no native 120813 to 121200 patch out there i had to find another solution. I've manually tweaked the version number in the patch download url and found the existing patch from 119404 to 121200.
Next problem: i didnt had version 119404, just the current tq copy of 120813. But this can be worked arround by forcing the repair tool to do a rollback for us, since version 120813 is nothing else than a broken (patched ) version 119404.
To enforce this rollback you have to copy your TQ directory and edit the file common.ini in your copy:
Replace the version numbers in the strings "build=120813" and "sync=120813" by "119404". They should look like "build=119404" and "sync=119404". Save the file.
Now start repair.exe in this directory. It will notice the broken (newer) files and download ~150MB to fix them. After that, you have the old version 119404 in your directory.
Start this old version with the /server:singularity flag as usual. When the client starts up, it will, after half a minute or so, offer you a patch to version 121200. Let the autopatcher do the job - this patch is just 10MB large.
Have fun.
This practice can be adapted respectiveley for future versions. I would also recommend you keep a copy of each sisi version directory for a while ...
P.S.: Please send me isk and fresh snowballs on TQ 
|

RoCkEt X
Hostile.
|
Posted - 2009.12.21 17:09:00 -
[2]
Quote: Downloading file replacements... Bits download job in incorrect state, state: TRANSIENT_ERROR Error Level: 2 Log file: C:\Program Files\CCP\EVE - Copy\repairlog.txt
repair.exe fails with that error reported in the repair file.
|

Ausser
Bubba Gump ORE Corp.
|
Posted - 2009.12.21 18:10:00 -
[3]
Originally by: RoCkEt X
Quote: Downloading file replacements... Bits download job in incorrect state, state: TRANSIENT_ERROR Error Level: 2 Log file: C:\Program Files\CCP\EVE - Copy\repairlog.txt
repair.exe fails with that error reported in the repair file.
That happened to me one time too. Reasons could be:
a) Dirty copy of TQ directory. E.g. by trying to patch before repair. Try to use a fresh copy, and edit just both the two lines in common.ini like shown above.
b) Used the 'Show details' button on the repair tool. Try to run the tool without the details (only the progress bar visible).
I have not figured out which one causes the failure since it worked on the second try with a fresh directory and without to touch the show details button.
Maybe you could post the common.ini if you still get the error.
|

Matthew97
Amarr
|
Posted - 2009.12.21 21:15:00 -
[4]
Confirmed that this works.
Quote:
Success! Update applied successfully! (19404-121200)
|
|

CCP Atropos

|
Posted - 2009.12.21 21:17:00 -
[5]
That TRANSIENT_ERROR is a BITS error. If you could do me a favour, open a command prompt as administrator, and then type 'bitsadmin /list' This should list any BITS jobs. One of the jobs should be called {eveonline_...} (I can't recall the exact prefix off hand).
If you could then execute 'bitsadmin /info <job name>' and replace <job name> with the full job name of the EVE job you got in the first step. I'd love to get a copy of the BITS info on your jobs.
Software Engineer Core Engineering |
|

Catari Taga
Centre Of Attention Rough Necks
|
Posted - 2009.12.21 22:39:00 -
[6]
Edited by: Catari Taga on 21/12/2009 22:39:02
Originally by: CCP Atropos That TRANSIENT_ERROR is a BITS error. If you could do me a favour, open a command prompt as administrator, and then type 'bitsadmin /list' This should list any BITS jobs. One of the jobs should be called {eveonline_...} (I can't recall the exact prefix off hand).
If you could then execute 'bitsadmin /info <job name>' and replace <job name> with the full job name of the EVE job you got in the first step. I'd love to get a copy of the BITS info on your jobs.
The BITSadmin tool is part of the support tools package which is not installed by default (find it in the Support\Tools folder of your Windows CD or download from Microsoft).
The job will be called eveonline_client_repair.
|

Ausser
Bubba Gump ORE Corp.
|
Posted - 2009.12.22 02:10:00 -
[7]
Edited by: Ausser on 22/12/2009 02:17:42
Originally by: CCP Atropos That TRANSIENT_ERROR is a BITS error. If you could do me a favour, open a command prompt as administrator, and then type 'bitsadmin /list' This should list any BITS jobs. One of the jobs should be called {eveonline_...} (I can't recall the exact prefix off hand).
If you could then execute 'bitsadmin /info <job name>' and replace <job name> with the full job name of the EVE job you got in the first step. I'd love to get a copy of the BITS info on your jobs.
I wasnt able to reproduce the TRANSIENT_ERROR problem any more. I've captured bitsadmin output while running the test like described above.
OS is Vista Ultimate x64 SP2 with all patches applied.
Originally by: bitsadmin /list C:\Windows\system32>bitsadmin /list
BITSADMIN version 3.0 [ 7.0.6001 ] BITS administration utility. (C) Copyright 2000-2006 Microsoft Corp.
{1C3C1DE9-AB63-41E0-BEF9-6B98A503E950} 'eveonline_client_repair' TRANSFERRING 19 / 85 745215 / 154038759 Listed 1 job(s).
Originally by: bitsadmin /info eveonline_client_repair C:\Windows\system32>bitsadmin /info eveonline_client_repair
BITSADMIN version 3.0 [ 7.0.6001 ] BITS administration utility. (C) Copyright 2000-2006 Microsoft Corp.
{1C3C1DE9-AB63-41E0-BEF9-6B98A503E950} 'eveonline_client_repair' TRANSFERRING 46 / 85 4643433 / 154038759
There is not much information without /verbose flag specified.
If you like you can have the output from "bitsadmin /util /version /verbose" too (it's long).
Originally by: Catari Taga The BITSadmin tool is part of the support tools package which is not installed by default (find it in the Support\Tools folder of your Windows CD or download from Microsoft).
BITSAdmin is on Vista allready preinstalled, just XP users need to download it.
Nice description of BITSAdmin, its the command line options and a download link to the XP version can be found here on MSDN.
|

Alex Zander505
Amarr Red Water Syndicate
|
Posted - 2009.12.22 06:53:00 -
[8]
i tried to open up the common.ini and change the build and sync but it wont let me change it. it says something how the file cannot be created and check if the file name and path is correct but it wont ever let me save. can someone help me? and also when i try to run the repair it says nothing is wrong... probably because i cant get the common.ini to save. Help?
|

Ausser
Bubba Gump ORE Corp.
|
Posted - 2009.12.22 07:41:00 -
[9]
Originally by: Alex Zander505 i tried to open up the common.ini and change the build and sync but it wont let me change it. it says something how the file cannot be created and check if the file name and path is correct but it wont ever let me save. can someone help me? and also when i try to run the repair it says nothing is wrong... probably because i cant get the common.ini to save. Help?
Sounds like you are using Vista, which has access control to protect important files, and your sisi copy is located below C:\Program Files.
Simply move the sisi directory to the desktop, it should be editable there. 
|

EntroX
Total Mayhem. Cry Havoc.
|
Posted - 2009.12.22 08:42:00 -
[10]
Confirming this worked under Vista x64 
/ex
|

Ximen
|
Posted - 2009.12.22 11:34:00 -
[11]
Originally by: Alex Zander505 i tried to open up the common.ini and change the build and sync but it wont let me change it. it says something how the file cannot be created and check if the file name and path is correct but it wont ever let me save. can someone help me? and also when i try to run the repair it says nothing is wrong... probably because i cant get the common.ini to save. Help?
Save it to my documents, and then drag it into the folder and replace it. Seems like one of UAC's weirder behaviors, but it actually makes sense, kinda. |

NyteTyger
Gallente NiteSun Enterprises
|
Posted - 2009.12.22 11:52:00 -
[12]
Originally by: Ximen Edited by: Ximen on 22/12/2009 11:38:09
Originally by: Alex Zander505 i tried to open up the common.ini and change the build and sync but it wont let me change it. it says something how the file cannot be created and check if the file name and path is correct but it wont ever let me save. can someone help me? and also when i try to run the repair it says nothing is wrong... probably because i cant get the common.ini to save. Help?
Save it to my documents, and then drag it into the folder and replace it. Seems like one of UAC's weirder behaviors, but it actually makes sense, kinda.
Oh and this method worked fine on W7 ultimate x64
W7 Home Premium 64 here, worked like a charm.
Thanks OP!  __________________________________________
It's a do or die universe, so you better damn well choose between one or the other. |

keuel
Gallente The Scope
|
Posted - 2009.12.22 22:22:00 -
[13]
Strange, it didnŠt work on here, IŠve done everything you said, and it said the same error of trascent_error :( Is it probablybecause I donŠt have 8000mb of free space?
|

Rabbak
|
Posted - 2009.12.22 23:08:00 -
[14]
thx Ausser! 
|

Lt Expendable
|
Posted - 2009.12.23 00:29:00 -
[15]
Originally by: Ausser
Originally by: Alex Zander505 i tried to open up the common.ini and change the build and sync but it wont let me change it. it says something how the file cannot be created and check if the file name and path is correct but it wont ever let me save. can someone help me? and also when i try to run the repair it says nothing is wrong... probably because i cant get the common.ini to save. Help?
Sounds like you are using Vista, which has access control to protect important files, and your sisi copy is located below C:\Program Files.
Simply move the sisi directory to the desktop, it should be editable there. 
this worked great im downloding the patch right now thank you all so much for your wondrful work here also id like to say it doesnt have to be the whole diectory for sisi just moving the common.ini to my doc or the desktop, editing and copying it back to the directory worked with vista uac thanx all
|

d3vo
|
Posted - 2009.12.23 03:58:00 -
[16]
Thanks a lot OP! __________ \(^.^)/ |

Ausser
Bubba Gump ORE Corp.
|
Posted - 2009.12.23 04:35:00 -
[17]
Originally by: Lt Expendable ((EDITED)) BE WARNED:::: you will probably have to manually patch 119404 to latest, auto patching puts the client back to ver.120813!!
Hmm... did you forgotten to start eve.exe with the /server:87.237.38.50 flag? If so, the autopatcher would patch to current tq version instead of what is on sisi.
|

Mikal Drey
Atlas Alliance
|
Posted - 2009.12.23 08:57:00 -
[18]
Edited by: Mikal Drey on 23/12/2009 08:57:33 hey hey
i had 118927 . . .
changed the build number, changed the sync number, clicked repair.
149MB \o/
and i changed directly to the current 121200 build number without any intermediate patching.
tyvm this helped alot and will hopefully remove all the pain of test server patching drama.
|

Logia
|
Posted - 2009.12.25 12:13:00 -
[19]
Thanks, works like a charm on windows 7 x64 Professional.
|

Lady Yevon
Amarr Incorporated Fears
|
Posted - 2009.12.26 15:19:00 -
[20]
I have followed your step and am now on version 6.20.121200 however I have server as 87.237.32.22 and status as Incompatible (Release)
HELP!
|

PirateMajor
|
Posted - 2009.12.26 18:07:00 -
[21]
I have followed your step and am now on version 6.20.121200 however I have server as 87.237.32.22 and status as Incompatible (Release)
HELP!
|

Lord Atrix
|
Posted - 2009.12.26 23:47:00 -
[22]
i have got the latest test server build 121200. Every time I tried to download the patch I keep get an error 404 from the link and doesnt work from the test server patch patch and using the convert link. Anyway i have got the 121200 server build but now comes up with incompatible release server 87.237.32.22 same as above post but i have this problem only after the dominion patch and i could get access before. Have you guys just closed the test server for now? or do we need to do something more?
|

Lord Atrix
|
Posted - 2009.12.26 23:53:00 -
[23]
Originally by: Bux Naked
Originally by: Borgor Brag And how exactly do I do that?
Thanks for the reply
right click the EVE shortcut and go to properties and where you see the "C:\xxxx\xxxx\eve test\eve.exe" just add /server:87.237.38.50 right after the quotation marks.
Example of what it should look like: "C:\eve test\eve.exe" /server:87.237.38.50
I generally hate it when people link a page with nothing but irrelevant text when you only need to know one small part, i.e. how to add the /server IP 
well after doing a bit more looking through forum found this its solved my problem
|

Lady Yevon
Amarr Incorporated Fears
|
Posted - 2009.12.27 01:23:00 -
[24]
Edited by: Lady Yevon on 27/12/2009 01:23:02
Originally by: Lord Atrix
Originally by: Bux Naked
Originally by: Borgor Brag And how exactly do I do that?
Thanks for the reply
right click the EVE shortcut and go to properties and where you see the "C:\xxxx\xxxx\eve test\eve.exe" just add /server:87.237.38.50 right after the quotation marks.
Example of what it should look like: "C:\eve test\eve.exe" /server:87.237.38.50
I generally hate it when people link a page with nothing but irrelevant text when you only need to know one small part, i.e. how to add the /server IP 
well after doing a bit more looking through forum found this its solved my problem
Thanks Lord Atrix, Confirming this sorted my problem.
|

Griefuss
|
Posted - 2009.12.27 18:07:00 -
[25]
Originally by: Ausser
Originally by: RoCkEt X
Quote: Downloading file replacements... Bits download job in incorrect state, state: TRANSIENT_ERROR Error Level: 2 Log file: C:\Program Files\CCP\EVE - Copy\repairlog.txt
repair.exe fails with that error reported in the repair file.
That happened to me one time too. Reasons could be:
a) Dirty copy of TQ directory. E.g. by trying to patch before repair. Try to use a fresh copy, and edit just both the two lines in common.ini like shown above.
b) Used the 'Show details' button on the repair tool. Try to run the tool without the details (only the progress bar visible).
I have not figured out which one causes the failure since it worked on the second try with a fresh directory and without to touch the show details button.
Maybe you could post the common.ini if you still get the error.
Just to echo this i kept having bits error before i deleted my duplicate tq copy and tried again with a fresh copy, works now (XP)
|

Poision Kevin
Amarr Big Shadows Atlas Alliance
|
Posted - 2009.12.28 20:55:00 -
[26]
Originally by: Mikal Drey Edited by: Mikal Drey on 23/12/2009 08:57:33 hey hey
i had 118927 . . .
changed the build number, changed the sync number, clicked repair.
149MB \o/
and i changed directly to the current 121200 build number without any intermediate patching.
tyvm this helped alot and will hopefully remove all the pain of test server patching drama.
Was same for me, and hope fully this will work, i'll come bck for confirming and all that stuff ;) nice guide though
PK
PK |

Allen Ramses
Caldari Typo Corp
|
Posted - 2009.12.29 01:23:00 -
[27]
For those of you having BITS errors, try deleting the SiSi cache folder. I kept getting BITS errors until I did.
%AppData%\Local\CCP\EVE is where you want to look.
____________ I'd make a forum signature that didn't suck, but I'm restricted by a character limit that does. |

ctttttttt
Total Mayhem. Cry Havoc.
|
Posted - 2009.12.29 06:32:00 -
[28]
thanks for the help. Every time ive tried to connect to the test server in the past its something new i have to do. Its always a much more fun adventure trying to get the test server to work then actually testing stuff. uff.
|

NyteTyger
Gallente NiteSun Enterprises
|
Posted - 2009.12.29 22:27:00 -
[29]
Bumping this since the number of people unable to read past the first 3 topics seems to have spiked... __________________________________________
It's a do or die universe, so you better damn well choose between one or the other. |

Enraged Mado
DEATHFUNK Atlas Alliance
|
Posted - 2009.12.29 23:17:00 -
[30]
Had an error with BITS when running repair also.
Managed to fix it by disabling and restarting the BITS service.
Thanks.  -------
|
| |
|
| Pages: [1] 2 :: one page |
| First page | Previous page | Next page | Last page |