Page 1 of 2

Posted: Tue May 05, 2009 6:08 am
by Catwiesel
Windows Version (and Service Packs): Windows XP (32bit) SP2
Processor Speed: AMD X2 5000+
RAM: 2GB
Video Card (Make and Model#): ATI HD3870
Sound Card (Make and Model#): Creative Audigy
Connection Type (Dialup, Cable, DSL, other): DSL (6mbit)
Modem (Make and Model#): AVM DSL Card
Router (Make and Model#): NONE
Internet Service Provider(company name): T-Online
Location(State/Province/Locality, and Country): Germany
Installed Mods: CortUI

Make and Version of firewall: NONE
- windows firewall deactivated
- external router, NAT enabled (automatically forwards ports)


Make and version of anti-virus:
- Avira AntiVir Personal

Confirm that you have the following installed:
.Net 2.0 [x] It is


Problem Encountered at Step #: 6 to 7
Which Program (ASGS/Allegiance): Allegiance

What Error Message: AutoUpdate Error

Comments (What you tried, description, etc):

Alright, Allegiance worked 2 hours ago, I was playing the whole night. I was taking a break, watching TV, closed it and restarted it a few minutes later to see if my rank did get back up.
After step 6 where the MOTD usually loads the AutoUpdate window opens up, but it does not update. After a few minutes waiting (where Allegiance uses so many CPU power I hardly can move the mouse curser) an error is shown:

AutoUpdate Error
Try again later. As a last resort you may want to reinstall.

See UpdateError.txt for details.

The UpdateError.txt reads as follows:
"Update attempt at: 5/5/09 at 7:38:18 (local time)
Failed to open file for download.(12029) "

Thats it, nothing more will happen and I am guessing because it can not update I dont get the MOTD and can not list the games.

I tried manually forwarding the port on TCP and UDP assuming that is the right one (12029)
I also tried setting my computer/local IP as NAT server so all packets will be forwarded to me.
Both did not have the desired effect.

I then proceeded to try a Update/Repair Critcal Files from withing asgs2.2 which itself worked and tried to get into allegiance without success.

So was there an update the last few hours? Is it working for everybody else? Maybe the problem is not on my end and if it is has someone an idea how to get the update working or manually update the files?

Thanks in advance
Catwiesel

EDIT: While I was posting this thread someone else did the same and it appears I am not the only one with the problem. So no need to reply, I will wait for the cure :)

Posted: Tue May 05, 2009 6:13 am
by Andarvi
Ok, let me write this more clearly:

The problem is probably server side. Don't do anything to your local install (reinstall, try to patch manually etc.) until you read you have to on these boards. Your local install is fine if it worked up to now.

Posted: Tue May 05, 2009 6:15 am
by Jagnara
although it may sound a bit sadistic, im glad someone else is having problems with this as well.
:innocent:

Posted: Tue May 05, 2009 6:21 am
by Catwiesel
Andarvi wrote:QUOTE (Andarvi @ May 5 2009, 05:13 PM) Ok, let me write this more clearly:

The problem is probably server side. Don't do anything to your local install (reinstall, try to patch manually etc.) until you read you have to on these boards. Your local install is fine if it worked up to now.
No question about that! I was just wondering if
a) there is an update needed but not working correctly atm or
b) there is an update which works for everyone else and I have to somehow get it to work for myself (better router settings) or
c) there is NO update needed BUT everytime you open alleg it needs to check for updates and that is broken (not on client side) and we ALL need to wait

looks like a or c to me and since I cant do anything about that, well I am not concerned, or tempted to reinstall everything (which btw WILL definately need an autoupdate) but will just wait for it to work again.

But thank you all for answering so quickly. must be the alleg downtime, everyone on forum :)

Oh and without being sadistic in any way, I am also glad we all are affected. Means it aint my fault! :D

Posted: Tue May 05, 2009 12:00 pm
by Tigereye
I must have broke autoupdate last night when publishing cc_04. Sorry.
I'm on my blackberry now, so can't investigate properly. I'll get this fixed asap.

Let's blame spidey because it's clearly his fault since he administers autoupdate.
;)

-TE

Posted: Tue May 05, 2009 12:04 pm
by Icky
He's in place for like a week and already things are breaking!

Posted: Tue May 05, 2009 1:04 pm
by Tigereye
Can someone please try again and let me know if it is still broken?
I just made a change immediately before this post.

Thanks,

--TE

Posted: Tue May 05, 2009 1:15 pm
by TheCorsair
As of this post. Same issue.

Posted: Tue May 05, 2009 1:18 pm
by stressed
Tigereye wrote:QUOTE (Tigereye @ May 5 2009, 06:04 AM) Can someone please try again and let me know if it is still broken?
I just made a change immediately before this post.

Thanks,

--TE

Not working. Try again.

Posted: Tue May 05, 2009 1:23 pm
by Tigereye
Wow found the problem (I think)

This is the first push of a new core since the new server, and it seems when migrating everything to the new server, I missed one small little file that's used in the autoupdate process.

Let me know if it works as of this post.

Thanks for testing for me. I'm in a remote location without the game installed.

--TE