OPERATIONAL DEFECT DATABASE
...
...
BugZero found this defect 2662 days ago.
Log Name: System Source: Service Control Manager Date: 6/25/2017 6:25:05 PM Event ID: 7024 Task Category: None Level: Error Keywords: Classic User: N/A Computer: DESKTOP-60TK3U1 Description: The MongoDB service terminated with the following service-specific error: Cannot create another system semaphore. Event Xml: Unknown macro: {555908d1-a6d7-4695-8e1e-26931d2012f4} " EventSourceName="Service Control Manager" /> 7024 0 2 0 0 0x8080000000000000 4004 System DESKTOP-60TK3U1 MongoDB %%100 4D006F006E0067006F00440042000000
aleksey.savateyev commented on Mon, 26 Jun 2017 18:24:43 +0000: The mongod.cfg was pointing to a wrong data folder. Started as soon as I changed to the right one. Yes, my bad, but the error could be way more descriptive and helpful. What is the word "semaphone" doing in end-user message???
Install latest 3.4.5 release for Win2008 R2 with SSL (64-bit) Unpack the dump from some other 3.4 WT database into data Install the Windows service using --install parameter and typical mongod.cfg Start the service using "net start"
