Unable to start Deep Security Manager service after pointing to a new database server

- Updated:
- 18 Jul 2018
- Product/Version:
- Deep Security 11.0
- Platform:
- N/A N/A

Summary

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.

Details

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:

Rating:

Category:

Troubleshoot

Solution Id:

1120194

Feedback

Did this article help you?

Thank you for your feedback!

What was the problem with this article?

The image(s) in the article did not display properly.

The article did not provide detailed procedure.

The article is hard to understand and follow.

The video did not play properly.

The article did not resolve my issue.

Others. Please specify.

*This form is automated system. General questions, technical, sales, and product-related issues submitted through this form will not be answered.

If you need additional help, you may try to contact the support team. Contact Support

Thanks for voting.

To help us improve the quality of this article, please leave your email here so we can clarify further your feedback, if neccessary:

We will not send you spam or share your email address.

*This form is automated system. General questions, technical, sales, and product-related issues submitted through this form will not be answered.