Patching error

[Sneaky Que]

After the last patch I can't patch or play 2D at all, have tried all the usual tricks, deleting patch folder content, restarted computer a few times, virus scanned etc...

When I try and patch it downloads about 90% of the patch then stops and says it cannot update the client.

KR also patched up fine and is working 100%. So I did a trace route to patch.owo.com and got this...



Tracing route to patch.owo.com [159.153.199.100]

over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms SpeedTouch.lan [10.0.0.138]

2 13 ms 22 ms 19 ms 172.18.113.99

3 14 ms 14 ms 12 ms 172.18.75.14

4 14 ms 12 ms 12 ms 61.9.194.136

5 179 ms 199 ms 200 ms GigabitEthernet2-7.dkn9.Canberra.telstra.net [165.228.176.193]

6 13 ms 12 ms 14 ms TenGigabitEthernet0-8-0-2.dkn-core1.Canberra.telstra.net [203.50.10.251]

7 14 ms 14 ms 14 ms TenGigE0-8-0-0-1.civ-core2.Canberra.telstra.net [203.50.6.125]

8 18 ms 17 ms 18 ms Pos0-5-0-2.ken-core4.Sydney.telstra.net [203.50.6.17]

9 17 ms 18 ms 18 ms Bundle-Ether1.pad-gw2.Sydney.telstra.net [203.50.6.29]

10 19 ms 20 ms 20 ms TenGigabitEthernet0/x.sydp-core02.Sydney.reach.com [203.50.13.70]

11 199 ms 200 ms 199 ms i-13-0.wil-core02.net.reach.com [202.84.141.109]

12 176 ms 176 ms 173 ms i-0-0.paix-core02.net.reach.com [202.84.143.62]

13 174 ms 175 ms 178 ms static.net.reach.com [202.84.251.74]

14 * * * Request timed out.

15 176 ms 192 ms 172 ms edge03.eqx-sjc.ea.com [159.153.192.254]

16 186 ms 173 ms 174 ms edge01.eqx-sjc.ea.com [159.153.192.1]

17 250 ms 310 ms 307 ms 159.153.192.238

18 280 ms 272 ms 274 ms 159.153.199.100

Trace complete.

Seems there would be an issue with hop 14? Looks like it is either an EA server or right before it gets to EA. Anyone else having 2D patching issues? Any ideas?

 

[Teeshy]

I cant get todays patch to work either, though for me it does seem to download the entire thing, starts to apply the patch, then I get an error message

I've cleared the patch folder and re-downloaded the patch 4 times so far, still getting the same error, I can get in and play still, so I've given up on the patch =P

 

[Sneaky Que]

I cant get todays patch to work either, though for me it does seem to download the entire thing, starts to apply the patch, then I get an error message

I've cleared the patch folder and re-downloaded the patch 4 times so far, still getting the same error, I can get in and play still, so I've given up on the patch =P

Yay! I'm not alone!

I'v given up also... I get the feeling it has something to do with that hop 14 server in my trace route above, which is nothing I can fix.

If a Dev is reading this could you please verify that your servers are all ok? Since KR patching works and 2D's doesn't it points to that hop that is timing out...

In the meantime, KR it is!

 

[jaraxlebaenrae]

If you are running vista you need to set uo or uoa to "run as administrator" I had this problem also, after 4 or 5 times of deleting the patch file i det it to run as admin and it worked fine.

 

[Sneaky Que]

double post...

 

[Sneaky Que]

If you are running vista you need to set uo or uoa to "run as administrator" I had this problem also, after 4 or 5 times of deleting the patch file i det it to run as admin and it worked fine.

Thanks but I'm running Win XP Home, Pro and Win 2k. Tried to patch on 3 different computers and no luck.

I also noticed that the latest patch it is trying to download is ~1.73MB according to UO Auto Patcher, but when I open the patch folder to delete it after it fails the reported size of the downloaded patch is only ~1.62MB...

I am thinking that I am getting major packet loss from the hop that is timing out and as a result losing part of the patch file during download, making it impossible for the Patcher to patch with it.

 

[Zyon Rockler]

I'm running Windows Vista 64. Had no problems patching off the same router, same connection, my son's computer running Windows XP Pro 64, received a patch error.

For now you can open the UO Folder and click on the icon to skip the patch server and get into the game, KR of 2D.

So far deleting patch folder content did not work. Updating Windows, Defrag and Disk Check are working now. I hope that this will fix the patch error.

I will check back later to see how it's going.

 

[von Beck]

Seems there would be an issue with hop 14? Looks like it is either an EA server or right before it gets to EA. Anyone else having 2D patching issues? Any ideas?

Nup. That's just a server that does not reply to ICMP messages (that's what tracert uses to do its thing). That's a fairly common setting on busy internet backbone servers. The proof that nothing's wrong with hop 14 is that all remaining hops in the trace exhibit no packet loss and exhibit no significant increase in latency. (from 16 to 17 is a bit laggy, but that's nothing to do with 14)

Thanks heaps for the heads up about the patch being broken mate. I'll be avoiding running the patch program until its fixed.

 

[Sneaky Que]

I'm running Windows Vista 64. Had no problems patching off the same router, same connection, my son's computer running Windows XP Pro 64, received a patch error.

For now you can open the UO Folder and click on the icon to skip the patch server and get into the game, KR of 2D.

So far deleting patch folder content did not work. Updating Windows, Defrag and Disk Check are working now. I hope that this will fix the patch error.

I will check back later to see how it's going.

I cant log in without patching either in 2D, but can log in fine with KR. I'm in the process of reinstalling 2D on my 2nd comp so we will see how that goes, I still think it is a networking issue though.

I did another two trace routes just now...


Tracing route to patch.owo.com [159.153.199.100]

over a maximum of 30 hops:


1 <1 ms <1 ms <1 ms SpeedTouch.lan [10.0.0.138]

2 13 ms 14 ms 14 ms 172.18.113.99

3 13 ms 13 ms 12 ms 172.18.75.14

4 13 ms 12 ms 12 ms 61.9.194.136

5 16 ms 20 ms 15 ms GigabitEthernet2-7.dkn9.Canberra.telstra.net [165.228.176.193]

6 15 ms 14 ms 14 ms TenGigabitEthernet0-8-0-2.dkn-core1.Canberra.telstra.net [203.50.10.251]

7 14 ms 12 ms 13 ms TenGigE0-8-0-0-1.civ-core2.Canberra.telstra.net [203.50.6.125]

8 18 ms 17 ms 17 ms Pos0-5-0-2.ken-core4.Sydney.telstra.net [203.50.6.17]

9 17 ms 18 ms 18 ms Bundle-Ether1.pad-gw2.Sydney.telstra.net [203.50.6.29]

10 21 ms 18 ms 20 ms TenGigabitEthernet0/x.sydp-core02.Sydney.reach.com [203.50.13.70]

11 199 ms 200 ms 200 ms i-13-0.wil-core02.net.reach.com [202.84.141.109]

12 173 ms 174 ms 175 ms i-0-0.paix-core02.net.reach.com [202.84.143.62]

13 175 ms 175 ms 175 ms static.net.reach.com [202.84.251.74]

14 * * * Request timed out.

15 172 ms 173 ms 171 ms edge03.eqx-sjc.ea.com [159.153.192.254]

16 174 ms 173 ms 173 ms edge01.eqx-sjc.ea.com [159.153.192.1]

17 173 ms 173 ms 173 ms 159.153.192.238

18 190 ms 177 ms 177 ms 159.153.199.100

Trace complete.




Tracing route to login.owo.com [159.153.196.43]

over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms SpeedTouch.lan [10.0.0.138]

2 17 ms 13 ms 14 ms 172.18.113.99

3 14 ms 20 ms 25 ms 172.18.75.14

4 14 ms 15 ms 21 ms 61.9.194.136

5 14 ms 12 ms 12 ms GigabitEthernet2-7.dkn9.Canberra.telstra.net [165.228.176.193]

6 14 ms 13 ms 13 ms TenGigabitEthernet0-8-0-2.dkn-core1.Canberra.telstra.net [203.50.10.251]

7 14 ms 14 ms 18 ms TenGigE0-8-0-0-1.civ-core2.Canberra.telstra.net [203.50.6.125]

8 22 ms 17 ms 17 ms Pos0-5-0-2.ken-core4.Sydney.telstra.net [203.50.6.17]

9 17 ms 17 ms 18 ms Bundle-Ether1.pad-gw2.Sydney.telstra.net [203.50.6.29]

10 17 ms 18 ms 18 ms TenGigabitEthernet2-0.sydp-core02.Sydney.reach.com [203.50.13.50]

11 199 ms 200 ms 205 ms i-14-0.wil-core02.net.reach.com [202.84.140.237]

12 174 ms 183 ms 174 ms i-0-0.paix-core02.net.reach.com [202.84.143.62]

13 174 ms 175 ms 175 ms static.net.reach.com [202.84.251.74]

14 * * * Request timed out.

15 173 ms 173 ms 173 ms edge03.eqx-sjc.ea.com [159.153.192.254]

16 173 ms 174 ms 172 ms edge01.eqx-sjc.ea.com [159.153.192.1]

17 172 ms 174 ms 173 ms 159.153.192.230

18 177 ms 179 ms 177 ms 159.153.196.43

Trace complete.


Whatever hop 14 is it has to be the problem, both the login and patch servers for 2D time out at this link.

 

[Kurgan]

Not a bad tracert for me..

1----1 ms----1 ms----1 ms Wireless_Broadband_Router
2----6 ms----14 ms----14 ms 98.111.86.1
3----6 ms----5 ms----6 ms G9-3-221.LCR-02.STTLWA.verizon-gni.net [130.81.138.206
4----7 ms----6 ms----7 ms P15-0.LCR-02.LSANCA.verizon-gni.net [130.81.28.166]
5----8 ms----7 ms----8 ms 0.so-7-1-0.XT2.SEA7.ALTER.NET [152.63.105.61]
6----26 ms----26 ms----26 ms 0.ge-6-0-0.XL4.SJC7.ALTER.NET [152.63.49.146]
7----27 ms----27 ms----28 ms POS7-0.GW1.SJC7.ALTER.NET [152.63.53.193]
8----27 ms----27 ms----27 ms ea-gw2.customer.alter.net [157.130.194.226]
9----28 ms----27 ms----28 ms edge01.eqx-sjc.ea.com [159.153.192.234]
10----26 ms----27 ms----26 ms 159.153.199.100

And this is over wireless.

 

[Sneaky Que]

13 174 ms 175 ms 175 ms static.net.reach.com [202.84.251.74]

14 * * * Request timed out.

15 173 ms 173 ms 173 ms edge03.eqx-sjc.ea.com [159.153.192.254]

I found this interesting, hop 13 is as follows:

IP:202.84.251.74
[SIZE=-1]OrgName: Asia Pacific Network Information Centre
OrgID: APNIC
Address: PO Box 2131
City: Milton
StateProv: QLD
PostalCode: 4064
Country: AU


Hop 15 is:

IP: [/SIZE]159.153.192.254
[SIZE=-1]OrgName: Electronic Arts, Inc.
OrgID: ELECTR-60
Address: 209 Redwood Shores Parkway
City: Redwood City
StateProv: CA
PostalCode: 94065
Country: US[/SIZE]

It means that hop 14 is the link from Australia to the US over the Pacific Ocean (maybe it's Cyclone Hamish?). I am also getting some horrid lag from Sydney to Milton which starts at hop 11, goes from about 20 to 200.

What is annoying is that to play on my home shard of Oceania (which is located in Sydney) I dont need to use these links, if only they had a localized patch and login server in Australia!

 

[Sneaky Que]

Although that doesn't explain why I can connect and patch with KR... Does anyone know the IP for the KR login and patch servers? Would be interesting to see if they are going through the same route.

 

[Sneaky Que]

Yay! Just got home and tried it again and it patched successfully!