I am trying to install CouchDB on a Windows 2008 R2 standard version server and it starts the couchdb service running but I am unable to access the couchdb url. And below is the error:
Erlang R15B (erts—5.9) [source] [smp:16:16] [async—threads:0]
Eshell V5.9 (abort with ^G)
1} ("init terminating in do_boot",{{badmatch,(error,{{app_would_not_start,os_mon
}, couch_app.start,[normal,["../etc/couchdb/default.ini","../etc/couchdb/local.i
ni"]]}}}},[{couch,start,0,[{file,"d:/relax/couchdb/src/couchdb/couch.erl"},{line
,18}]},{init,start_it,1,[{file,"init.erl"},{1ine,1041}]},{init,start_em,1,[{fi1e
,"init.erl"},{line.1022}]}]}}
Crash dump was written to: er]_crash.dump
init terminating in do_boot {}
Abnormal termination
When tried on Windows 7 the same installer works fine. Please help on how to fix the issue as it has to run on the Windows 2008 R2 Standard server machine.
First thing to check is if CouchDB starts from a command prompt, without running the service. The installer leaves an icon on the start menu for this, or you can try c:\couchdb\bin\couchdb.bat as well. I recommend installing to a filename without spaces just to ensure Windows is happy.
BTW you don't say what version/release of CouchDB this is, nor where you got it; R15B is not included in the recent official builds. I'd recommend the latest official release from http://couchdb.apache.org/#downloads which uses R16B02 and seeing how you get on.
Related
I'm new to PowerShell, so this may be a basic oversight.
On windows 10 pro (for development) and Windows Server 2016 (target environment) I have installed the latest released version of PowerShell.
(Get-Host).Version gives Major 6, Minor 1, Build 0, Revision -1.
My first mistake? as a version of PowerShell is already installed by default?
The process I am trying to automate is to share a backup cartridge drive from host physical machines, and access it as a network share for the VMs (Hyper-V) to backup to. In development I'm just using a USB attached drive, but errors are the same in both environments.
I keep getting errors in any of the SMBShare commands :
Get-SmbShare, Remove-SmbShare, New-SMBShare.
The errors are of the format:
"The term 'Get-SmbShare' is not recognized as the name of a cmdlet,
function, script file, or operable program"
I am running Powershell as administrator, and getting the same errors when typing directly, or from running a script.
Is there something I need to add/import to use SMBShare commands ?
PowerShell has fractured; everything up to v5.1 was Windows only, then v6 was made cross-platform by moving it to a new foundation, and that lost a lot of compatibility.
Your easiest way forward is to use PowerShell 5.1, unless you need v6 for some specific feature. Or to use 6 to launch 5.1 and run a script, the same way you might launch Python or VBScript engines to run a script.
But if you are staying with 6, then there is another option - Microsoft have released a WindowsCompatibility Module - still an early release candidate, so not heavily tested. This brings a way to run Windows modules inside PS v6 (only on Windows, not cross platform).
You would need to install it, with this as an administrator:
Install-Module WindowsCompatibility
Then you can:
Import-Module WindowsCompatibility
Import-WinModule SmbShare
Get-SmbShare
Installed mongodb on Windows.
Mongodb: 3.4.3 - Windows Server 2008 R2 64-bit, with SSL support x64
OS: Windows 7 64-bit
When I run mongod.exe or mongo.exe this error occurs
The application was unable to start correctly (0xc000007b). Click OK to close the application
What can I do to get rid of this error?
Thanks to everyone who helped.
I got rid of this error by updating Visual C++ Redistributable. But note that before this i also updated my Net Framework, DirectX and drivers for video-card.
Go to my Computer
Properties (Under windows edition check if service pack 1 is listed)
If not, make sure you have following windows updates installed on your system:
KB958488 (dot NET Framework) (<=10mb) (msu file)
KB2533552 (a prerequisite for service pack 1) (<=10mb) (msu file)
KB976932 (service pack 1) (around 900 mb) (exe file)
KB2999226 (Visual C++) (<=2mb) (msu file)
Add your mongo db bin directory to Path (Environment variable):
Example >>> C:\Program Files\MongoDB\Server\3.4\bin
Go to control panel → system and security → system → advanced system settings → advanced → environment variable → system variables → Path
Restart your system
Create a file C:\data\db
then run cmd
change directory to mongodb bin
run mongod
Enjoy....
I was facing the same issue with mongodb 3.6.5 version on my windows 7. I tried updating .net and vc++, nothing worked. Then I downloaded and installed an older version of mongodb, version 3.2 and it worked!
I have the issue while running mongod (Error 0xc000007b when launching mongod.exe / mongo.exe).
I solve the problem by using these following steps
1 step:uninstall the latest version of mongodb currently (4.2).
2 step: install mongodb version(3.0.15) don't worry its running all the feature that given by 4.2.
3 step:install the mongodb 3.0.15 in installing it gives the option (complete ,custom and other) you select the complete option and install.
4 step: Go to the program file check the mongodb folder inside the mongodb folder go to bin and run the mongod application .On this time the error will gone..
I solved this error by installing all the Microsoft Visual C++ re distribute files .
i.e. all the versions .
You need correct version to run mongo 2013 and 15 didnt work but 2019 did .
I have just downloaded and installed Groovy 2.3.3 using the Windows installer. While trying to run some of the examples using groovyclient (which tries to start groovyserver), I receive the following error.
\Groovy\Groovy-2.3.3\bin\.. was unexpected at this time.
My Groovy_Home is as follows:
GROOVY_HOME=C:\Program Files (x86)\Groovy\Groovy-2.3.3
The full output is as follows:
C:\Users\Greg>groovyserver
Groovy home directory: "C:\PROGRA~2\Groovy\GROOVY~1.3"
Groovy command path: "C:\PROGRA~2\Groovy\GROOVY~1.3\bin\groovy.bat" (found at GR
OOVY_HOME)
\Groovy\Groovy-2.3.3\bin\.. was unexpected at this time.
I am running on Windows 7 Home Premium - 64 bit
Not sure if this is a universal solution but here's what worked for me on two separate machines running Windows 7 Home Premium (64) and Windows 7 Enterprise (64).
I tried this out with both Groovy 2.2.1 and Groovy 2.3.4
I simply uninstalled Groovy and installed it again, this time outside the Program Files directory. The groovyclient and groovyserver tools started working properly and I no longer get these errors.
Apparently, Groovy has some trouble running the executables if they're installed in Program Files. I'm not sure why this happens. I suspected that it may have something to do with spaces in the catalog's name but I successfully ran groovyclient installed in such a directory ( C:\Groovy\Test groovy with spaces\Groovy-2.2.1 specifically). Therefore, I suspect this has something to do with permissions.
If anyone has an idea why this happens, feel free to expand upon this answer. Maybe the exact reason this error occurs is different and I just managed to work around it by changing the installation directory.
Has any one encountered the error: Could not create Java Virtual Machine error while installing IBM Websphere ILog JRules Studio 7.1.1? I have Windows 7 64 bit OS but this error could happen on any Windows machine. By default IBM ships the package for 32 bit so our installation team tried with 32 bit JDK 6 (with many minor versions) for many days but could not figure out. I have posted my own solution below. Check this out and save your life.
You usually start installation by running JRules_V711_CZLX7ML.exe file on windows. It will extract all resources on your temp directory and you might encounter error: "Could Not Create Java Virtual Machine". Just follow these steps and it "might" solve your problem:
1. Go to your temp directory by typing "%temp%" in Start-> Run or Windows Explorer.
2. Look for directory something like: I1403739667. Go inside this directory.
3. Open command prompt and go to I1403739667/Windows/resource/jre/bin
4. Run command: java -version
5. If you see following error, go further otherwise you might have some other problems:
JVMJ9VM011W Unable to load j9jpi24: The specified module could not be found.
Error: could not load Mercury Interactive support. Please run the setup again.
If the problem persists please contact Mercury's Customer support.
JVMJ9VM011W Unable to load j9jpi24: The specified module could not be found.
JVMJ9VM015W Initialization error for library jvmhook(-3): JVM_OnLoad failed
Could not create the Java virtual machine.
This happens if you have installed HP Quick Test Professional which used to be Mercury before HP bought over.
Right click on your computer icon on desktop and look for following environment variable: IBM_JAVA_OPTIONS
Either rename it to IBM_JAVA_OPTIONS_DONOTUSE or delete it.
Try installing again.
NOTE: I had tried to by pass this error by changing the vm property in Rule Studio.lax file to use JDK 6 32 bit installed on my windows machine and was able to install successfully but there were just too many Rules compilation errors which would not make any sense. So NEVER try to use your own JDK. You have to use the IBM JDK shipped as part of Rule Studio.
All,
Am trying to get Node.js to work on Vista machine.
I installed Cygwin (as per the Github instructions) which appears to have been installed correctly. However, none of the commands are executing.
Are there any tutorials for the stages after the Cygwin installation?
PROBLEM: When any command is executed, I get 'Bash: command not found' error.
Not even command like 'c:\cygwin\bin' is executing.
When I type 'user' in cygwin command prompt, I get 'ntvdm has encountered an system error. Parameter incorrect'.
I thought the above error may be due to the firewall, disabling the firewall did not have any effect, running the program with admin rights also did not change the results...
Am confused and would love to get some guidance on what steps to go with next on getting Node.js up and running on a Windows Vista machine.
Many thanks,
UPDATE1:
We managed to make a bit more progress. It appears that we had not installed all the relevant files related to Cygwin. Upon re-download and reinstalled, it ran well, however, we have driven into another error. Error we get:
How to compile/install node.js(could not configure a cxx compiler!) (Ubuntu).
We followed the instructions as per the above thread (3rd post from top for Windows machines), however, we are still stuck at the same error.
Any guidance please?
Have you tried just using the Windows self contained binaries? http://node-js.prcn.co.cc/ This way you actually don't need to bother with Cygwin.
At first, i tried it your way too, using Cygwin. After smashing my head for the 10th time against a wall i just stopped trying and found a much cleaner solution.
I'm using VirtualBox running a Debain guest system to locally develop on my Windows 7 machine. Using VirtualBox, you can easily set up shared folders or port forwarding for node apps between your Windows machine and your Debian guest system.
Since you are using a plain Linux-system, all the compiling-pain is blown away.
If you plan to run node.js in production on a windows system: don't. I hardly believe node.js will be ever stable enough on windows-based systems using MINGW/Cygwin...
People seem to run into problems with Cygwin because they think that they are using a Windows machine.
If you install Cygwin, and open a bash shell prompt using the Cygwin icon, you are now in a UNIX environment and everything works the same as it would on UNIX. That includes building node.js.
I think you added some info to the question and I can see your problem. Yes, normally on Cygwin it has been possible to build node.js just as you would on any UNIX system, but that is no longer possible on Windows 7. Before running ./configure you have to:
Close all cygwin apps.
Double-click on C:\Cygwin\bin\ash.exe
Run ./rebaseall and when it completes, run ./perlrebase.
exit from the ash shell window.
At this point Cygwin will be back to normal and you can ./configure and make install.