CO Launcher not loading

sypherv · January 2013

bjswanks wrote: »

I don't know if anyone looked in the gameclient folder clientservercomm .txt file shows a ton of socket errors, etc...

I'm sure the Devs knows about it, along with anyone else reading this.....

would this cause the game to fail to launch?

xcaligax · January 2013

I gave up. I'm playing ********* while this whole thing unscrews itself.

xcaligax · January 2013

oh wow! HHAHAHAHA! IT CENSORES THE NAMES OF OTHER GAMES! Well played PWE, well played. :rolleyes:

sanguineviper · January 2013

Well, i managed to get on, but I was plunged into a totally dead silent world due to chat offline, ahwell...

romgotsk · January 2013

welcome to Champions Offline.

trailturtle · January 2013

This should be fixed now. Thanks for your patience, everyone.

ethanmorrigan · January 2013

I got in now, sadly i had yesterday a whole day i wanted to play.

circleofpsi · January 2013

trailturtle wrote: »

This should be fixed now. Thanks for your patience, everyone.

Mine works ok now but was slow doing the patch thing however also I live in the UK, England so here is my test thing trailturtle

Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.

C:\Users\alex.MICROS4U>tracert patchserver.crypticstudios.com

Tracing route to patchserver.crypticstudios.com [208.95.185.41]
over a maximum of 30 hops:

1 7 ms 7 ms 6 ms cpc5-telf12-2-0-gw.16-1.cable.virginmedia.com [8
2.39.228.1]
2 8 ms 7 ms 8 ms wolv-core-2a-xe-211-618.network.virginmedia.net
[80.1.80.65]
3 7 ms 6 ms 7 ms wolv-core-2b-ae1-0.network.virginmedia.net [213.
105.159.150]
4 41 ms 84 ms 32 ms brhm-bb-1b-ae7-0.network.virginmedia.net [213.10
5.159.145]
5 13 ms 15 ms 15 ms ae1.lon25.ip4.tinet.net [77.67.65.161]
6 91 ms 91 ms 91 ms xe-3-0-0.bos11.ip4.tinet.net [141.136.109.138]
7 91 ms 108 ms 91 ms internap-gw.ip4.tinet.net [77.67.77.54]
8 92 ms 91 ms 90 ms border11.te7-1-bbnet1.bsn.pnap.net [63.251.128.4
1]
9 94 ms 91 ms 107 ms perfectworldent-4.border11.bsn.pnap.net [216.52.
61.78]
10 90 ms 91 ms 91 ms 208.95.185.41

Trace complete.

malcontentment · January 2013

trailturtle wrote: »

This should be fixed now. Thanks for your patience, everyone.

So... what was it?

Someone trip over a network cable?

trailturtle · January 2013

All told, it looks like it was a provider issue. One of the channels we use for players <-> patch servers had issues, and it took a while to both diagnose that and reroute traffic through the channels that still worked smoothly.

som3one1 · January 2013

Still having issues here sadly, same as the ones described in this thread.
Throwing in my tracert as well.

Tracing route to patchserver.crypticstudios.com [208.95.185.41]
over a maximum of 30 hops:

1 2 ms 1 ms 1 ms 192.168.1.1
2 28 ms 22 ms 42 ms ua-85-228-32-1.cust.bredbandsbolaget.se [85.228.32.1]
3 45 ms 62 ms 43 ms ti3200a210-pc3.ti.telenor.net [146.172.73.217]
4 55 ms 50 ms 33 ms ti3010d400-xe1-0-0.ti.telenor.net [146.172.80.249]
5 43 ms 35 ms 35 ms ti3001c310-ae11-0.ti.telenor.net [146.172.101.193]
6 84 ms 37 ms 33 ms ti0001c400-ae18-0.ti.telenor.net [146.172.98.46]
7 84 ms 66 ms 72 ms ti0001b400-ae1-0.ti.telenor.net [146.172.105.66]
8 37 ms 46 ms 57 ms tiscali-1.ti.telenor.net [148.122.9.10]
9 139 ms 137 ms 146 ms xe-3-0-0.bos11.ip4.tinet.net [141.136.109.138]
10 164 ms 143 ms 165 ms internap-gw.ip4.tinet.net [77.67.77.54]
11 161 ms 142 ms 144 ms border11.te7-1-bbnet1.bsn.pnap.net [63.251.128.41]
12 156 ms 163 ms 133 ms perfectworldent-4.border11.bsn.pnap.net [216.52.61.78]
13 138 ms 146 ms 147 ms 208.95.185.41

Trace complete.

trailturtle · January 2013

Hrm. Our network engineers are making a change to try to fix the channels in question -- stay tuned, heroes...

faredawg1 · January 2013

Was doing fine all morning. Now the launcher wont load again.

darkangel12893 · January 2013

ikr just went in powerhouse and its freaking doing the same thing as yesterday

jonsills · January 2013

The launcher's having problems at Cryptic. (Not for everyone, though, which makes it worse for the engineers...)

Blind Ferret's webcomic sites are all offline. They aren't sure why.

Peter David's blog has been reported as an "attack site" twice in the past week.

Wrong Planet has had to institute a browser check every time someone logs in, because they were getting hit with a spambot so bad it amounted to a DDoS attack. (Over 1000 new accounts per day for several days - at a site devoted to autism and Asperger's Syndrome.)

One of the users at SJGames' forums is trying to figure out why there's a massive spike in traffic to one particular page of his blog.

I'm going to assume it's all coincidence - for now...

ethanmorrigan · January 2013

Right now it goes on and off, sometimes it works, sometimes doesn't.

jonsills · January 2013

Aaaand now it's out here in western Washington state (which was apparently unaffected before). Hope the wires get untangled soon - I had to delete Captain Americlown (he's a Soldier AT, and my son's perseveration on guns is beginning to disturb people at school, so no guns around him even in games until his perseveration changes), and I'd finally found a decent Inuit word for "blizzard" ("piqsirpoq", Labrador Inuit) for a Canadian Glacier...

towershield · January 2013

I want to give Trailturtle and the engineers some props here for being on top of this issue. These selective outage type issues can be a massive pain to track down and diagnose.

I bought you guys a beer for all your hard work, once the issue is fixed I'll be knocking them back on your collective behalf.

jonsills · January 2013

Okay, it returned an error on the last two attempts, saying it was unable to connect to the Patch Server.

This last time, I got an IE page saying that it was unable to connect to the Internet (while I was online here with Firefox).

Sadly, I don't know how to run a traceroute, or I'd give you that data as well.

(You know, there are a couple of things I really ought to be doing instead of this anyway...)

nepht · January 2013

Yeah was trying to get my sister to play CO shes having the same issue.

neuraldamage · January 2013

Aaaaaand... it's back.

Dead in the water here. :mad:

Edit: Apparently the hamster is being tested.

Hello Captain! Please read this new notice, which is different from yesterday.

We are working with our external routing provider to run a few tests on the launcher so we can try to determine the cause for the outage yesterday -- this may cause some players to have an issue appear with the launcher, but please stand by. We hope to complete our testing ASAP -- it is our top priority. These tests will help us in implementing a resolution so we can avoid the issue from yesterday in the future. Again, not all players are affected, but if you are, please read this post.

Thanks you and we hope to have you back in-game ASAP.

- The Star Trek Online Community Team

http://sto-forum.perfectworld.com/showpost.php?p=7725421&postcount=85

deathsentry2012 · January 2013

Worked this morning and around lunch time (noon EST), but now..nada.. dead in the water..anyone at cryptic looking at this? anyone open up a ticket?

darkangel12893 · January 2013

im seriously bored right now lol nothing to do in a hospital bed =.=

darktempestgg · January 2013

I havent been able to login since monday afternoon, keeps saying error connectng to the patching server

Tracing route to patchserver.crypticstudios.com [208.95.185.41]
over a maximum of 30 hops:

3 123 ms 101 ms 103 ms 217.32.142.174
4 23 ms 101 ms 101 ms 212.140.206.202
5 119 ms 101 ms 101 ms 31.55.165.43
6 110 ms 101 ms 101 ms 31.55.165.107
7 114 ms 99 ms 101 ms 109.159.250.118
8 327 ms 54 ms 53 ms core1-te0-0-0-16.ealing.ukcore.bt.net [109.159.2
50.26]
9 220 ms 101 ms 102 ms core1-pos5-0-0.telehouse.ukcore.bt.net [194.74.6
5.122]
10 130 ms 100 ms 103 ms 166-49-211-157.eu.bt.net [166.49.211.157]
11 129 ms 100 ms 107 ms 166-49-211-38.eu.bt.net [166.49.211.38]
12 119 ms 208 ms 201 ms xe-1-2-0.bos11.ip4.tinet.net [89.149.183.13]
13 326 ms 199 ms 204 ms internap-gw.ip4.tinet.net [77.67.77.54]
14 119 ms 203 ms 203 ms border11.te7-1-bbnet1.bsn.pnap.net [63.251.128.4
1]
15 149 ms 162 ms 125 ms perfectworldent-4.border11.bsn.pnap.net [216.52.
61.78]
16 142 ms 205 ms 199 ms 208.95.185.41

Trace complete.

Now, I live in the UK and the internet connection im using at the minute isnt mine but I can connect to CO either way and I have tried all that has been suggested

#EDIT# litterally 2minutes after posting I was able to get on

trailturtle · January 2013

To my understanding, the change yesterday (shifting players to different patcher channels) was a pure band-aid, and can't be permanent. The work they've been doing today has been taking off the band-aid and trying to track down the issue; unfortunately, it doesn't look like they've found the fix. They'll be reverting to the status of last night, when it was functional for pretty much everyone, but probably a little slow.

Sorry for the inconvenience, folks, I know this is cutting into playing time.

jonsills · January 2013

Okay, I'm in now. I think I'll avoid disconnecting for a while, just in case...

knazzir · January 2013

trailturtle wrote: »

To my understanding, the change yesterday (shifting players to different patcher channels) was a pure band-aid, and can't be permanent. The work they've been doing today has been taking off the band-aid and trying to track down the issue; unfortunately, it doesn't look like they've found the fix. They'll be reverting to the status of last night, when it was functional for pretty much everyone, but probably a little slow.

Sorry for the inconvenience, folks, I know this is cutting into playing time.

STO just announced on twitter that they completed testing, they got data on how to try to avoid this happening again, and people should be able to log in now. If they figured it out, I would assume the ones working on this game would know as well, or am I wrong and the tech teams don't talk to each other?

trailturtle · January 2013

No, it's the same team working on it for both games. They did get data, they've completed testing for the day, and people should be able to log in now. If we're lucky, this data means that they can analyze what happened and just completely fix the issue, with no further issues visible. That depends on the solution being present in the data, though, so we won't know the final resolution until they've had time to analyze.

knazzir · January 2013

Thanks for clarifying that for me, Trailturtle, much appreciated.

redcapcoh · January 2013

trailturtle wrote: »

No, it's the same team working on it for both games. They did get data, they've completed testing for the day, and people should be able to log in now. If we're lucky, this data means that they can analyze what happened and just completely fix the issue, with no further issues visible. That depends on the solution being present in the data, though, so we won't know the final resolution until they've had time to analyze.

Great, whatever the tech guys did broke my launcher.
As soon as I click on "Play" it crashes.
"(null) has encountered an unexpected crash."

Assertion failed

Program: ...
SVN Revision: FC.31.20130110.9 (SVN 142075(http://code/svn/FightClub/Baselines/FC.31.20130110.0(branch svn = 142622)) Gimme 01101313:23:18)(+incrs)
Time: Wed Jan 30 08:58:36 AM
Process ID: 7080
File: c:\src\libs\utilitieslib\utils\error.c
Line: 363
Expression: 0

Error Message: Unable to create hogg file! : 

  0 GameClient.exe!00d368b1 (0,a6ae70,0,2800)SymGetSymFromAddr(): gle = 487
		Line: --- (0)
		Module: GameClient.exe
  1 GameClient.exe!00c109e2 (0,2007acc,0,5bc34c1)SymGetSymFromAddr(): gle = 487
		Line: --- (0)
		Module: GameClient.exe
  2 GameClient.exe!00c46f9e (0,4cfd9fc,0,0)SymGetSymFromAddr(): gle = 487
		Line: --- (0)
		Module: GameClient.exe
  3 GameClient.exe!00c482c1 (0,4cfd9fc,0,1)SymGetSymFromAddr(): gle = 487
		Line: --- (0)
		Module: GameClient.exe
  4 GameClient.exe!00c47f89 (0,4cfd9fc,0,1)SymGetSymFromAddr(): gle = 487
		Line: --- (0)
		Module: GameClient.exe
  5 GameClient.exe!00c483d4 (0,205ae74,0,a6d830)SymGetSymFromAddr(): gle = 487
		Line: --- (0)
		Module: GameClient.exe
  6 GameClient.exe!00d240cd (0,2,0,a6e8f4)SymGetSymFromAddr(): gle = 487
		Line: --- (0)
		Module: GameClient.exe
  7 GameClient.exe!00d359dd (0,a6ead4,0,0)SymGetSymFromAddr(): gle = 487
		Line: --- (0)
		Module: GameClient.exe
  8 GameClient.exe!00d2fe89 (0,a6ead4,0,0)SymGetSymFromAddr(): gle = 487
		Line: --- (0)
		Module: GameClient.exe
  9 GameClient.exe!00d3a88e (0,0,0,0)SymGetSymFromAddr(): gle = 487
		Line: --- (0)
		Module: GameClient.exe
 10 GameClient.exe!00d3ae9e (0,a6eec4,0,17e8403)SymGetSymFromAddr(): gle = 487
		Line: --- (0)
		Module: GameClient.exe
 11 GameClient.exe!00c98bff (0,5bb6c30,0,0)SymGetSymFromAddr(): gle = 487
		Line: --- (0)
		Module: GameClient.exe
 12 GameClient.exe!00c88403 (0,0,0,0)SymGetSymFromAddr(): gle = 487
		Line: --- (0)
		Module: GameClient.exe
 13 GameClient.exe!00c88f47 (0,0,0,0)SymGetSymFromAddr(): gle = 487
		Line: --- (0)
		Module: GameClient.exe
 14 GameClient.exe!00c896c9 (0,0,0,0)SymGetSymFromAddr(): gle = 487
		Line: --- (0)
		Module: GameClient.exe
 15 GameClient.exe!00c876ee (0,0,0,0)SymGetSymFromAddr(): gle = 487
		Line: --- (0)
		Module: GameClient.exe
 16 GameClient.exe!0009739c (0,29e91d8,0,2c25b70)SymGetSymFromAddr(): gle = 487
		Line: --- (0)
		Module: GameClient.exe
 17 GameClient.exe!0051269a (0,b60000,0,0)SymGetSymFromAddr(): gle = 487
		Line: --- (0)
		Module: GameClient.exe
 18 GameClient.exe!013092b2 (0,a6f7b8,0,75a98543)SymGetSymFromAddr(): gle = 487
		Line: --- (0)
		Module: GameClient.exe
 19 GameClient.exe!0130915f (0,7e998000,0,a6f7fc)SymGetSymFromAddr(): gle = 487
		Line: --- (0)
		Module: GameClient.exe
 20 BaseThreadInitThunk (7e998000,0,18d9c180,0)
		Line: --- (0)
		Module: KERNEL32.DLL
 21 RtlInitializeExceptionChain (1e69150,0,7e998000,0)
		Line: --- (0)
		Module: ntdll.dll
 22 RtlInitializeExceptionChain (1e69150,0,7e998000,0)
		Line: --- (0)
		Module: ntdll.dll

Heap is NOT corrupted
No windows SYSTEM error code found.

deisticbrace · January 2013

Dayum, son. Looks like the Great White North got hit with this too. Especially hard since like, every one of those hops timed out. Oh, Toronto, Canada for this report.

Microsoft Windows [Version 6.0.6002]
Copyright (c) 2006 Microsoft Corporation. All rights reserved.

C:\Windows\system32>tracert patchserver.crypticstudios.com

Tracing route to patchserver.crypticstudios.com [208.95.185.41]
over a maximum of 30 hops:

1 * * * Request timed out.
2 * * * Request timed out.
3 * * * Request timed out.
4 * * * Request timed out.
5 * * * Request timed out.
6 * * * Request timed out.
7 * * * Request timed out.
8 * * * Request timed out.
9 * * * Request timed out.
10 * * * Request timed out.
11 * * * Request timed out.
12 * * * Request timed out.
13 * * * Request timed out.
14 41 ms 41 ms 41 ms 208.95.185.41

Trace complete.

C:\Windows\system32>

drgmstr · January 2013

trailturtle wrote: »

No, it's the same team working on it for both games. They did get data, they've completed testing for the day, and people should be able to log in now. If we're lucky, this data means that they can analyze what happened and just completely fix the issue, with no further issues visible. That depends on the solution being present in the data, though, so we won't know the final resolution until they've had time to analyze.

Can't just yet. Still getting unable to display page error messages and a trying to update launcher window with 6 failed attempts before popping up a warning about connection issues.

flamingbunnyman · January 2013

deisticbrace wrote: »

Dayum, son. Looks like the Great White North got hit with this too. Especially hard since like, every one of those hops timed out. Oh, Toronto, Canada for this report.

I'm in Kelowna, BC, Canada. For the heck of it, I did a tracert too.

Tracing route to patchserver.crypticstudios.com [208.95.185.41]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  192.168.0.1
  2    21 ms    37 ms    62 ms  11.4.0.1
  3    70 ms    10 ms     7 ms  64.59.168.242
  4    13 ms    13 ms     9 ms  rd2ht-tge2-1.ok.shawcable.net [66.163.72.162]
  5    29 ms    22 ms    22 ms  66.163.76.58
  6   215 ms    54 ms    48 ms  rc4wt-pos15-0-0.wa.shawcable.net [66.163.76.210]

  7    25 ms    28 ms    22 ms  xe-11-0-0.edge1.Seattle3.Level3.net [4.59.232.85
]
  8   221 ms    23 ms    42 ms  ae-23-52.car3.Seattle1.Level3.net [4.69.147.165]

  9    54 ms   364 ms   194 ms  sprint-level3-te.Seattle1.Level3.net [4.68.63.34
]
 10    66 ms    29 ms   313 ms  sl-crs2-tac-.sprintlink.net [144.232.1.154]
 11   126 ms    77 ms   100 ms  sl-crs2-chi-0-3-5-0.sprintlink.net [144.232.19.1
04]
 12   427 ms   220 ms    86 ms  sl-crs2-akr-0-3-3-0.sprintlink.net [144.232.20.1
86]
 13   350 ms    97 ms    97 ms  sl-crs2-spr-0-4-5-0.sprintlink.net [144.232.18.1
09]
 14   106 ms    96 ms    95 ms  sl-st20-bos-0-0-0.sprintlink.net [144.232.8.48]

 15   106 ms   387 ms   230 ms  sl-internap-190725-0.sprintlink.net [144.223.45.
50]
 16   180 ms   220 ms    99 ms  border11.te7-1-bbnet1.bsn.pnap.net [63.251.128.4
1]
 17   118 ms   106 ms   107 ms  perfectworldent-4.border11.bsn.pnap.net [216.52.
61.78]
 18     *        *        *     Request timed out.
 19     *        *        *     Request timed out.
 20     *        *        *     Request timed out.
 21     *        *        *     Request timed out.
 22     *        *        *     Request timed out.
 23     *        *        *     Request timed out.
 24     *        *        *     Request timed out.
 25     *        *        *     Request timed out.
 26     *        *        *     Request timed out.
 27     *        *        *     Request timed out.
 28     *        *        *     Request timed out.
 29     *        *        *     Request timed out.
 30     *        *        *     Request timed out.

Trace complete.

Looks like it got as far as one of PW's servers before crapping out. Funny that every time it fails, it tells ME to check MY internet connection.

ethanmorrigan · January 2013

And again i can say the same, no sucessful launcher update, always connection error.

meedacthunist · January 2013

Doing standard maintenace and breaking connection for good.

Cryptic.

cyberzubzeroi · January 2013

STart the SErverrrrrr!!!:))))))))))))))

jonsills · January 2013

flamingbunnyman wrote: »

Looks like it got as far as one of PW's servers before crapping out. Funny that every time it fails, it tells ME to check MY internet connection.

Well, it's not like you can check Cryptic's internet connection...

trailturtle · January 2013

Launcher seems to be working now. Regular maintenance should proceed apace, if I understand properly.

CO Launcher not loading

Comments