CouchDB 2.0.0 on Windows 10

2016-09-23 Thread John Le Brasseur
Hi. Firstly a very well done to everybody who worked to reach CouchDB 2.0.0. I uninstalled my working CouchDB 1.6.1 on my Windows 10 machine. Windows retained the Service link, however, so I removed it with regedit. I restarted the windows machine and installed CouchDB 2.0.0.(No options were

CouchDB 2.0.0 on Windows 10

2016-09-23 Thread John Le Brasseur
Hi Following up on my recent post, I found this in my couchDB.log: [info] 2016-09-23T11:22:33.225000Z couchdb@localhost <0.202.0> Starting couch_sup [error] 2016-09-23T11:22:33.239000Z couchdb@localhost <0.205.0> CRASH REPORT Process (<0.205.0>) with 0 neighbors exited with

Re: CouchDB 2.0.0 on Windows 10

2016-09-23 Thread Joan Touzet
Hi John, Sounds like whatever CouchDB 1.6.1 left behind is causing you issues. As I wasn't responsible for that installer I'm not sure I can suggest anything other than a full uninstall and reinstall of CouchDB 2.0.0. After uninstalling, be sure to completely delete the left behind C:\CouchDB

Re: CouchDB 2.0.0 on Windows 10

2016-09-23 Thread John Le Brasseur
Hi Joan I have reinstalled quite a few times but always with the same result. You say 9 files but have listed 8. I presume 8 is the correct amount. My installation directory has no spaces in it. How is it that the (Apache CouchDB) service is running if it is not loading properly??? If I

Re: CouchDB 2.0.0 on Windows 10

2016-09-23 Thread Joan Touzet
nssm is correct. Services cannot be batch files, so we use the (freely licensed) nssm.exe to launch our couchdb.cmd batch file. You are right, I entered it wrong. If you stop the service and run couchdb.cmd by hand, do you still get the same error? -Joan - Original Message - > From:

Re: CouchDB 2.0.0 on Windows 10

2016-09-23 Thread Jason Gordon
I had a similar error (Windows 8) when I tried to start CouchDB 2.0 on a non-standard port(s). When I put the httpd, and ssl ports back to their original values, it then started for me. Jason Gordon | Principal | A S S U R E B R I D G E Office: +1 888 409 6995 | Mobile: +1 978 885 6102

Re: CouchDB 2.0.0 on Windows 10

2016-09-23 Thread John Le Brasseur
Hi Joan. Same result. On 23 September 2016 at 17:45, Joan Touzet wrote: > nssm is correct. Services cannot be batch files, so we use the (freely > licensed) nssm.exe to launch our couchdb.cmd batch file. > > You are right, I entered it wrong. > > If you stop the service and

Re: CouchDB 2.0.0 on Windows 10

2016-09-23 Thread Nick North
It doesn't help much, but I had slightly similar problems on Win10: after uninstalling 1.6.1, the service for 2.0 did not install at all. But couchdb.cmd worked fine, for what it's worth. Installing on a clean machine, with no CouchDB history, worked perfectly. Unfortunately I haven't been able

Re: CouchDB 2.0.0 on Windows 10

2016-09-23 Thread Joan Touzet
I will say that in my testing on Windows 10, IE wouldn't connect to a localhost URL (http://localhost:5984/) but Firefox would. CONNECTION_REFUSED suggests Couch isn't running at all. -Joan - Original Message - > From: "John Le Brasseur" > To:

Re: CouchDB 2.0.0 on Windows 10

2016-09-23 Thread John Le Brasseur
Hi Nick, Jason. Thanks. It must be a 1.6.1 uninstall issue somewhere I believe. By the way, if I stop the 2.0 service when it is running, a message comes up: "Windows could not stop the Apache CouchDB service on local Computer. The service did not return an error. This could be an internal

Re: CouchDB 2.0.0 on Windows 10

2016-09-23 Thread John Le Brasseur
Hi. Notes: One browser reports: "ERR_CONNECTION_REFUSED" permissions? and Safari on my Windows said: "Safari can't open the page http://127.0.0.1:5984/ because Safari can't connect to the server 127.0.0.1. Windows Network Diagnostics said: "Problem found The remote device or resource won't

Re: CouchDB 2.0.0 on Windows 10

2016-09-23 Thread Nick North
Chrome, Edge, and IE all work for me on Win10, connecting to localhost. Nick On Fri, 23 Sep 2016 at 20:43 Joan Touzet wrote: > I will say that in my testing on Windows 10, IE wouldn't connect to a > localhost URL (http://localhost:5984/) but Firefox would. > >