4 ms·

I'm pleased the error message actually mentioned exactly what's wrong. Compare the two snippets in [1]: > Description: The FIP-FS "Microsoft" Scan Engine fail

by cube00 5y ago

I'm pleased the error message actually mentioned exactly what's wrong. Compare the two snippets in [1]: > Description: The FIP-FS "Microsoft" Scan Engine failed to load. PID: 23092, Error Code: 0x80004005. Error Description: Can't convert "2201010001" to long. > Description: The FIP-FS Scan Process failed initialization. Error: 0x80004005. Error Details: Unspecified error. I hope it's trend that continues because when it's going pear shaped every little morsel of information is important to narrow down the problem. I'm less pleased they seemly didn't deploy this update to an internal on-prem test Exchange server before a wider release. [1]: https://techcommunity.microsoft.com/t5/exchange-team-blog/email-stuck-in-exchange-on-premises-transport-queues/ba-p/3049447 https://techcommunity.microsoft.com/t5/exchange-team-blog/em...

irrational 5y ago
> when it's going pear shaped I think this means “when it’s going bad”, but what does “pear shaped” mean? And why a pear?
- FooHentai 5y ago
  It originated in the British Royal Air Force where an imperfectly-executed loop-de-loop would go 'pear shaped' instead of round as intended. Interestingly it then played off the British tendency for understatement so that something that meant 'a bit wonky' slid into meaning 'off the rails busted'.
mizzao 5y ago
> I'm less pleased they seemly didn't deploy this update Is there actually an update here, or just some code that was probably sitting around for years until 2022 rolled around?
- aoetalks 5y ago
  AFAIK it was a signature update, and the existing code couldn't understand the new signatures with a 2022 timestamp. IMHO, signatures still should have been deployed to an early ring before broad release. Antimalware signatures as code, anyone?
  - gregmac 5y ago
    These kinds of things are always tricky, and always easier to see in hindsight. Everything is a trade-off. I can easily picture a scenario where there is pressure to reduce time to release signature updates, and someone looked at a process where there was early testing (that would have caught this) and said "Over the past 5 years, we've deployed hundreds of signatures with exactly zero failures; why are we still doing this process that adds a pointless delay?"

by cube00 5y ago

irrational 5y ago

> when it's going pear shaped I think this means “when it’s going bad”, but what does “pear shaped” mean? And why a pear?

FooHentai 5y ago
It originated in the British Royal Air Force where an imperfectly-executed loop-de-loop would go 'pear shaped' instead of round as intended. Interestingly it then played off the British tendency for understatement so that something that meant 'a bit wonky' slid into meaning 'off the rails busted'.

mizzao 5y ago

> I'm less pleased they seemly didn't deploy this update Is there actually an update here, or just some code that was probably sitting around for years until 2022 rolled around?

aoetalks 5y ago
AFAIK it was a signature update, and the existing code couldn't understand the new signatures with a 2022 timestamp. IMHO, signatures still should have been deployed to an early ring before broad release. Antimalware signatures as code, anyone?
- gregmac 5y ago
  These kinds of things are always tricky, and always easier to see in hindsight. Everything is a trade-off. I can easily picture a scenario where there is pressure to reduce time to release signature updates, and someone looked at a process where there was early testing (that would have caught this) and said "Over the past 5 years, we've deployed hundreds of signatures with exactly zero failures; why are we still doing this process that adds a pointless delay?"