After moving the database to a new SQL 2016 Server, the Deep Security Manager service may not start. This happens when the database server is restored using an old database backup without the latest Deep Security Manager version under 'systemversions' table.
Make sure that the old database backup is complete, then re-run the database restore. The Deep Security Manager Service should now connect to the database.
For more information on how to back up and restore the database, you may refer to the following articles: