After I set the BypassFiltering to false and reboot the server, issue was not present anymore. So, to solve it. Ran the script and reboot the server.
The FIP-FS Scan Process failed initialization. Error: 0x80010105 AND Faulting application name: scanningprocess.exe
Hi,
Exchange 2016 on Server 2016.
The FIP-FS Service is crashing and mail isn't being sent or received.
mail only flows when the anti malware service is disabled within Exchange.
Errors which are show are:
1: The FIP-FS Scan Process failed initialization. Error: 0x80010105. Error Details: The server threw an exception.
2: Faulting application name: scanningprocess.exe, version: 15.1.2176.9, time stamp: 0x60276c79
Faulting module name: scanningprocess.exe, version: 15.1.2176.9, time stamp: 0x60276c79
Exception code: 0xc0000005
Fault offset: 0x000000000005c5fd
Faulting process id: 0x3cf4
Faulting application start time: 0x01d713bf77380dbc
Faulting application path: C:\Program Files\Microsoft\Exchange Server\V15\FIP-FS\Bin\scanningprocess.exe
Faulting module path: C:\Program Files\Microsoft\Exchange Server\V15\FIP-FS\Bin\scanningprocess.exe
Report Id: ea2fad9c-70c5-4e2a-9662-5906f6da0eb1
Faulting package full name:
3: The anti-malware agent encountered an error while scanning. MessageId: <ce6f9d3a-a94d-473e-a8d6-cd222d267627@journal.report.generator> Message sent: 5/03/2021 1:21:48 AM From: <> Size: 727629 Bytes Error: Microsoft.Filtering.ScanAbortedException: Exception of type 'Microsoft.Filtering.ScanAbortedException' was thrown.
at Microsoft.Filtering.InteropUtils.ThrowPostScanErrorAsFilteringException(WSM_ReturnCode code, String message)
at Microsoft.Filtering.FilteringService.EndScan(IAsyncResult ar)
at Microsoft.Exchange.Transport.Agent.Malware.MalwareAgent.OnScanCompleted(IAsyncResult ar)
Faulting package-relative application ID:
We tried to stop the service, update engine and signatures with the powershell command "& $env:ExchangeInstallPath\Scripts\Update-MalwareFilteringServer.ps1 -Identity <FQDN of server>" which also throws an error.
I saw post: https://social.msdn.microsoft.com/Forums/en-US/33020637-55a8-4c03-a239-e8aabff23b4d/the-fipfs-scan-process-failed-initialization?forum=exchangesvrsecuremessaging
But this didn't work.
Any help appreciated
25 answers
Sort by: Newest
-
-
Johan Valstar 6 Reputation points
2022-01-03T21:08:40.13+00:00 I ran the script Reset-ScanEngineVersion.ps1 but it did not solve the issue! After completion:
PS C:\Program Files\Microsoft\Exchange Server\V15\Scripts> Get-EngineUpdateInformation
Engine : Microsoft
LastChecked : 01-03-2022 09:37:40 +01:00
LastUpdated : 01-03-2022 09:37:49 +01:00
EngineVersion : 1.1.18800.4
SignatureVersion : 1.355.1339.0
SignatureDateTime : 01-03-2022 08:48:44 +01:00
UpdateVersion : 2112330012
UpdateStatus : UpdateAttemptSuccessfulBut I still had the -BypassFiltering set to true, when I updated this to false and restart the transport service, mails got stuck again in the queue.
Set it again to true and restart transport service solved it again. -
Luciano Coppola 1 Reputation point
2022-01-03T18:54:24.437+00:00 Yep, It's the same one as was referenced in the blog.
-
Hollisorama 381 Reputation points
2022-01-03T18:42:53.943+00:00 -
Joshua Thompson 201 Reputation points
2022-01-02T18:14:03.127+00:00 Microsoft should be releasing a true fix for this right? Then we dont have to bypass filtering which is not a great solution. I understand mail flow is more important than scanning at this point.
I am having this issue with the Filtering service stopping but I am not seeing the mail flow issue.