Free Allegiance Forums

Original post:

I've searched through the forums, and I can't seem to find a solution to this problem. If there already is one, I apologize.


When I fire up ASGS and log in, as it goes through all the stuff it does as it's logging in, it gets to the "Launching Allegiance" part... and does nothing. No error message, no crashing, no nothing. It just keeps going through the starting process and ends at the check ins.


I already have the .NET framework, I'm not sitting behind a router, all of the connection options should be perfect, it just won't launch the game.


Any help would be appreciated, I'm getting tired of the training missions /glare.gif" style="vertical-align:middle" emoid=":glare:" border="0" alt="glare.gif" />

-----------------------------------------------------------------------------------------------------------------------------


I've already reinstalled both Allegiance and the .NET v1.1 framework, I've tried launching Allegiance manually once ASGS is running, I've checked the task manager to see if Allegiance was running in the backround, etc etc etc. Still no solution yet

Ok, launching Allegiance manually once ASGS is running just gives me the "ASGS Authenication Failed" error /mad.gif" style="vertical-align:middle" emoid=":mad:" border="0" alt="mad.gif" />

Blah, I give up. I'll just play on the Beta servers

1) AMke sure your Firewall isn't blocking ports 2300-2400. If you are using Windows Firewall make sure that you have allowed Allegiance as an exception.

2) Forum account and ASGS are not the same ... When you first join ASGS you need to create a new callsign.

The only time I've seen ASGS fail to launch Allegiance is when ASGSClient.exe and Allegiance.exe were not in the same directory.

Since the installer puts them together by default, that means you would of had to move them... which you should not do.

There have been occasional problems in the past when people install to other than the default, although most of those were corrected in later releases. Just to be safe, uninstall, and then reinstall leave everything set to the defaults.

beauty wrote:QUOTE (beauty @ Jul 2 2006, 12:30 PM) 1) AMke sure your Firewall isn't blocking ports 2300-2400. If you are using Windows Firewall make sure that you have allowed Allegiance as an exception.

2) Forum account and ASGS are not the same ... When you first join ASGS you need to create a new callsign.

1) Not behind a firewall. Not using a router.

2) I'm aware of that.

Pook wrote:QUOTE (Pook @ Jul 2 2006, 12:36 PM) The only time I've seen ASGS fail to launch Allegiance is when ASGSClient.exe and Allegiance.exe were not in the same directory.

Since the installer puts them together by default, that means you would of had to move them... which you should not do.

There have been occasional problems in the past when people install to other than the default, although most of those were corrected in later releases. Just to be safe, uninstall, and then reinstall leave everything set to the defaults.

Already did that, they're in the same directory.



Also, thought it might help if I posted a log.

7/2/2006 3:10:39 PM: Initializing
7/2/2006 3:10:40 PM: Reading Settings
7/2/2006 3:10:40 PM: Logging Option: OFF
7/2/2006 3:10:44 PM: WARNING: Debug logging is resource intensive.
7/2/2006 3:10:45 PM: Checking for system updates
7/2/2006 3:10:45 PM: Checking for existing processes
7/2/2006 3:10:45 PM: Saving Settings
7/2/2006 3:10:45 PM: Saving MRU Callsigns
7/2/2006 3:10:47 PM: Checking connectivity
7/2/2006 3:10:47 PM: Using Port: DirectPlay
7/2/2006 3:10:48 PM: Checking ASGS Client Version
7/2/2006 3:10:48 PM: Client Version: 120
7/2/2006 3:10:48 PM: Server Version: 120
7/2/2006 3:10:48 PM: Securing Installation
7/2/2006 3:10:49 PM: Validating Installation
7/2/2006 3:10:50 PM: Preparing Key
7/2/2006 3:10:50 PM: Key Generated
7/2/2006 3:10:50 PM: Connecting to ASGS Server
7/2/2006 3:10:50 PM: Authenticating
7/2/2006 3:10:51 PM: Ticket Received
7/2/2006 3:10:51 PM: Return Value: 0
7/2/2006 3:10:51 PM: Callsign: Tyrin@CDT-B(0)
7/2/2006 3:10:51 PM: Authenticated successfully
7/2/2006 3:10:51 PM: Checking messages
7/2/2006 3:10:51 PM: Return Value: 0
7/2/2006 3:10:51 PM: No messages
7/2/2006 3:10:51 PM: Checking polls
7/2/2006 3:10:52 PM: Return Value: 0
7/2/2006 3:10:52 PM: No polls
7/2/2006 3:10:52 PM: Logged In
7/2/2006 3:10:52 PM: Launching Allegiance
7/2/2006 3:11:07 PM: Active
7/2/2006 3:11:20 PM: Saving Form Position
7/2/2006 3:11:20 PM: Beginning Logout
7/2/2006 3:11:20 PM: Closing processes
7/2/2006 3:11:20 PM: Sending Logout Request
7/2/2006 3:11:20 PM: Logged Out
7/2/2006 3:11:20 PM: Exiting

Looks to me more like Allegiance is starting up and then immediately closing. It woudln't take 15+ seconds to do "nothing" and if ASGS fails to find an "Allegiance.exe" process when it tries to start it up, it actually reports it and says "Failed to Launch Allegiance".

Watch your task manager, sort it alphabetically. I bet that Allegiance.exe will appear for a few seconds and then disappear when you login.

Also - I notice that you have debug logging on.

You should find some debug logs that ASGS has been spitting out... chances are that they'll show an Allegiance crash at startup problem as well.

Nope, Allegiance doesn't show up in the task manager. Also, all the debug logs I have are the same, almost letter for letter (time and dates being the exception).

what you posted is ASGS's console output.

In the ASGS directory you'll find a DEBUG log file that has a whole lot of stuff that Allegiance itself is reporting.

Negative on the Allegiance debug logs, all I have is the asgs_debug.log file, and a list of files that were updated the first time I ran Allegiance.