I tried to install couchDB on windows 10.
now I know that there was a problem with couchDB and windows 10 creator update,
but the problem was supposed to be fixed in version 2.1.0 like they said in the apache issues https://issues.apache.org/jira/browse/COUCHDB-3395.
I searched everywhere and all the answers refer to CouchDB 2.0.0 with windows 10 creator update, but I tried it anyway.
switched the nssm to version 2.24
tried to run from the cmd
run it manually from the event viewer
even reinstall and restart the computer
but nothing worked.
I got this problem when Im trieng to run the couchDB manually from the services.
and when I go to the event viewer this is the error:
I'm really clueless!
Does anyone have an idea?
Related
I'm trying to run the planet scale cli and the docs said to install mysql,
After I installed mysql shell 8 and tried to run it, it throws:
api-ms-win-core-path-l1-1-0.dll missing
where does api-ms-win-core-path-l1-1-0.dll come from?
and how do I add it?
Windows 7 64bit, powershell 2.0 , windows .net framework 4
I filed a mySQL bug report and this is what they said:
Thank you for your bug report.
However, this is not our bug.
This is a missing Windows system library. You can read more about that
here:
https://wiki-drivers.com/du-101/?m=src_evp_adwords_du_dll_e&build=ppc&content=ppcdudll&build=ppc&kw=api-ms-win-core-path-l1-1-0.dll&gclid=EAIaIQobChMIl6LTgbjJ-wIVmeFRCh1KvwH_EAAYASAAEgJWwvD_BwE
alternative solution would be to try upgrade to PowerShell 5 and install via scoop or something of that nature
I've yet to try this solution due to my windows 7 laptop's screen messing up causing me to upgrade my laptop.
Thought it would be helpful to follow up with my findings
Hoping this is the right place to ask this. I'm trying to learn React Native and I'm using Expo as my medium for deployment, but I'm finding that I'm literally getting 20 minutes at a time before my browser fails to connect with the error code ERR_CONNECTION_FAILED. I've tried the following:
netsh winsock reset, then the related ipconfig commands for flushing DNS settings
Clearing browser caches
Updating drivers
I'm at my wits end as the only thing that completely solves it is restarting my laptop, which for obvious reasons isn't feasible every 20 minutes, so I'm hoping somebody can help.
I'm experiencing the same issue with Expo in this environment:
Windows 10, version 1909 (OS build 18363.476)
using WSL (Windows Subsystem for Linux) with Ubuntu 18.04 LTS
These links were useful to learn why this is happening:
https://github.com/expo/expo-cli/issues/99
https://github.com/microsoft/WSL/issues/2913
https://github.com/microsoft/WSL/issues/3951
In essence, this issue seems to be due to a problem with WSL. Per a post in the first link, I tried the alternative to restarting the computer and it worked - it made the ERR_CONNECTION_FAILED problems disappear...for 20 minutes. That alternative is as follows:
WIN+R -> services.msc
Find LxssManager
Right-click -> Restart
This restarts the WSL service which also means that the WSL instance that was running gets terminated. This is less than ideal, but at least a computer restart is avoided. The third link says this WSL problem is fixed in Windows Insider Build 18890.
I am now considering spinning up a VM to run Ubuntu instead of trying to use WSL for Expo projects.
I uninstalled the latest Windows updates, and the problem has not surfaced since.
I am currently running a 5.x version of XAMPP on a Windows 10 box, which has been working really well.
However I think it is time I look at upgrading to version 7.x to test my sites before I get my production VPS server to run php 7 etc
Can I install the new version in a separate directory (e.g. xampp7) and choose what xampp to run as needed via its control panel? Will each install know what version of php etc to load and use while that version is operating?
I have not tested this yet, I didn't want to risk stuffing up my existing install :)
Cheers
When I run 'meteor update', it says that I have the latest version Meteor 0.8.3. When I specify the release using '--release 0.9.2.2', it says that the version is unknown.
What's going on here?
I tried reinstalling but got the exact same behavior.
Unfortunately, Meteor does not support Windows out of the box. That means that it has to be ported, which takes some time. So if you want the newest Meteor version as soon as it is released, you can either run a VM with Linux (for example, using Virtualbox) or install Linux alongside Windows on you computer (make sure to back up all data before, though!)
Or you can just wait becuase as saimeunt pointed out, Meteor will be ported to Windows soon.
From March 31, 2015, meteor is supported on Windows
https://www.meteor.com/install
When my laptop wiped a few months back, I had to re-install, and thinking I didn't have the original disk image anymore, I downloaded and installed what was then the latest version of XAMPP (1.7.2a). I quickly became annoyed with some of the quirks of the new version's included version of phpMyAdmin, however, and so I frankly stopped bothering with it for a while.
Recently, I stumbled across the disk image for the original version I installed (0.7.4) again, and so I decided to attempt to downgrade it by following the instructions on their forums for uninstalling it in OS X (link), after which I installed the older version. It appeared to have installed just fine, but when I attempted to access phpMyAdmin, I ended up getting the following:
Existing configuration file (./config.inc.php) is not readable.
Removing, logging out, and re-installing again still produced the same error (in fact, the running commentary on the XAMPP control panel seems to indicate it may have screwed up XAMPP's Apache installation somehow, albeit pages still appear to load properly).
Shy of an archive and install, what options do I have to try and eradicate all traces of the old installations of XAMPP so it can start fresh with an installation of my desired version?
Deleted the folder for the current installation, installed the desired version on top of it. Re-installed Snow Leopard and it fixed the installation such that it's been running without issue since.