If using GlobalCapture 2.1.0 or later, you may encounter an issue where the MongoDB service periodically stops and does not start up again. This can cause issues with GlobalCapture processing, GlobalAction processing, or viewing batches in the Batch Manager. The most common causes of this issue are read/write failures on the hard drive or power outage.
...
- On your GlobalCapture server, stop the MongoDB service and all dependent services. These include S9GlobalAction, GlobalCapture_1, ssBatchPortal, and GlobalForms.
- Navigate to your MongoDB data folder. By default, this will be in "C:\GetSmart\mongodb\data".
- Locate the two files "mongod.lock" and "WiredTiger.lock". Delete these two files.
- Open the "journal" folder . You should see a number of files, including some starting with "WiredTigerLog" or "WiredTigerPreplog". Delete the contents of the journal folder.
- Start the MongoDB service. The service should create new lock files and WiredTiger journal files.
- Start the services dependent on MongoDB (S9GlobalAction, GlobalCapture_1, ssBatchPortal, and GlobalForms).
...
| Info |
|---|
Note that this only applies to sites using GlobalCapture 2.1.0 or later. If you are using an older version of GlobalCapture or any version of GlobalSearch older than 4.4.0, then these steps do not apply to your site. |
...