Readiness Checks fail with "The type initializer for 'Microsoft.Exchange.Configuration.Tasks.ThrottlingModule`1' threw an exception."

Question

There's another thread about this issue but the accepted answer actually has nothing at all to do with the original problem/question so that's a bit deceptive.
Anyway, when trying to install Exchange 2013 SP1 (on 2012 R2 Datacentre) the installation reaches the Configuring Prerequisites part of the Readiness Checks and then fails out with the message:
The type initializer for 'Microsoft.Exchange.Configuration.Tasks.ThrottlingModule`1' threw an exception.
I honestly can't find any way around this issue and the only mentions I've seen resulted in people reinstalling Windows which obviously isn't really a resolution to the problem.
Is there any known fix for this issue?

Answer 1

Ok well I've managed to get around that now by recreating a few registry keys and documented that here (apparently I'm not allowed to create links so can't put that here).
I have a new issue now though. It seemed to get almost all the way through the installation process but is now failing due to a "memory" issue although due to the wording I can't tell whether it means RAM or Disk space. Either way, neither should
apply. The drive has 80GB of space available and the machine has 8GB of RAM (only 2GB in use at the time the installer was ran and the amount didn't drop).
The exact error is...
Error:
The following error was generated when "$error.Clear();
Write-ExchangeSetupLog -Info "Setting up FIPS configuration based on Exchange Install Path";
$FipsDataPath = [System.IO.Path]::Combine($RoleInstallPath, "FIP-FS\Data");
$FipsEnginesPath = [System.IO.Path]::Combine($FipsDataPath, "Engines");
Write-ExchangeSetupLog -Info "Loading FipFs snapin";
Add-PsSnapin Microsoft.Forefront.Filtering.Management.PowerShell -ErrorAction SilentlyContinue;
Set-ConfigurationValue -XPath "/fs-conf:Configuration/fs-sys:Machine/fs-sys:Paths/fs-sys:TraceFile" -Value $FipsDataPath -Confirm:$false
Set-ConfigurationValue -XPath "/fs-conf:Configuration/fs-sys:Machine/fs-sys:Paths/fs-sys:Engines" -Value $FipsEnginesPath -Confirm:$false
# Copy Microsoft Engine to Engines folder during the install
$FipsBinPath = [System.IO.Path]::Combine($RoleInstallPath, "FIP-FS\Bin");
$MicrosoftEngineSourcePath = [System.IO.Path]::Combine($FipsBinPath, "Engine\Microsoft");
$MicrosoftEngineDestinationPath = [System.IO.Path]::Combine($FipsEnginesPath, "amd64\Microsoft");
$MicrosoftEngineExists = Test-Path $MicrosoftEngineDestinationPath
if(! $MicrosoftEngineExists)
Robocopy $MicrosoftEngineSourcePath $MicrosoftEngineDestinationPath /S /COPYALL
" was run: "Creating an instance of the COM component with CLSID {2DC947D7-A2DC-4276-A554-891346CE2032} from the IClassFactory failed due to the following error: 8007000e Not enough storage is available to complete this operation. (Exception from HRESULT: 0x8007000E (E_OUTOFMEMORY)).".
Error:
The following error was generated when "$error.Clear();
Write-ExchangeSetupLog -Info "Setting up FIPS configuration based on Exchange Install Path";
$FipsDataPath = [System.IO.Path]::Combine($RoleInstallPath, "FIP-FS\Data");
$FipsEnginesPath = [System.IO.Path]::Combine($FipsDataPath, "Engines");
Write-ExchangeSetupLog -Info "Loading FipFs snapin";
Add-PsSnapin Microsoft.Forefront.Filtering.Management.PowerShell -ErrorAction SilentlyContinue;
Set-ConfigurationValue -XPath "/fs-conf:Configuration/fs-sys:Machine/fs-sys:Paths/fs-sys:TraceFile" -Value $FipsDataPath -Confirm:$false
Set-ConfigurationValue -XPath "/fs-conf:Configuration/fs-sys:Machine/fs-sys:Paths/fs-sys:Engines" -Value $FipsEnginesPath -Confirm:$false
# Copy Microsoft Engine to Engines folder during the install
$FipsBinPath = [System.IO.Path]::Combine($RoleInstallPath, "FIP-FS\Bin");
$MicrosoftEngineSourcePath = [System.IO.Path]::Combine($FipsBinPath, "Engine\Microsoft");
$MicrosoftEngineDestinationPath = [System.IO.Path]::Combine($FipsEnginesPath, "amd64\Microsoft");
$MicrosoftEngineExists = Test-Path $MicrosoftEngineDestinationPath
if(! $MicrosoftEngineExists)
Robocopy $MicrosoftEngineSourcePath $MicrosoftEngineDestinationPath /S /COPYALL
" was run: "Creating an instance of the COM component with CLSID {2DC947D7-A2DC-4276-A554-891346CE2032} from the IClassFactory failed due to the following error: 8007000e Not enough storage is available to complete this operation. (Exception from HRESULT: 0x8007000E (E_OUTOFMEMORY)).".
So if it's not the drive (there's only one drive in the machine) or RAM then what exactly has it ran out of?