Trying to run MongoDB as a service

[q0paz]

I have seen quite a few questions on here regarding trying to run MongoDB as a service on Windows server.

Win Server 2012 R2 Standard.

Can run it from the console no problem.

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. 

The Error message is the 1053 timeout :

 

"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."

"A timeout was reached (600000 milliseconds) while waiting for the MongoDB service to connect."

EventID 7000 and EventID 7009 respectively both timestamped the same as the start entry.

I have seen the examples with the registry mod to the ServicesPipeTimeout and changed it. 

However  it is not actually timing out. The call returns instantly, the error messages are both timestamped the same and there is no delay before the error is returned. So this is obviously not the issue and it therefore makes no difference.

I also tried running the service under different accounts and also elevated the permissions for the account running the service. The service still failed to start.

From the console  mongod --config "C:\MongoDB\mongod.cfg" starts it from the console, indicating that nothing in the config itself is causing any error. 

However the mongod.cfg is :

 

systemLog:

  verbosity: 5

  traceAllExceptions: true

  destination: file

  path: "X:/data/log/mongodb.log"

storage:

  dbPath: "X:/data/db/"

the "ImagePath" value in the registry is 

C:\MongoDB\bin\mongod.exe --config "C:\MongoDB\mongod.cfg" --service

Nothing is written to the Mongo logs so it would appear that whatever is being passed to mongod.exe by the service startup is erroring immediately and the process is not even starting. 

Presumably mongod.exe takes different arguments depending on how the user wishes to start it ?

Is there an available source of any information about this ?

Are there any debug switches I can pass to the mongod.exe  ? Or other tools ?

Any other ideas how I can actually trap the real reason for the start error ?

Thanks.

Mongo 3.4 Community .

Trying to evaluate it properly.

[Момчил Божинов]

Hello,

whats X ? is it local to the server ?

Momchil

[q0paz]

Nope. X is a share on our data storage machine.

I had the issue of UAC unable to access the share but applied the registry hack detailed here 

https://technet.microsoft.com/en-us/library/ee844140(v=ws.10).aspx

I have subsequently added Everyone to the folder permissions and assigned full access...

.

[Момчил Божинов]

"I also tried running the service under different accounts and also elevated the permissions for the account running the service. The service still failed to start."

Have you tried running the service under the same user that was used to map that drive ?

[Kevin Adistambha]

Hi,

Have you had success in configuring your MongoDB service?

How did you install MongoDB? Are you following the procedure outlined in Install MongoDB Community Edition on Windows? You may want to review the section titled Configure a Windows Service for MongoDB Community Edition.

Best regards
Kevin

​