Clash Royale CLAN TAG

MongoDB : A Service Specific error occurred :100

I have just installed "mongodb" on Windows, while starting it, the following error appears

A Service Specific error occurred :100

Any Suggestions?

net start MongoDB

datadb

log

7 Answers
7

The reason for this error message is that you have another process already established.
In my case it was the mongod.exe file I had opened in CMD, when I closed it and restarted the net start MongoDB command, it connected successfully.
BTW i am using Windows 10 current build as of July 2017 with MongoDB 3.4

mongod.exe

net start MongoDB

Please try running the below commands as Administrator in the comment prompt.

mongod --repair

mongod --repair

mongod --remove

mongod --remove

then like @Yahya did, specify the log path,

mongod --install --logpath C:datadblogmongo.log

mongod --install --logpath C:datadblogmongo.log

net start mongodb

net start mongodb

Hope it helps.

Check your Mongo log in your /data/log folder (which you should have created during install), there might be a solution in there.

I had this issue, I checked the System Event Log which gave me the following:

The MongoDB service terminated with the following service-specific error: Cannot create another system semaphore.


When I checked the log I found this:

Unable to create/open lock file: c:datadbmongod.lock The process cannot access the file because it is being used by another process.. Is a mongod instance already running?


Turns out I'd started the process manually in another command window so it couldn't start it again. You may have a different issue but the log should tell you what is going on!

For me, somehow directories I have specified for db and log config file were not auto created.

dbpath=datadb

logpath=datalogmongo.log


so I created them manually then ran the command again and service started.

I am using v3.4.9 om Windows 10

execute the command

"C:Program FilesMongoDBServer3.6binmongod.exe"


and check which error is displayed

Running mongod.exe through a service does not display the error messages. In my case, i didnt created the directory /data/db, which i specified in my configuration file. My Configuration file is based on the docs create-a-configuration-file

The error was only displayed after executing the command directly

For example mongoDB version 3.6 is installed, and the installing path of MongoDB is "D:Program FilesMongoDB".

Create folder D:mongodblogs, then create file mongodb.log inside this folder.

D:mongodblogs

mongodb.log

Run cmd.exe as administrator,

D:Program FilesMongoDBServer3.6bin>taskkill /F /IM mongod.exe
D:Program FilesMongoDBServer3.6bin>mongod.exe --logpath D:mongodblogsmongodb.log --logappend --dbpath D:mongodbdata --directoryperdb --serviceName MongoDB --remove
D:Program FilesMongoDBServer3.6bin>mongod --logpath "D:mongodblogsmongodb.log" --logappend --dbpath "D:mongodbdata" --directoryperdb --serviceName "MongoDB" --serviceDisplayName "MongoDB" --install


Remove these two files mongod.lock and storage.bson under the folder "D:mongodbdata".

mongod.lock

storage.bson

Then type net start MongoDB in the cmd using administrator, the issue will be gone.

net start MongoDB

I manually created datadb directory and it solved the problem

By clicking "Post Your Answer", you acknowledge that you have read our updated terms of service, privacy policy and cookie policy, and that your continued use of the website is subject to these policies.