FortiSandbox
FortiSandbox provides a solution to protect against advanced threats and ransomware for companies who don’t want to implement and maintain a sandbox environment on their own.
keithli_FTNT
Staff
Staff
Article Id 195133
Description

Below are telltale signs that your FortiSandbox’s Windows VM is not activated properly

1. Dashboard shows a “!” on Windows VM.

FSA2.0-Windows-VM-not-activated-1.jpg

2. Scrolling over the “!” shows an error message:

FSA2.0-Windows-VM-not-activated-Warning.jpg

3. Command vm-status returns the same error:

> vm-status
ERROR: Could not activate all the VM images with given keys. Please reburn other valid keys or reboot after changing your environment/network settings
Virtual Hosts Initialization .......... Failed
 
Installed VM Images:
ID Ver Name
4 5 WINXPVM1
1 6 WINXPVM
8 5 WIN7X86VM
2 6 WIN7X64VM

4. Command status returns Windows VM: Not-Initialized

> status
System:
Version:              v2.00-build0021
Serial number:        FSA-VM000000xxxx
FSA-VM License:       Valid, 365 day(s) left
System time:          Tue Jan 27 17:29:05 2015 EST
Disk Usage:           68 GB
Image status check:   OK
 
Windows VM:           Not-Initialized
VM Internet access:   On
Disk Size:            251 GB

5. Logs show failure to activate:

msg="FortiSandbox system is up. Start initializing Sandbox VMs."
msg="Start activation WIN7X86VM with key xxxxx-xxxxx-xxxxx-xxxxx-xxxxx"
msg="Failed to activate WIN7X86VM with key xxxxx-xxxxx-xxxxx-xxxxx-xxxxx"
msg="Failed to activate WIN7X86VM message="-1:Not activated"  "
msg="Could not activate all the VM images with given keys. Please reburn other valid keys or reboot after changing your environment/network settings"
msg="GUI database is not ready."
msg="System database is not ready. A program should have started to rebuild it and it shall be ready after a while."
msg="Windows VM are not activated or initialized. ERROR: Could not activate all the VM images with given keys. Please reburn other valid keys or reboot after changing your environment/network settings ."

6. Dashboard widgets return “Database Not Ready”:

FSA2.0-DBnotReady.png

7. (FortiSandbox 2.0) The File-based Detection and URL Detection pages do not load properly. As soon as user goes to those pages, the page loads briefly and then return back to the System Dashboard:

Menu_opening.png

8. Connection from a FortiGate GUI fails:

TestConnection.jpg

9. Connections from FortiGate to FortiSandbox via port 514 are constantly reset.

FSA-conndisconnect.JPG 

Related Articles

Technical Note: Updating the Windows VM on the FortiSandbox

Troubleshooting Windows VM package activation and initialization issues

Contributors