...
When I start mongod.exe it crashes and tries to create a minidump file in it's installation directory. Obviously on Windows regular user/service accounts don't have write permission to C:\Program Files\. 2016-11-11T15:04:38.107+0100 I CONTROL [initandlisten] MongoDB starting : pid=4316 port=27017 dbpath=E:\AppicaptorData\data 64-bit host=ac-win3 2016-11-11T15:04:38.107+0100 I CONTROL [initandlisten] targetMinOS: Windows 7/Windows Server 2008 R2 2016-11-11T15:04:38.107+0100 I CONTROL [initandlisten] db version v3.2.10 2016-11-11T15:04:38.107+0100 I CONTROL [initandlisten] git version: 79d9b3ab5ce20f51c272b4411202710a082d0317 ... 2016-11-11T15:04:41.907+0100 I CONTROL [initandlisten] failed to open minidump file C:\Program Files\MongoDB\Server\3.2016-11-11T14-04-41.mdmp : errno:5 Access denied
JIRAUSER1268551 commented on Tue, 8 Aug 2023 15:00:10 +0000: Closing these issues and closing the containing epic. Please reopen if these are still a problem. JIRAUSER1261784 commented on Fri, 13 Aug 2021 08:06:44 +0000: Hi I am facing the same issue,any help will be appreciated JIRAUSER1259587 commented on Thu, 22 Apr 2021 05:12:58 +0000: Adding my vote for this ticket. I have also encountered this in mongo version 4.4.5. This started after my PC crashed. Tried reinstalling but still the same issues. Is there any workaround to fix this. Thank you. nick@innsenroute.com commented on Thu, 7 Dec 2017 22:28:26 +0000: Adding my vote for this ticket. I have also encountered this. mark.benvenuto commented on Tue, 15 Nov 2016 19:32:41 +0000: Currently, we chose the location of the mongod.exe executable for the dump location. We should add a config switch to choose the dump directory, and maybe change the default directory to be the Windows temporary directory. Our tests rely on the dump file being in the same directory as the binary directory so we will need to take this into account when we make a change. See https://github.com/mongodb/mongo/blob/549c3f4315fd95431a662e7a8eff880f00b1458d/src/mongo/util/exception_filter_win32.cpp#L57 ramon.fernandez commented on Sun, 13 Nov 2016 13:31:23 +0000: Thanks for reporting this, we're investigating.
This happens every time mongo crashes, e.g. because of an unhandled exception.