Page 1 of 1

Posted: Thu Apr 17, 2008 2:08 am
by Trigger1969
Ok, I haven't played in a couple weeks. After an ASGS update, I'd crash immediately following login. Checked Helpline and saw pinned thread about installing on main system drive. Uninstalled and reinstalled on System Drive. ASGS loaded and completed update (multiple). Logged in fine and entered Allegiance where auto update took over and did its thing. When update was finished, ASGS crashed out with error code: x5c9b035fed62d487 . Everytime I login now It crashes with same error as it begins to launch. Copied console:

• Initializing
• Reading Settings
• Logging Option: SIMPLE
• Loading MRU Callsigns
• Loading Form Position
• Checking Installation
• Checking OOBE
• Ready
• Checking for system updates
• Checking for existing processes
• Saving Settings
• Saving MRU Callsigns
• Checking connectivity
• Using Port: DirectPlay
• Checking ASGS Client Version
• Client Version: 165
• Server Version: 165
• Securing Installation
• Validating Installation
• Preparing Key
• Key Generated
• Connecting to ASGS Server
• Authenticating
• Ticket Received
• Return Value: 0
• Callsign: Trigger_(14)
• Authenticated successfully
• Checking messages
• Return Value: 0
• No messages
• Checking polls
• Return Value: 0
• No polls
• Logged In
• Launching Allegiance
• Active
• Allegiance exited with code: x5c9b035fed62d487
• Creating Crashfile
• Beginning Logout
• Closing processes
• Sending Logout Request
• Logged Out


Windows Version (and Service Packs): Windows XP pro
Processor Speed: AMD Athlon 64 X2 Dual 2.0GHz
RAM: 1 gig
Video Card (Make and Model#): Diamond Viper x1300
Sound Card (Make and Model#): Onboard Realtek AC97
Connection Type (Dialup, Cable, DSL, other): WDSL
Modem (Make and Model#): N/A
Router (Make and Model#): Belkin
Internet Service Provider(company name): Internet Texoma
Location(State/Province/Locality, and Country):Texas, USA
Installed Mods: None

Problem Encountered at Step #: (read the "What Should Happen" for this step#)
Which Program (ASGS/Allegiance):
What Error Message:
Comments (What you tried, description, etc):
Described above

Posted: Thu Apr 17, 2008 2:15 am
by w0dk4
I have the exact same error. Glad Im not alone.

QUOTE ASGS crashed out with error code: x5c9b035fed62d487[/quote]

Surely you mean Allegiance here /wink.gif" style="vertical-align:middle" emoid=";)" border="0" alt="wink.gif" />

Posted: Thu Apr 17, 2008 2:18 am
by Dogbones
Have you tried the "Update / repair critical files" option in ASGS?
It is under Help in the ASGS gui.

Edit: Note I have noticed the new ASGS always gets the allegiance.exe client regardless if it just downloaded it or not.

Posted: Thu Apr 17, 2008 2:26 am
by Trigger1969
Dogbones wrote:QUOTE (Dogbones @ Apr 16 2008, 09:18 PM) Have you tried the "Update / repair critical files" option in ASGS?
It is under Help in the ASGS gui.

Edit: Note I have noticed the new ASGS always gets the allegiance.exe client regardless if it just downloaded it or not.
Just tried... no effect. That reminded me though. After reinstalling on my system drive and completing the ASGS update. After 1st Login, I received a corrupt file (or similar) error and allowed it to be fixed. don't know if this is relevant or not.

Also, w0dk4 is correct that ASGS doesn't crash out, alleg does. ASGS just is still up.

Posted: Fri Apr 18, 2008 12:28 am
by Trigger1969
Ok, my thread was ignored but you can close it as I solved the problem...

Posted: Fri Apr 18, 2008 3:59 am
by ImmortalZ
And how did you solve it? This is a new error that we are not familiar with.

Posted: Fri Apr 18, 2008 4:43 am
by Trigger1969
I don't know if it had anything to do with it, but I used an old installer that I had when I reinstalled. I downloaded a new copy of the downloader and reinstalled again. Came up with no problems. If nothing has changed with the installer, then it was just a bad install originally. I made an assumption that the installer would not have changed, only the program, but it looks like it has. My mistake. *slaps self*

Posted: Fri Apr 18, 2008 7:06 am
by ImmortalZ
Ah, a possible corrupt file or registry entry. Thanks for the info. Closing this.