The service still failed to start.įrom the console mongod -config "C:\MongoDB\mongod.cfg" starts it from the console, indicating that nothing in the config itself is causing any error.Ĭ:\MongoDB\bin\mongod.exe -config "C:\MongoDB\mongod.cfg" -service I also tried running the service under different accounts and also elevated the permissions for the account running the service. So this is obviously not the issue and it therefore makes no difference. The call returns instantly, the error messages are both timestamped the same and there is no delay before the error is returned. I have seen the examples with the registry mod to the ServicesPipeTimeout and changed it. "A timeout was reached (600000 milliseconds) while waiting for the MongoDB service to connect."ĮventID 7000 and EventID 7009 respectively both timestamped the same as the start entry. " The MongoDB service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion. However trying to start the service either with 'net start MongoDB' from the command line or from the services snap in and it fails to start. I have seen quite a few questions on here regarding trying to run MongoDB as a service on Windows server.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |