Hello,

We're experiencing a significant issue with our ManageEngine EndPoint Central environment following the application of a new license. Any insights would be invaluable.

Background:

Roughly a week ago, our ManageEngine EndPoint Central license expired unexpectedly, despite an active renewal period from 01/12/2023 to 30/11/2024. After reapplying the new license, we encountered a range of issues:

• Restrictions on core features such as Mobile Device Management (MDM) and the Security Add-on.
• Database inconsistency errors at server start-up.

In response, we restored several servers to their previous states after the initial database recommendation failed:

• Main Endpoint Central (EPC) server
• Failover server
• SQL Server

One server, the distribution server, hasn’t been restored yet.

Current Problem:

1. Database and File System Inconsistency Errors:

   • After applying the new license file, the following day we began seeing errors related to "Database and file system inconsistency" upon starting the EPC server.
   • The error message indicates that this issue occurred after a “recent backup restore of the database,” though no backup restoration took place when this error originally started happening.
   • We followed the recommended repair steps provided on the error page, allowing the so-called repair to run for 24 hours, but eventually cancelled the process as there was no sign of completion or resolution.

Potential Issue Related to the New License:

Given the timing of these errors, we’re considering that the new license may have introduced incompatibilities:

• It’s possible the license activated features or modules that require schema changes in the database, creating an inconsistency between the database and application.
• We’re awaiting feedback from ManageEngine to confirm if the license introduces schema changes or requires specific settings in SQL Server.

Steps Taken So Far:

• Restored the primary servers (EPC, failover, and SQL).
• Ran initial integrity checks on the database, with DBCC CHECKDB showing no structural issues.
• Attempted the repair steps as recommended, but cancelled after no progress was made in 24 hours.

I'm reaching out to see if anyone has encountered a similar issue or can provide insights into the following:

1. Database and File System Inconsistency After License Application:

   • Has anyone experienced inconsistency errors following a license application with ManageEngine?
   • Could new features or modules activated by a license require additional steps to align the database schema with the application?

2. ManageEngine and SQL Server Compatibility:

   • Are there known compatibility issues between ManageEngine licenses and SQL Server configurations?
   • Should specific SQL Server settings be adjusted when applying a new license?

• We’re working with ManageEngine support to clarify if the new license affects the database schema, but as usual their response times and are absolutely terrible, so much so that we are reevaluating the future of the product in our organisation.
• Considering setting up a test environment to replicate the issue without impacting production.

Thank you in advance for any advice you can provide!