[SERVER-26028] Windows zip releases missing msvcr120.dll and msvcp120.dll Created: 08/Sep/16  Updated: 28/May/20  Resolved: 18/May/20

Status: Closed
Project: Core Server
Component/s: Packaging
Affects Version/s: 3.2.6, 3.3.12
Fix Version/s: None

Type: Bug Priority: Minor - P4
Reporter: John Becker Assignee: Andrew Morrow (Inactive)
Resolution: Won't Fix Votes: 7
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Duplicate
is duplicated by SERVER-32877 Unable to run mongod.exe on Windows 1... Closed
Related
related to SERVER-47954 MongoDB community zip on Windows shou... Closed
related to SERVER-17368 Create windows SSL zip file with Open... Closed
is related to SERVER-15400 Create Windows Enterprise Zip File wi... Closed
Operating System: ALL
Steps To Reproduce:

1) Download any zip release from https://www.mongodb.org/dl/win32/x86_64-2008plus-ssl?_ga=1.249432199.1028970917.1409164818
2) Extract to any directory
3) Run mongod in an environment that does not have msvcr120.dll or msvcp120.dll on the PATH.

Sprint: Dev Platform 2020-06-01
Participants:

 Description   

The Windows zip releases do not contain the Visual Studio 2013 redistributable libraries.

The msi installers carry the libraries and install them to %WINDIR%\System32.



 Comments   
Comment by Andrew Morrow (Inactive) [ 18/May/20 ]

I am closing this ticket as won't fix. MongoDB ships two types of releases for Windows: zipfiles and MSIs. If you install our MSIs you will notice that they include the merge modules for the redistributable runtime libraries. This allows us to automatically install the necessary library support should the system not already have it.

Unfortunately, the same is not possible with the zip distribution, because a zip distribution does not give us an opportunity to run install actions when you unpack it. So there is no way for us to actually install the redistributable runtime libraries. We could bundle the vcredist executable into the zip file (and, in fact, the enterprise zip does so), but that still requires manual intervention to install it.

Directly including the required DLLs in the zip packages bin directory would work, but is inadvisable from a security perspective: it would mean that MongoDB would need to re-issue packages every time a vulnerability was disclosed in the Microsoft runtime environment. Any lag between disclosure and our issuing a release could leave running servers vulnerable.

Since including the DLLs directly isn't an option, and since including the vcredist package doesn't avoid the need for a manual step one way or another, there isn't much we can do to improve the situation with the zip file. Our recommendation is that if you want automated installation of the redistributable runtime libraries should your system not have them, you should install via the MSI instead of using the zipfiles.

Comment by Paul Sukhanov [ 18/May/20 ]

Just downloaded the .zip of 4.2.6 and this is still an issue on Windows 10  

I'm bundling mongod with another software and would prefer to use a static build if available... but looks like I might have to build it myself...

Comment by Gary Gregory [ 11/Apr/18 ]

Agreed, my testing is now hard coded to Mongo 3.4 due to this bug.

Comment by Benjamin Berman [ 11/Apr/18 ]

Minor?! It's a blocker! There are 200 packages that use de.flapdoodle.embed.mongo. Please fix this. The number of workarounds that dependent packages use is staggering.

Comment by Gary Gregory [ 09/Apr/18 ]

I am also a user of https://github.com/flapdoodle-oss/de.flapdoodle.embed.mongo and this limits what I can do.

Comment by Phillip Wirth [ 22/Mar/18 ]

Can we get a fix for 3.6 too?

I am a maintainer of a lib which relies on the windows zip distributions. It breaks more and more builds on windows machines :/

https://github.com/flapdoodle-oss/de.flapdoodle.embed.mongo

Comment by Ramon Fernandez Marina [ 07/Mar/18 ]

Please see SERVER-32877 for other missing libraries reported by users when considering this ticket.

Generated at Thu Feb 08 04:10:56 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.