After installing new patch test server not working
By
Ad Astra,
Posted on: 2009-06-09 15:10 in The Global Training Room Test Server
This happend to me also, after like 5 mins it worked.
Not sure whats causing it, tho.
For many of us, any fixes seem to be rather hit or miss, and there seem to be several varieties of problem floating around. For instance, on my initial attempt to log in it downloaded the patch, and then proceeded to try to fix 'tempfile', which it wanted to take two hours to do. I closed the updater, deleted my checksum, and then verified...and got in. However, when I tried to go back in 2 hours later, it tried the same thing again...and deleting the checksum file hasn't gotten me in. Nor can I find a 'tempfile' in the root game folder, or anywhere at all in fact, to try deleting.
The other thread on this can be found here.
Same issue here. Glad to know it's not just me.
Fixing files now after copying piggs over from live. Created shortcut and ready to bypass.
Thanks for the help gang! It was gonna take 8 hours to download the whole game again!
Neutron-Star
lvl 50 Inv/EM tank
Looks like in addition to the missing pigg files in the pigg directory all the dlls in the game root directory have been removed by the updater. Copying from live client seems to work, but verifying may delete some files again.
I suspect a Nemesis plot to prevent us from testing doms...
If somebody you're arguing with goes off the deep end, don't follow.
Haven't tried anything yet but I am glad to not be the only one though.
Edit: Are the Devs going to do anything to fix this?
"Yes, winning all the time can be boring."
-Knight_Chill
"It's amazing how well you can put up with endurance issues if you hide them under a large enough pile of bodies."
-Spiritchaser speaking on Dom Revamp
awesome first they deleted toons now they delete the game!
I lol'd.
@macskull, @Not Mac | XBL: macskull | Steam: macskull | Skype: macskull
"One day we all may see each other elsewhere. In Tyria, in Azeroth. We may pass each other and never know it. And that's sad. But if nothing else, we'll still have Rhode Island."
"One day we all may see each other elsewhere. In Tyria, in Azeroth. We may pass each other and never know it. And that's sad. But if nothing else, we'll still have Rhode Island."
[ QUOTE ]
Haven't tried anything yet but I am glad to not be the only one though.
Edit: Are the Devs going to do anything to fix this?
[/ QUOTE ]
Nope. They're going to let it continue, so that when Issue 15 goes live almost no one can get on unless they manually fix their own game, and even then it won't work 100% of the time.
Sheesh. OF COURSE they're going to fix it. That's what they have a Test Server for, so that when something catastrophically wrong like this happens they can fix it before it gets to the Live Servers.
considering that this patch basically killed my test client i would assume when THIS patch comes live we won't be able to play for a week............and don't tell me they gonna fix it, maybe they will on test but shold i remind you all the crashes that happen every new issue?
[ QUOTE ]
considering that this patch basically killed my test client i would assume when THIS patch comes live we won't be able to play for a week............and don't tell me they gonna fix it, maybe they will on test but shold i remind you all the crashes that happen every new issue?
[/ QUOTE ]
Crashes, lag, yes, of course new issues have problems. But there's no way they'll let a patch go live that literally destroys nearly all game files.
becuase there are so many posts from them waring users about it or even telling us it is happening...
I let the test server download run. It downloaded about 700MB worth of files and claimed it was ready to go. I copied the piggs folder from live to test directory (did not replace any existing files) and ran the updater again, at which point the launcher fired up and... connected to live. I'm downloading a completely new copy now, from scratch, and am hoping that fixes it.
@macskull, @Not Mac | XBL: macskull | Steam: macskull | Skype: macskull
"One day we all may see each other elsewhere. In Tyria, in Azeroth. We may pass each other and never know it. And that's sad. But if nothing else, we'll still have Rhode Island."
"One day we all may see each other elsewhere. In Tyria, in Azeroth. We may pass each other and never know it. And that's sad. But if nothing else, we'll still have Rhode Island."
[ QUOTE ]
I let the test server download run. It downloaded about 700MB worth of files and claimed it was ready to go. I copied the piggs folder from live to test directory (did not replace any existing files) and ran the updater again, at which point the launcher fired up and... connected to live. I'm downloading a completely new copy now, from scratch, and am hoping that fixes it.
[/ QUOTE ]
I did that overnight, and it acted like it was downloading or rather it said fixing all the files. But when I tried it this morning it did the same crash and error report after I hit 'next' after launching the mac test client.
[ QUOTE ]
I let the test server download run. It downloaded about 700MB worth of files and claimed it was ready to go. I copied the piggs folder from live to test directory (did not replace any existing files) and ran the updater again, at which point the launcher fired up and... connected to live. I'm downloading a completely new copy now, from scratch, and am hoping that fixes it.
[/ QUOTE ]
If you run the updater directly (double clicking the .exe) then you'll get live cause you're not using the -test switch that's in the updater shortcut.
Once you get a complete game folder don't run the updater again. Use the updater bypass method.
I didn't get a DLL error until I tried one of the fixes mentioned in either this or another thread - previously I'd be able to launch the test updater just fine but after I clicked "next" nothing would happen - no loading splash screen, no "CityOfHeroes.exe" process... nothing.
@macskull, @Not Mac | XBL: macskull | Steam: macskull | Skype: macskull
"One day we all may see each other elsewhere. In Tyria, in Azeroth. We may pass each other and never know it. And that's sad. But if nothing else, we'll still have Rhode Island."
"One day we all may see each other elsewhere. In Tyria, in Azeroth. We may pass each other and never know it. And that's sad. But if nothing else, we'll still have Rhode Island."
The thing is that we shouldn't have to do these workarounds. They should pull whatever caused this problem. Fix it. Then republish. They should also acknowledge that there is a problem and make some sort of statement about what they are doing to correct the issue. At the very least just say "We are aware and working on a fix. Please be patient. ETA for fix is(whenever)"
Just my 2 enfamy and that ain't worth much. 
[ QUOTE ]
The thing is that we shouldn't have to do these workarounds. They should pull whatever caused this problem. Fix it. Then republish. They should also acknowledge that there is a problem and make some sort of statement about what they are doing to correct the issue. At the very least just say "We are aware and working on a fix. Please be patient. ETA for fix is(whenever)"
Just my 2 enfamy and that ain't worth much.
[/ QUOTE ]
^^this
[ QUOTE ]
becuase there are so many posts from them waring users about it or even telling us it is happening...
[/ QUOTE ]
But then, it's not live.
Orc&Pie No.53230 There is an orc, and somehow, he got a pie. And you are hungry.
www.repeat-offenders.net
Negaduck: I see you found the crumb. I knew you'd never notice the huge flag.
[ QUOTE ]
The thing is that we shouldn't have to do these workarounds. They should pull whatever caused this problem. Fix it. Then republish. They should also acknowledge that there is a problem and make some sort of statement about what they are doing to correct the issue. At the very least just say "We are aware and working on a fix. Please be patient. ETA for fix is(whenever)"
Just my 2 enfamy and that ain't worth much.
[/ QUOTE ]
Boo hoo closed beta 
Orc&Pie No.53230 There is an orc, and somehow, he got a pie. And you are hungry.
www.repeat-offenders.net
Negaduck: I see you found the crumb. I knew you'd never notice the huge flag.
Good point ,Leech. However can you imagine the outcry if it was live? This needs to be corrected ASAP regardless that its on test server.
[ QUOTE ]
Good point ,Leech. However can you imagine the outcry if it was live? This needs to be corrected ASAP regardless that its on test server.
[/ QUOTE ]
Do you really think they're just sitting there in the office reading this thread and the many others, and just laughing at us instead of fixing? They need to first figure out what the problem is before they attempt to fix, so until they do that, we're not going to hear anything from them.
Loose --> not tight.
Lose --> Did not win, misplace, cannot find, subtract.
One extra 'o' makes a big difference.
You got PMS or something, HotFlash? No need to be rude or catty. Please do not presume to tell me what I think.
The point is the problem with the updater has been out since the last patch. Thats well over 24 hours and there still has not even been an official recognition that a problem does exist.Communication is key.Communication is also a common courtesy. 
I don't think the customer base expecting the bare minimum is too much to ask.
Thats what I think.
[ QUOTE ]
You got PMS or something, HotFlash? No need to be rude or catty. Please do not presume to tell me what I think.
The point is the problem with the updater has been out since the last patch. Thats well over 24 hours and there still has not even been an official recognition that a problem does exist.Communication is key.
[/ QUOTE ]
I would think that the many threads about it, with more than a few people with a problem, should be warning enough that something is amiss, but then I'm one of the people that actually pays attention to things in the forums. Would you be satisfied with a "Yes, we're aware it's broken, and no, we don't have a solution yet, sorry" response? That's all you're really going to get at this point, because, as you said, it's only been 24 hours, and most of that time people haven't been at work.
Loose --> not tight.
Lose --> Did not win, misplace, cannot find, subtract.
One extra 'o' makes a big difference.
[ QUOTE ]
[ QUOTE ]
The thing is that we shouldn't have to do these workarounds. They should pull whatever caused this problem. Fix it. Then republish. They should also acknowledge that there is a problem and make some sort of statement about what they are doing to correct the issue. At the very least just say "We are aware and working on a fix. Please be patient. ETA for fix is(whenever)"
Just my 2 enfamy and that ain't worth much.
[/ QUOTE ]
^^this
[/ QUOTE ]
Agreed.
I'm still having major major problems logging on as well, and I keep getting similar errors trying to "load in" that everyone else is getting. So far, none of the "work-arounds" have "worked" so far either..
Devs? Ya guys wanna fix this soon...or what??!? 
[ QUOTE ]
Hasn't worked for me so far. I get constant crashes when the game tries to launch still.
[/ QUOTE ]
Verify that your CohTest folder is something like 2.8 - 3.1 GBs. If it's only a few hundred megabytes then you need to use Zombie's suggestion and copy over the pigg folder from your live folder.
When doing this DO NOT overwrite the existing pigg files in the CohTest folder. Then try using the updater bypass method I outlined.