unable to validate allegiiance installation after asgs auto update

merc · Post by **merc** » Wed Aug 02, 2006 4:46 am

OK, what is going on. ASGS auto update and tell me alleg is not validated. What is the solution for this?

• Reading Settings
• Logging Option: SIMPLE
• Loading MRU Callsigns
• Loading Form Position
• Checking Installation
• 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: 127
• Server Version: 127
• Securing Installation
• Validating Installation
• Unable to validate Allegiance installation.
• File Allegiance.exe has an invalid signature.

Paradigm2 · Post by **Paradigm2** » Wed Aug 02, 2006 5:05 am

Got the same thing

Post by **Pook** » Wed Aug 02, 2006 5:09 am

ASGS -> Help -> Get Latest Build.

merc · Post by **merc** » Wed Aug 02, 2006 5:11 am

Pook wrote:QUOTE (Pook @ Aug 2 2006, 12:09 AM) ASGS -> Help -> Get Latest Build.

Did exactly that but still no resolve.

I mean asgs auto update so I should have to do it but I did it again anyway. Still same error.

Post by **Pook** » Wed Aug 02, 2006 5:14 am

Then the updater isn't being allowed to update your Allegiance.exe

Make sure that Allegiance.exe is not read-only, or simply Delete your existing Allegiance.exe and then rerun the help-> get latest build command.

merc · Post by **merc** » Wed Aug 02, 2006 5:20 am

Pook wrote:QUOTE (Pook @ Aug 2 2006, 12:14 AM) Then the updater isn't being allowed to update your Allegiance.exe

Make sure that Allegiance.exe is not read-only, or simply Delete your existing Allegiance.exe and then rerun the help-> get latest build command.

OK, I remove the exe out of the folder did asgs update. But nada. Now it try to launch alleg but ofcourse no alleg.exe in folder cus I deleted it and it did not down load.

• Checking for system updates
• Checking for existing processes
• Saving Settings
• Saving MRU Callsigns
• Checking connectivity
• Using Port: DirectPlay
• Checking ASGS Client Version
• Client Version: 127
• Server Version: 127
• Securing Installation
• Validating Installation
• Preparing Key
• Key Generated
• Connecting to ASGS Server
• Authenticating
• Ticket Received
• Return Value: 0
• Callsign: TheJoker(23)
• Authenticated successfully
• Checking messages
• Return Value: 0
• No messages
• Checking polls
• Return Value: 0
• No polls
• Logged In
• Launching Allegiance
• Unable to launch Allegiance.
• Allegiance did not launch in the time allotted.
• Beginning Logout
• Closing processes
• Sending Logout Request
• Logged Out

Paradigm2 · Post by **Paradigm2** » Wed Aug 02, 2006 5:20 am

I get "Unable to launch updater. Update ASGS Manually." when I try that Pook.

The only way I know to update it manually is through the link http://downloads.alleg.net/asgs/asgs.zip, but that just gives me build 127 again and the same error.

Post by **Pook** » Wed Aug 02, 2006 5:21 am

Merc,

Your installation is obviously abnormal.

ASGSClient.exe and ASGSUpdate.exe have to be in the same folder as Allegiance.exe, right in the root of your allegiance installation.

If that's not the case, then the update is going to place the files in the wrong spot.

Post by **Pook** » Wed Aug 02, 2006 5:25 am

Paradigm2 wrote:QUOTE (Paradigm2 @ Aug 2 2006, 12:20 AM) I get "Unable to launch updater. Update ASGS Manually." when I try that Pook.

The only way I know to update it manually is through the link http://downloads.alleg.net/asgs/asgs.zip, but that just gives me build 127 again and the same error.

Para,

Get the ASGS.zip, extract the contents (ASGSclient.exe and ASGSupdate.exe) into the allegiance root folder, right alongside Allegiance.exe

Then double-click ASGSUpdate.exe to run it and manually update.

bacillen · Post by **bacillen** » Wed Aug 02, 2006 5:26 am

Pook wrote:QUOTE (Pook @ Aug 2 2006, 03:21 PM) Merc,

Your installation is obviously abnormal.

ASGSClient.exe and ASGSUpdate.exe have to be in the same folder as Allegiance.exe, right in the root of your allegiance installation.

If that's not the case, then the update is going to place the files in the wrong spot.

I was getting the same problem as you Merc, then noticed that the Allegiance.exe I needed appeared to be going to c:\program files\microsoft games\allegiance\ASGS for some reason. Once I copied that one into my root alleg dir there I got going again.