The MONGO database prompts the "object references not set to an instance of an object" solution when you create a table with Mongovue

First, the question
After installing the 3.4 mongdb, I randomly downloaded a Mongovue client online, unable to view the default database local collection, and the following issue occurred when creating the collection

Error in creating new Collection
Object references are not set to an instance of an object.
Type:System.NullReferenceException
Stack: In MangoUI.ComNavTree.dbAddCollection_Click (Object sender, EventArgs e)
After searching on the internet, some people said it was MongoDB version of the reason, replaced by 2 can be, too lazy to change, continue to find ways to eventually switch the storage engine, MongoDB defaults to the Wiredtiger engine after 3.2, and the management software matches the previous engine, so it cannot be used, and the presence engine must be reset.
Second, Reason:

Before 2015/3/17, MongoDB had only one storage engine, called mmap,mongodb3.0 's launch, which made MongoDB have two engines: MMAPv1 and Wiredtiger. MMAPV1: Adapts to all MongoDB versions, MongoDB3.0 's default engine Wiredtiger: Only 64-bit MONGODB supported

MongoDB two engines can switch to each other, and we can specify the engine type when creating the service.

Third, the solution steps:

To reset the storage engine:
CD D:\MongoDB\bin

Reset Storage Engine Statements
Mongod–storageengine Mmapv1–dbpath D:\MongoDB\data2

* Note: The database location must be re-specified, as the original D:\MongoDB\data reset the storage engine when the name must be replaced, D:\MONGODB\DATA2
After completion the client uses the command TestDB to create its own database

re-use Mongovue link TestDB