Technical Tip: Fortinet Single Sign-On (FSSO) application crashes observed after upgrading the FSSO Collector Agent to version 5.0.0330

After upgrading the FSSO (Fortinet Single-Sign-On) CA to version 5.0.0330, customers may experience FSSO CA application crashes on the Windows Server. The crashes are not restricted to any particular Windows Server version.

Windows application event may show similar crash events:

Faulting application name: collectoragent.exe, version: 5.0.330.0, time stamp: 0x694497b6
Faulting module name: combase.dll, version: 10.0.26100.32236, time stamp: 0xb18fc53c
Exception code: 0xc0000005
Fault offset: 0x00000000000197af
Faulting process id: 0xD84
Faulting application start time: 0x1DCA7FC8B615C4E
Faulting application path: C:\Program Files (x86)\Fortinet\FSAE\collectoragent.exe
Faulting module path: C:\WINDOWS\System32\combase.dll
Report Id: 3d9130ad-f8c5-48e4-87de-c670e52dca3c
Faulting package full name:
Faulting package-relative application ID:

A crash will cause the FSSO Windows AD connector on the FortiGate to disconnect. If a secondary FSSO connector is configured, the system will automatically fail over to the secondary connector. To get notified of the FSSO down events, an automation stitch may be configured on the FortiGate. Creating automation stitches.

To fix this issue, the FSSO CA can be downgraded to version 5.0.0325 or upgraded to the next version of FSSO Collector Agent (the releases are usually bundled with FortiOS releases).

Related articles:

• Technical Tip: How to export FSSO Collector Agent logs
• Technical Tip: Common reasons FSSO status shows as 'down' on the Firewall
• Troubleshooting Tip: FortiGate cannot connect to FSSO Agent on Windows AD
• Troubleshooting Tip: FSSO Complete troubleshooting for TAC tickets
• Technical Tip: FortiGate FSSO Collector Agent 5.0.0323 or earlier does not support Windows Server 2025 with default polling mode