Before the Deep Security Manager service starts, it needs to go through a checklist (e.g. heap usage, resource situation, database accessibility, etc). Once any item on the checklist failed to pass, it will show the "Precondition check failed" error.
The error message usually occurs due to the following reasons:
- There is a database connectivity issue.
- The schema version between Deep Security Manager and database node is mismatched.
To resolve the issue, you can perform the corresponding solution below:
- For connectivity issue, follow this article to check the database connection: Creating a data link (UDL) file and testing the connectivity to a Microsoft SQL server.
- When the schema version is mismatched, refer to this page for upgrading the Deep Security Manager and SQL Database Schema.
For detailed reasons on why the error occurs, you may check the server0.log.