Planetside 2 failed to install/update/validate

Discussion in 'Player Support' started by xerozero, Dec 11, 2012.

  1. xerozero

    Hey i have tried to run Planetside 2 for the last 2 weeks, maybe longer now but every time the launcher opens i get an error. when i press retry i get the same thing, this even happens when i validate. this is the same for steam and non steam versions. the error i get is:
    Unable to download SocketError:Connection Timed-out - Destination host failed to respond (10060 - 64.37.129.51 - http://manifest.patch.station.sony....lanetside2-live.sha.soeSocketError:Connection Timed-out - Destination host failed to respond (10060 - 64.37.129.51 - http://manifest.patch.station.sony....lanetside2-live.sha.soeSocketError:Connection Timed-out - Destination host failed to respond (10060 - 64.37.129.51 - http://manifest.patch.station.sony....lanetside2-live.sha.soeSocketError:Connection Timed-out - Destination host failed to respond (10060 - 64.37.129.51 - http://manifest.patch.station.sony....lanetside2-live.sha.soeSocketError:Connection Timed-out - Destination host failed to respond (10060 - 64.37.129.51 - http://manifest.patch.station.sony....lanetside2-live.sha.soeSocketError:Connection Timed-out - Destination host failed to respond (10060 - 64.37.129.51 - http://manifest.patch.station.sony....lanetside2-live/live/planetside2-live.sha.soe
    xerozero, Dec 11, 2012
    #1

  2. xerozero

    come on someone must know how to fix this...
    xerozero, Dec 14, 2012
    #2

  3. enjoy02

    same error here to :(
    enjoy02, Dec 30, 2012
    #3

  4. TSR-Jesse S Customer Service

    There are a few different issues which may be causing this problem for you, so you may need to try a few things to get into the game:

    1. Please ensure that you have added an exception within your Firewall or Anti-Virus software for planetside2.exe, launchpad.exe, awesomiumprocess.exe, and ApplicationUpdaterService.exe.

    The location of these files can vary, but by default they should look like this:

    Win7/Vista/Win8

    C:\Users\<your username>\AppData\Local\Sony Online Entertainment\ApplicationUpdater\ApplicationUpdaterService.exe
    C:\Users\Public\Sony Online Entertainment\Installed Games\PlanetSide 2\LaunchPad.exe
    C:\Users\Public\Sony Online Entertainment\Installed Games\PlanetSide 2\PlanetSide2.exe
    C:\Users\Public\Sony Online Entertainment\Installed Games\PlanetSide 2\LaunchPad.libs\AwesomiumProcess.exe

    Windows XP

    C:\Documents and Settings\<your username>\Application Data\ Sony Online Entertainment\ApplicationUpdater\ApplicationUpdaterService.exe
    C:\Program Files\Sony Online Entertainment\Installed Games\PlanetSide 2\LaunchPad.exe
    C:\Program Files\\Sony Online Entertainment\Installed Games\PlanetSide 2\PlanetSide2.exe
    C:\Program Files\Sony Online Entertainment\Installed Games\PlanetSide 2\LaunchPad.libs\AwesomiumProcess.exe

    The AppData and Application Data folders are hidden in Windows by default so you may need to enable "View Hidden Files/Folders" before you are able to find these files.

    2. You may need to clear the cache settings for the launch pad by going to the launchpad.libs folder in your PlanetSide 2 directory and delete the launchpad.cache folder then try accessing the game once again.

    3. The launcher may have been corrupted and will need to be repaired before it will work correctly. You can repair the launcher with the launcher set up file from the following link:

    https://launch.soe.com/installer/PS2_setup.exe

    Let me know if that helps.
    TSR-Jesse S, Dec 31, 2012
    #4

  5. xerozero

    None of the above worked for me. My firewall is down and my anti virus had all the paths already in exceptions. number 2 and 3 just give the exact same error.
    xerozero, Jan 5, 2013
    #5

  6. C4Chaos42

    Hmmm...

    Try pinging the IP addresses to see if your computer is able to even access it:

    1. Press windows key + R
    2. Type: cmd
    3. Then in command prompt type: ping -n 10 <ip address>
    IP addresses can be found in the error report you posted.
    Example: ping -n 10 64.37.129.51

    If you are able to reach the destination ip address, you should see a result like the one below.
    Code:
    Pinging 64.37.129.51 with 32 bytes of data:
Reply from 64.37.129.51: bytes=32 time=192ms TTL=115
Reply from 64.37.129.51: bytes=32 time=192ms TTL=115
Reply from 64.37.129.51: bytes=32 time=193ms TTL=115
 
Ping statistics for 64.37.129.51:
Packets: Sent = 3, Received = 3, Lost = 0 (0% loss)
Approximate round trip times in milli-seconds:
Minimum = 192ms, Maximum = 193ms, Average = 192ms

    This is what you should see if you can't (below are random IP addresses for demo purposes).
    Code:
    Pinging 192.168.1.112 with 32 bytes of data:
Reply from 192.168.1.7: Destination host unreachable.
Reply from 192.168.1.7: Destination host unreachable.
 
Ping statistics for 192.168.1.112:
Packets: Sent = 2, Received = 2, Lost = 0 (0% loss),
    Code:
    Pinging 202.23.1.14 with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
 
Ping statistics for 202.23.1.14:
Packets: Sent = 3, Received = 0, Lost = 3 (100% loss),
    C4Chaos42, Jan 5, 2013
    #6 Last edited by C4Chaos42, Jan 5, 2013

  7. xerozero

    i pinged both my IP addresses and got the following

    Pinging 192.168.0.10 with 32 bytes of data:
    Reply from 192.168.0.10: bytes=32 time<1ms TTL=128
    Reply from 192.168.0.10: bytes=32 time<1ms TTL=128
    Reply from 192.168.0.10: bytes=32 time<1ms TTL=128
    Reply from 192.168.0.10: bytes=32 time<1ms TTL=128
    Reply from 192.168.0.10: bytes=32 time<1ms TTL=128
    Reply from 192.168.0.10: bytes=32 time<1ms TTL=128
    Reply from 192.168.0.10: bytes=32 time<1ms TTL=128
    Reply from 192.168.0.10: bytes=32 time<1ms TTL=128
    Reply from 192.168.0.10: bytes=32 time<1ms TTL=128
    Reply from 192.168.0.10: bytes=32 time<1ms TTL=128

    Ping statistics for 192.168.0.10:
    Packets: sent = 10, received = 10 lost = 0
    Approx round trip times in ms
    min=0ms, max=0ms, average=0ms

    pinging 124.148.147.104 with 32 bytes of data:
    Reply from 124.148.147.104: bytes=32 time=1ms TTL=64
    Reply from 124.148.147.104: bytes=32 time<1ms TTL=64
    Reply from 124.148.147.104: bytes=32 time<1ms TTL=64
    Reply from 124.148.147.104: bytes=32 time<1ms TTL=64
    Reply from 124.148.147.104: bytes=32 time<1ms TTL=64
    Reply from 124.148.147.104: bytes=32 time<1ms TTL=64
    Reply from 124.148.147.104: bytes=32 time<1ms TTL=64
    Reply from 124.148.147.104: bytes=32 time<1ms TTL=64
    Reply from 124.148.147.104: bytes=32 time<1ms TTL=64
    Reply from 124.148.147.104: bytes=32 time<1ms TTL=64

    Ping statistics for 124.148.147.104:
    Packets: sent=10, receives=10, lost=0
    Approx round trip time in ms
    minimum=0ms, max=1ms, average=ms
    xerozero, Jan 5, 2013
    #7 Last edited by xerozero, Jan 5, 2013

  8. C4Chaos42

    Ping 64.37.129.5
    C4Chaos42, Jan 5, 2013
    #8

  9. xerozero

    request timed out
    edit. you said 64.37.129.5 when its at the end 51

    Pinging 64.37.129.51 with 32 bytes of data:
    Replying from 64.37.129.51: bytes=32 time=243ms TTL=118
    Replying from 64.37.129.51: bytes=32 time=200ms TTL=119
    Replying from 64.37.129.51: bytes=32 time=277ms TTL=118
    Replying from 64.37.129.51: bytes=32 time=253ms TTL=118
    Replying from 64.37.129.51: bytes=32 time=226ms TTL=119
    ....
    Ping statistics for 64.37.129.51:
    Packets: Sent = 10, Received = 10, Lost = 0
    Approx round trip times in milli-seconds
    Min=219ms, Max=277ms, Average=238ms
    xerozero, Jan 5, 2013
    #9 Last edited by xerozero, Jan 5, 2013

  10. C4Chaos42

    Strange...
    C4Chaos42, Jan 5, 2013
    #10

  11. xerozero

    Also the files ApplicationUpdaterService.exe and PlanetSide2.exe are non existent at the moment seeing as it wont even download planetside 2 when every time i launch the launchpad that error happens
    xerozero, Jan 7, 2013
    #11

  12. TSR-Jesse S Customer Service

    I'd suggest you do bypass your router and/or firewall initially to determine if they are the cause of the problem.

    If after bypassing your router or firewall you are able to connect then you most likely have an issue with the port forwarding in your router or firewall.

    If this is the case then, I'd suggest that you use the following information to properly configure your router or firewall for connectivity. You will need to consult the technical documentation for your router or firewall to be sure you know how to do this.

    PS2 Ports
    TSR-Jesse S, Jan 7, 2013
    #12

  13. xerozero

    My router is both a modem and a router in one so i cant bypass that.
    xerozero, Jan 7, 2013
    #13

  14. xerozero

    none of the above worked
    xerozero, Jan 12, 2013
    #14

  15. TSR-Jesse S Customer Service

    Regrettably this issue can be caused by a variety of different factors so it is hard to definitively say what could be triggering it. To provide you with a more concise answer my best suggestion would be to open a support ticket with us so we can check your system specs and provide you with some solid suggestions to get you back into the game. You can open a ticket with us at the following link:

    http://help.station.sony.com/app/ask
    TSR-Jesse S, Jan 12, 2013
    #15

  16. Death Wolf

    I just get
    http://manifest.patch.station.sony....anetside2-live.sha.soeSocketError:Unreachablehttp://manifest.patch.station.sony....anetside2-live.sha.soeSocketError:Unreachablehttp://manifest.patch.station.sony....anetside2-live.sha.soeSocketError:Unreachablehttp://manifest.patch.station.sony....anetside2-live.sha.soeSocketError:Unreachablehttp://manifest.patch.station.sony....anetside2-live.sha.soeSocketError:Unreachablehttp://manifest.patch.station.sony....anetside2-live.sha.soeSocketError:Unreachablehttp://manifest.patch.station.sony....anetside2-live.sha.soeSocketError:Unreachablehttp://manifest.patch.station.sony....anetside2-live.sha.soeSocketError:Unreachablehttp://manifest.patch.station.sony....anetside2-live.sha.soeSocketError:Unreachable
    Death Wolf, Nov 4, 2013
    #16