cant get alleg cliant to start

mut2121 · Post by **mut2121** » Sat Oct 03, 2009 12:54 am

Windows Version (and Service Packs):xp
Processor Speed:2.4ghz
RAM:632
Video Card (Make and Model#):dont know
Sound Card (Make and Model#):dont know
Connection Type (Dialup, Cable, DSL, other):dsl
Modem (Make and Model#):n
Router (Make and Model#):n
Internet Service Provider(company name):att
Location(State/Province/Locality, and Country):michigan, usa
Installed Mods:none

Make and Version of firewall:n
Make and version of anti-virus:avast

Confirm that you have the following installed:

* .Net 2.0 [ ] yep

Problem Encountered at Step #: (read the "What Should Happen" for this step#)
Which Program (ASGS/Allegiance):
What Error Message:

i've uninstalled mcaffe using the removeal tool, installed avast, and uninstalled all the framework reinstalled 2 and still it says ASGSClient has encounterd a problem and needs to close it is differnt than when i had mcafee but it still wont work

Post by **FreeBeer** » Sat Oct 03, 2009 12:55 am

Did you reboot? Try it again (full power down, then power up).

mut2121 · Post by **mut2121** » Sat Oct 03, 2009 1:05 am

still not working

mut2121 · Post by **mut2121** » Sat Oct 03, 2009 1:19 am

dont know if it would help but this is what it wants to send to MS - event type : clr20r3 p1 : asgsclient.exe p2: 2.2.3337.18747 p3: 8 p4 system drawing p5 2.0.0.0 p6: 4889dec2 p7: 7af p8: 6c p9: system. argumentexception

Andon · Post by **Andon** » Sat Oct 03, 2009 7:14 am

Your problem may lie with Avast. Uninstall the firewall component of Avast - I don't remember what it's called, but it does cause issues.

Parasitism · Post by **Parasitism** » Sat Oct 03, 2009 1:17 pm

Andon wrote:QUOTE (Andon @ Oct 3 2009, 03:14 AM) Your problem may lie with Avast. Uninstall the firewall component of Avast - I don't remember what it's called, but it does cause issues.

Or just get rid of Avast overall.

Post by **FreeBeer** » Sat Oct 03, 2009 3:11 pm

His problem doesn't appear to be Avast related (the firewall component issue usually shows itself as a "failed to connect to lobby" error). However, I am in agreement as to what has been suggested if only for trouble-shooting reasons.

Uninstall Allegiance (I suspect the issue is here - something got borked but I can't say for sure). Reboot. Uninstall Avast. Reboot. Run the mcaffee removal tool again. Reboot. Install Allegiance with a freshly downloaded copy from this site. Reboot. Run Allegiance to see what happens. If you can connect, then install Avast (without installing the firewall component). Reboot. Run Allegiance.

The idea here is to isolate the problem one step at a time. Rebooting is important since each of those apps make registry entries/changes that may not take effect properly until a reboot occurs. I'd also recommend that you consider running a registry cleaner between each step. Not all programs clean up the registry properly after an uninstall and you may be experiencing a side effect of having orphaned or otherwise borked entries.

mut2121 · Post by **mut2121** » Sun Oct 04, 2009 12:48 am

uninstalled and reinstalled it all, still no luck

Post by **FreeBeer** » Sun Oct 04, 2009 4:23 am

hmmm.... the last time I ran across something like this, the guy had to re-install Windows. It happens. The OS gets so messed up (unrelated to Allegiance - but Allegiance just ends up highlighting the fact that there's issues) that cleaning up isn't really possible or practical. But before I recommend that as an action (it's a last-resort option) try running Windows Update, rebooting, running it again, etc. Then give Alleg a try again.

In the mean time maybe someone else will jump in with a trick or two you can try.

mut2121 · Post by **mut2121** » Sun Oct 04, 2009 12:42 pm

i had to reformat once before but that isnt an option now, i think its a problem in the c++ and/or .net, is there a utility that scans/repairs them