Resolved Issues

Resolved Issues

The following issues have been fixed in version 3.0.2. For inquires about a particular bug, please contact Customer Service & Support.

Bug ID	Description
446786	Downloaded original file does not have extension.
470595	Some syslog messages do not have time stamps.
474251	VMs running in parallel caused bad condition after some time passed.
486336	Password-protected .doc file detected as clean without interaction.
494453	YARA name should not be N/A in job details.
504140	Even when verdict is ready, it is not returned to FortiMail.
504440	Should include Detection OS in job detail reports.
504557	Scan process stopped due to damaged file stuck in pre-scan.
504868	No ICAP response when concurrent ICAP connections are more than 10.
505524	No submit user in job detail PDF report for malicious URLs.
505601	Failed to replace/delete/append URL black/white list text file.
505785	Remove port3 from health check monitoring interface list.
508232	Reboot should not reset the systool package.
508232	Reboot should not reset `systool`. See also 515410.
508478	Build-in `reports.db` does not contain report table.
508569	Some URL category ratings do not match as per administration guide.
509133	Office license on custom VMs does not get activated after upgrading to 3.0.1.
509137	URL matched in white list may not be caught.
510055	User-defined black list domain should not submit to cloud.
511512	Cannot load data now, please try again later error in Report Center.
513387	FortiSandbox not allowing special characters in password for LDAP authentication.
514511	Netshare scan hangs when there are a large number of files.
515410	FSA-3000E clean xls and xlsx files were rated as High Risk on WIN10X64VMO16 VM. See also 508232.
516096	GUI cannot handle large white / black lists.
516106	Number of black / white list entries domain/URL/URL REGEX is limited to 1000.
516204	High memory usage on FSA-VM00 - different values reported by SNMP, CLI output, and FortiSandbox GUI.

Resolved Issues

The following issues have been fixed in version 3.0.2. For inquires about a particular bug, please contact Customer Service & Support.

Bug ID

Description

446786

Downloaded original file does not have extension.

470595

Some syslog messages do not have time stamps.

474251

VMs running in parallel caused bad condition after some time passed.

486336

Password-protected .doc file detected as clean without interaction.

494453

YARA name should not be N/A in job details.

504140

Even when verdict is ready, it is not returned to FortiMail.

504440

Should include Detection OS in job detail reports.

504557

Scan process stopped due to damaged file stuck in pre-scan.

504868

No ICAP response when concurrent ICAP connections are more than 10.

505524

No submit user in job detail PDF report for malicious URLs.

505601

Failed to replace/delete/append URL black/white list text file.

505785

Remove port3 from health check monitoring interface list.

508232

Reboot should not reset the systool package.

508232

Reboot should not reset systool. See also 515410.

508478

Build-in reports.db does not contain report table.

508569

Some URL category ratings do not match as per administration guide.

509133

Office license on custom VMs does not get activated after upgrading to 3.0.1.

509137

URL matched in white list may not be caught.

510055

User-defined black list domain should not submit to cloud.

511512

Cannot load data now, please try again later error in Report Center.

513387

FortiSandbox not allowing special characters in password for LDAP authentication.

514511

Netshare scan hangs when there are a large number of files.

515410

FSA-3000E clean xls and xlsx files were rated as High Risk on WIN10X64VMO16 VM. See also 508232.

516096

GUI cannot handle large white / black lists.

516106

Number of black / white list entries domain/URL/URL REGEX is limited to 1000.

516204

High memory usage on FSA-VM00 - different values reported by SNMP, CLI output, and FortiSandbox GUI.

Release Notes

Resolved Issues

Resolved Issues