It has come to our attention that in some cases, customers may be affected by a bug found in the MongoDB version we are using as the Sisense application database. The MongoDB issue is described here. This issue is relevant for all versions starting with Sisense V6.7. We have been working closely with MongoDB to resolve this issue quickly.

This issue is related to MongoDB service process shutdown during Windows restart, which may result in a corrupted metadata file. The effect of the MongoDB issue is that in some cases the application database may become corrupted, and all Sisense configuration data, users, and dashboards may be lost.

We have encountered two customers with this issue. In both cases, Sisense managed to recover their information, and the systems were returned to full functionality. For instructions on how to periodically back up your MongoDB, click here.

We have immediately released a service pack for Sisense V6.7.1, including a MongoDB upgrade (to version 3.4.10) which resolves this issue.  Sisense V7.0.1 will be released shortly to address this issue for V7.0 users. This is a recommended upgrade if you are using Sisense V6.7 and later releases.

We apologize for the inconvenience this issue may have caused you. We value your support and trust and will continue to be transparent in handling issues in our product.