Windows Version (and Service Packs): vista home premium
Processor Speed: amd athlon 64 x 2 dual core 4200 ~2.2ghz
RAM: 2046 mb
Video Card (Make and Model#): radeon x850
Sound Card (Make and Model#): realtek digital output hd
Connection Type (Dialup, Cable, DSL, other): dsl
Modem (Make and Model#): motorola sbv5121xm
Router (Make and Model#): none
Internet Service Provider(company name): optimum online
Location(State/Province/Locality, and Country): ny usa
Installed Mods: none
Make and Version of firewall: windows
Make and version of anti-virus: none
Confirm that you have the following installed:
* .Net 2.0 [X]
Problem Encountered at Step #: (read the "What Should Happen" for this step#) 5
Which Program (ASGS/Allegiance):allegiance
What Error Message: non specific failed to launch needs to close will notify of fix if found
Comments (What you tried, description, etc): i have it in win 2003. and did manual updates also tried running in xp. when game launches it launched windowed then crashes. i also tried downloading the dotnetfix program. now i get what appears to be game launching full screen for 1-2 secs then goes to windowed for a few seconds and ctd.
...<your comments here>...
ctd after login
3/12/2010 1:29:23 PM: Initializing
3/12/2010 1:29:23 PM: Reading Settings
3/12/2010 1:29:23 PM: Logging Option: SIMPLE
3/12/2010 1:29:23 PM: Loading MRU Callsigns
3/12/2010 1:29:23 PM: Loading Form Position
3/12/2010 1:29:23 PM: Checking Installation
3/12/2010 1:29:23 PM: Checking OOBE
3/12/2010 1:29:23 PM: Ready
3/12/2010 1:29:24 PM: Checking for system updates
3/12/2010 1:29:24 PM: Checking for existing processes
3/12/2010 1:29:24 PM: Saving Settings
3/12/2010 1:29:24 PM: Saving MRU Callsigns
3/12/2010 1:29:25 PM: Checking connectivity
3/12/2010 1:29:25 PM: Using Port: DirectPlay
3/12/2010 1:29:28 PM: Checking ASGS Client Version
3/12/2010 1:29:28 PM: Client Version: 212
3/12/2010 1:29:28 PM: Server Version: 210
3/12/2010 1:29:28 PM: Securing Installation
3/12/2010 1:29:28 PM: Validating Installation
3/12/2010 1:29:29 PM: Preparing Key
3/12/2010 1:29:29 PM: Key Generated
3/12/2010 1:29:29 PM: Connecting to ASGS Server
3/12/2010 1:29:29 PM: Authenticating
3/12/2010 1:29:30 PM: Ticket Received
3/12/2010 1:29:30 PM: Return Value: 0
3/12/2010 1:29:30 PM: Callsign: moglery(0)
3/12/2010 1:29:30 PM: Authenticated successfully
3/12/2010 1:29:30 PM: Checking messages
3/12/2010 1:29:31 PM: Return Value: 0
3/12/2010 1:29:31 PM: No messages
3/12/2010 1:29:31 PM: Checking polls
3/12/2010 1:29:31 PM: Return Value: 0
3/12/2010 1:29:31 PM: No polls
3/12/2010 1:29:31 PM: Logged In
3/12/2010 1:29:31 PM: Launching Allegiance
3/12/2010 1:29:32 PM: Active
3/12/2010 1:29:44 PM: Allegiance exited with code: EXCEPTION_ACCESS_VIOLATION
3/12/2010 1:29:44 PM: Creating Crashfile
3/12/2010 1:29:23 PM: Reading Settings
3/12/2010 1:29:23 PM: Logging Option: SIMPLE
3/12/2010 1:29:23 PM: Loading MRU Callsigns
3/12/2010 1:29:23 PM: Loading Form Position
3/12/2010 1:29:23 PM: Checking Installation
3/12/2010 1:29:23 PM: Checking OOBE
3/12/2010 1:29:23 PM: Ready
3/12/2010 1:29:24 PM: Checking for system updates
3/12/2010 1:29:24 PM: Checking for existing processes
3/12/2010 1:29:24 PM: Saving Settings
3/12/2010 1:29:24 PM: Saving MRU Callsigns
3/12/2010 1:29:25 PM: Checking connectivity
3/12/2010 1:29:25 PM: Using Port: DirectPlay
3/12/2010 1:29:28 PM: Checking ASGS Client Version
3/12/2010 1:29:28 PM: Client Version: 212
3/12/2010 1:29:28 PM: Server Version: 210
3/12/2010 1:29:28 PM: Securing Installation
3/12/2010 1:29:28 PM: Validating Installation
3/12/2010 1:29:29 PM: Preparing Key
3/12/2010 1:29:29 PM: Key Generated
3/12/2010 1:29:29 PM: Connecting to ASGS Server
3/12/2010 1:29:29 PM: Authenticating
3/12/2010 1:29:30 PM: Ticket Received
3/12/2010 1:29:30 PM: Return Value: 0
3/12/2010 1:29:30 PM: Callsign: moglery(0)
3/12/2010 1:29:30 PM: Authenticated successfully
3/12/2010 1:29:30 PM: Checking messages
3/12/2010 1:29:31 PM: Return Value: 0
3/12/2010 1:29:31 PM: No messages
3/12/2010 1:29:31 PM: Checking polls
3/12/2010 1:29:31 PM: Return Value: 0
3/12/2010 1:29:31 PM: No polls
3/12/2010 1:29:31 PM: Logged In
3/12/2010 1:29:31 PM: Launching Allegiance
3/12/2010 1:29:32 PM: Active
3/12/2010 1:29:44 PM: Allegiance exited with code: EXCEPTION_ACCESS_VIOLATION
3/12/2010 1:29:44 PM: Creating Crashfile
-
Rachiou077
- Posts: 22
- Joined: Fri Mar 05, 2010 2:20 am
- Location: 127.0.0.1
- Contact:
Did you run the game as Administrator? Its best since your running Windows Vista u might need to run the game as Administrator
Last edited by Rachiou077 on Fri Mar 12, 2010 7:46 pm, edited 1 time in total.
One day, I'll show the human race what the true meaning of friendship really is.


The EXCEPTION_ACCESS_VIOLATION is almost always a graphic or sound file issue. Could be a corrupt or missing file. I'd completely uninstall Allegiance (including the removal of the files and folders found in /Program Files/Microsoft Games/Allegiance) and reboot. Then re-install again. Make sure you run it again as Admin and in Win2003 compatibility mode.
did that and also installed with the ogg box to convert the audio files still same thing. the only thing i havent tried yet is after i install i get a message saying signature is invalid(or expired cant remember) ive just been clicking repair then it appears to do an update. will try ignoring that message tomorrow and see if that has any affect on the process.
just curious could any .exe processes be affecting this? normally at startup i cut as many as possible and as required for other games ive had to delete btdna.exe. are there any that i must have or should look for are running?
just curious could any .exe processes be affecting this? normally at startup i cut as many as possible and as required for other games ive had to delete btdna.exe. are there any that i must have or should look for are running?
I'm not aware of any conflicts (other than certain firewalls or AV programs but that doesn't appear to be your problem - you can join the game but crash out. Firewalls and AV can prevent you from getting on the server at all.)
"Invalid signature" might be important here. Generally that's caused by a failure to clear our security - but again that's not your problem as ASGS is logging you in. However "invalid signature" could also mean a bad file that isn't passing our internal checksum system (prevents hacking of certain files). A corrupt file could very well cause this, and so does the EXCEPTION_ACCESS_VIOLATION error. So I think we're on the right track - trying to figure out which of the file(s) you have that don't pass muster.
"Invalid signature" might be important here. Generally that's caused by a failure to clear our security - but again that's not your problem as ASGS is logging you in. However "invalid signature" could also mean a bad file that isn't passing our internal checksum system (prevents hacking of certain files). A corrupt file could very well cause this, and so does the EXCEPTION_ACCESS_VIOLATION error. So I think we're on the right track - trying to figure out which of the file(s) you have that don't pass muster.

