Details
-
Task
-
Resolution: Won't Fix
-
Minor - P4
-
None
-
ops-manager-2.0.3, mongodb-3.2
-
None
-
Windows Server 2008 R2
-
0.5
Description
The mongodb-win32-x86_64-enterprise-windows-64-3.2.6.zip archive file which is being used by the backup daemon doesn't have MSVCR120.dll. The Microsoft Windows Installer package (.msi) that was used for the installation of Ops Manager does contain MSVCR120.dll.
The issue here is that the Dynamic Link Library is distributed with the .msi but not with the binary zipped file. Initial backup starts and fails with an error similar to the following:
Failed to start mongod. Corrupt: false
|
com.xgen.svc.brs.util.MongoManager$MongoManagerStartException: Upgrade command failed. Cmd: `[D:\MMSData\MongoDBReleases\mongodb-win32-x86_64-enterprise-windows-64-3.2.6\bin\mongod.exe, --port, 27501, --dbpath, D:\MongoDBHeaders\57332ddf093af36afc2b8f51/rs0/head/, --bind_ip, 127.0.0.1, --setParameter, ttlMonitorEnabled=false, --nojournal, --slowms, 1000, --setParameter, failIndexKeyTooLong=false, --setParameter, recoverShardingState=false, --setParameter, diagnosticDataCollectionEnabled=false, --storageEngine, wiredTiger, --wiredTigerCacheSizeGB, 2, --upgrade]` Code: `-1073741515` StdOut: StdErr:
|
com.xgen.svc.brs.util.MongoManager$MongoManagerStartException.badExitCode(MongoManager.java:203)
|
The solution to this issue is to install the Visual C++ Redistributable Packages on the backup daemon server. The package can be downloaded at the following link: https://www.microsoft.com/en-us/download/details.aspx?id=40784
It may be a good idea to include this information in our documentation to make this issue more visible to our customers.
Attachments
Issue Links
- links to