I saw a tutorial that said to run this:
C:\mongodb\bin\mongod.exe --config C:\mongodb\mongod.conf --remove
but that command does not work since there is no mongod.conf file in the mongodb folder in my Windows. Besides, I don't want to only stop the service, but to remove everythin, including files, services, etc. Is that possible?
I am using Windows 8.1.
The command...
C:\MongoDB\bin\mongod.exe --config C:\MongoDB\mongod.conf --remove
Is used to just remove the service.
If you don't have a mongod.conf and/or no longer have the .msi installer (who keeps that stuff?) then:
win-key + r and run regedit
Navigate to Computer\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\MongoDB (or just cut and paste this path)
Once there right click on MongoDb and click Delete. Service is now gone.
Goto C:\mongodb (or where you installed it) and delete directory. Mongodb is now gone.
Check your system environment variables to see if it's in your path (It will not exist unless you put it there).
Alternatively you may be able to re-download the msi and try using that.
EDIT: If you forgot to stop the service first or if it left dead orphan in services then open CMD or other shell as administrator and run the command: sc.exe delete MongoDB ... you should see: [SC] DeleteService SUCCESS
Use the command below to delete the service:
run cmd as Administrator
sc delete MongoDB
Since you're using Windows, just run the same .msi file that you installed it with.
It should be in your downloads folder, i'm guessing.
Once you opened the file, press next and there you will have the complete access to remove your MongoDB installation.
Run the mongo-db installation file that ends with .msi.
You'll see the remove option there, click on it.
Then you could delete the mongo-db files that are in your computer.
Go to services.msc and stop MongoDb service .
Delete all the folders in C: drive where MongoDb Folders exists.
Remove data folder if you created previously.
Type cmd in start and ryt click on cmd and select run as
administrator and type below Command.
sc delete MongoDB
If it throws some error like service not exists then open properties of the service and check whether you are giving the proper service name.
net stop MongoDB : This will stop your mongo server(in case of windows) then simply delete that MongoDb folder.
Related
when I try to install any dependence in command prompt get this error message and tried to google but nothing any one to help me please
please I need help someone to help me
try installing locally. and add this path to your system variable: C:\Program Files\nodejs
Reinstall the node.
You have two ways to install Node.js on your computer.
Option 1 – Setup by running the .msi installation file
Its a typical Windows installation and automated. No need to add
entries in environment varaiable
Option 2 – Setup by extracting .zip file
This method does not require admin access and can be used to install
on nodejs on a system on which you dont have admin access such as you
official laptop or desktop.
Removing nodejs is as simple as deleting the folder. You will have
to add entries in environment variable if you want to execute node
command from any location in windows command prompt. https://nodejs.org/en/download/
Based on the screenshot.your access is denied.Would suggest starting the terminal as an administrator before running the command.
I have issue with installation Mongo DB library in Azure Function. I can find, how to show console see on pic 2. I found some instructions 1, but it run on older interface of Azure, in my case I can't see it. I hope it's not restricted by free subscription.
Old instructions:
My case:
If you want to add the npm packages manually you can do it using the terminal in the function app.
The terminal will be under the Advance tools tab under developer tools section. Just click on go.
After that a new tab will open where your bash shell will be located.
Now just run the command to install the npm packages.
npm install mongodb
Then restart the function.
An error message pops out when I try to connect to the management console. The version is Kapow 10.1.0 master nightly 2370 x64.
The Error message is:
Unable to register to the default cluster: ManagementConsole failed to start: Spring subsystem failed to load.. Retrying
I had to delete the folder on Kapow Appdata User Profile folder, for example:
C:\users\<user>\appdata\local\Kapow
And then restart the RoboServer/Management Console.
This will create a new configuration and from there you can continue the installation (bring up the management console, enter the license, etc)
Please Delete Appdata and open localhost:50080 Management console and delete and then add Cluster settings again.
Now restart the Design studio and open it up again. Make sure you are using same objectdb.
You only need to rename the folder:
C:\Users\<user>\AppData\Local\Kapow\10.ur.version\Data
Then rerun the Management console as Administrator.
If you are still facing the same issue, please uninstall Kapow and install it again (also make sure you renamed the Data folder).
I'm trying to figure out if there is a way to change the Node.Js command prompt default path = C:\users...> (default when the prompt is launched) or C:\Windows\System (if launched with administrator privileges), to the location of the folder where i'm working.
Normally I have been doing C:\users..> cd C:\xampp\htdocs..... to navigate to the test folder and run test. Although once the command prompt is closed it reverts back to C:\users...>.
To achieve what I want I came across using Z:>C:\xampp\htdocs\projects.... but this returns access denied with or without administrator privileges. Even if I try C:>C:\xampp\htdocs\projects.... still get the Access Denied for some unknown reason. To be honest I don't know what Z:> or C:> will result.
Is it possible to change the default prompt path to the path of the directory I am working in so that every time command prompt is launched it goes to that directory? In this case C:\xampp\htdocs\projects.... instead of C:\users...>
This seems like a general windows CMD question. Simply change the start up directory for CMD. See this SO post.
Once you're in that directory, you should be able to run the node command as normal.
Look inside your default nodejs installation folder for a file called nodevars.bat. Here is my path:
C:\Program Files\nodejs\nodevars.bat
Open this and look towards the bottom--the line I needed was on the very bottom. Here is the line from the git master:
if "%CD%\"=="%~dp0" cd /d "%HOMEDRIVE%%HOMEPATH%"
I changed mine to
if "%CD%\"=="%~dp0" cd /d "C:\Users\David\Desktop\work\J\math"
And now I am happier.
I had the same question, today, 4/11/22, and DuckDuckGo provided this as the number one result for my query. Since the question appears to be unanswered, I will try for those who might show up later.
Maybe someone can tell me what I missed installing nodeJS to jenkins, because when I want to execute shell script npm update I get error npm: not found.
I installed jenkins nodejs plugin then added installer:
After I created job with prams:
What I need to do more, to have accessible npm in any jenkins job?
It works for me. The only difference is that where you have a text box that reads "0.12.7", I have a popup menu that reads "Node.js 0.12.7". Maybe something has gone wrong and you should delete the installer and add it back?
Windows users, did you restart?
Do keep in mind that you need to restart active processes after installing npm.
During installation the folder of your npm.cmd is added to the PATH variable. However, active applications don't refresh their PATH variable automatically. That also holds for your active Jenkins service (and its child processes). They are still running with an old version of your PATH variable.
In other words, you need to restart the Jenkins service (or restart your entire system). Once restarted, Jenkins will have an updated PATH variable, and it will be able to find the npm.cmd processes and others.
What's wrong with using absolute paths?
Using the full path is not a solid solution. A package.json file can contain references to other cli processes (e.g. node, ng, react-scripts, npm-run-all, ...). You will probably have similar issues there. There is no way to keep up and reference all of them with full paths.