Product operational failure

In case of unexpected security issues or failures during product operation, the following actions can be taken. Common issues include integrity verification failure, self-test failure, and access control policy violations.

Integrity Verification Failure
If integrity verification fails, all processes of the FilingBox MEGA2 v2 Client will be terminated, and normal operation will not be possible. In this case, authorized administrators should take actions such as reinstalling the client, checking the hash values set on the FilingBox MEGA2 v2 Server for the client, or follow the troubleshooting response system in 'Troubleshooting Other Failures' and proceed with phone reception and consultation.
Self-Test Failure
In the case of a self-test failure, actions such as restarting the service or reinstalling the client can be taken, or follow the troubleshooting response system in 'Troubleshooting Other Failures' and proceed with phone reception and consultation.
Access Control Policy Violation
If login fails, verify the IP and MAC values set in the 'Device Information' page of the administrator web UI, and check whether the registered device administrator account is correct. Also, ensure that communication between the client and server is functioning properly. If all information is correct but login still fails, follow the troubleshooting response system in 'Troubleshooting Other Failures' and proceed with phone reception and consultation.
Server Connection Failure
If the client logs in but fails to connect to the server (e.g., network issues or server process termination), follow the troubleshooting response system in 'Troubleshooting Other Failures' and proceed with phone reception and consultation.
Have more questions? Submit a request