Updated ASGS from build 165 to 210 today, and got the above error of 'Unable to validate allegiance installation'
I've tried an update/repair of critical files, and it can't delete the old asgsclient.exe I've manually deleted it and updating with asgsupdate.exe, it downloads a new client, but no luck.
ASGS log below:
• Initializing
• Reading Settings
• Logging Option: DEBUG
• 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: HTTP
• Checking ASGS Client Version
• Client Version: 210
• Server Version: 210
• Securing Installation
• Validating Installation
• Unable to validate Allegiance installation.
• This implementation is not part of the Windows Platform FIPS validated cryptographic algorithms.
Unable to Validate Allegiance Installation
Do you have .NET 2.0?
If so, there might be something wrong with your .NET install... check out the last line in your paste.
Do you have any interesting crypto libraries installed?
--TE
If so, there might be something wrong with your .NET install... check out the last line in your paste.
Do you have any interesting crypto libraries installed?
--TE
The Allegiance community currently hates their sysadmin because he is doing: [Too Much] [____________|] [Too Little]
Current reason: Removing the PayPal contribute page. Send Bitcoin instead: 1EccFi98tR5S9BYLuB61sFfxKqqgSKK8Yz. This scale updates regularly.
Reinstall didn't work. (I'd had .NET 1.1, 2.0 SP 2, 3.0 SP2, and 3.5 installed).
Problem Identified at http://support.microsoft.com/kb/911722, I was able to solve it by their recommended workaround of changing registry key HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa\fipsalgorithmpolicy to 0
Problem Identified at http://support.microsoft.com/kb/911722, I was able to solve it by their recommended workaround of changing registry key HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa\fipsalgorithmpolicy to 0
We've upped our standards. Up yours.