Microsoft has released security updates for vulnerabilities found in any version of:
Exchange Server 2013
Exchange Server 2016
Exchange Server 2019
These updates are available for the fol...
Updated Feb 24, 2022
Version 3.0
Blog Post
Sure. I think memory is not the issue. If I run manually
$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
there's the same error message. Maybe something with the COM+ class ?
Even a get query produces the same error message:
get-ConfigurationValue -XPath "/fs-conf:Configuration/fs-sys:Machine/fs-sys:Paths/fs-sys:TraceFile"
get-ConfigurationValue : 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)).
At line:1 char:1
+ get-ConfigurationValue -XPath "/fs-conf:Configuration/fs-sys:Machine/ ...
+ ~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : NotSpecified: (:) [], OutOfMemoryException
+ FullyQualifiedErrorId : System.OutOfMemoryException