[SERVER-47259] Windows MSI Installer "Service Failed to Start" Error Created: 01/Apr/20 Updated: 02/Apr/20 Resolved: 02/Apr/20 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Packaging |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Andrew Feierabend (Inactive) | Assignee: | Unassigned |
| Resolution: | Duplicate | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Operating System: | Windows | ||||||||
| Steps To Reproduce: | 1. Download the MongoDB 4.2.5 Windows MSI Installer from the Download Center. Both Community and Enterprise editions have this issue. 2. Proceed through the install steps:
3. Error during "Starting services" |
||||||||
| Participants: | |||||||||
| Description |
|
When installing MongoDB 4.2.5 on Windows 10 using the MSI package:
The follow error often appears:
Status above progress bar just before error was "Starting services" Tested with an administrator account. The following custom directory locations all failed when I used the "create a new folder" button in the installer:
(none of these folders were present on filesystem after exiting the installer post-error, whether using either "cancel" or "ignore"). The following custom install directory locations all failed without using the "create a new folder" button in the installer (i.e. using an existing directory):
This occurs with both Community and Enterprise editions. I only have a few Windows 10 boxes to test on at present unfortunately, but this occurs on all of them. Probably due to Windows' UAC and permissioning restrictions, so there may not be a ton we can do about this, but I imagine it bears looking into. I'd like to create a DOCS ticket to update our Windows MSI install instructions with any findings or recommendations. The initial report of this issue came from a DOCs reader through our feedback channel. |