I'm running CouchDB 2.0 on Windows for development purposes. After applying the Windows 10 Creators Update, the CouchDB service doesn't start anymore. When I try to start it manually, I get a generic "unable to start service" error message.
CouchDB 2.0 on Windows uses the Non-Sucking Service Manager (NSSM) to run itself as service. Apparently, NSSM has problems after the creators update has been applied:
2017-04-26: Users of Windows 10 Creators Update should use prelease build 2.2.4-101 to avoid an issue with services failing to start.
Thus, the problem can be fixed by using the mentioned build of NSSM:
Download the pre-release build 2.2.4-101 from https://nssm.cc/download
Stop the CouchDB service through the Windows Services dialog (paused is not enough)
Overwrite nssm.exe in <CouchDbInstallDir>\bin with the one from the downloaded ZIP file (make sure you pick the right version 32 bit / 64 bit)
Start the CouchDB service
Related
From Windows installation - Operations Manual:
Neo4j can also be run as a Windows service. Install the service with bin\neo4j install-service, and start it with bin\neo4j start.
But where is the service installed? Googling with the query where is neo4j service installed doesn't give any meaningful result.
This question is about installing Neo4j as windows service in Windows OS. What you missed is the first step in installing Neo4j. In step 3 of topic 1 of Windows Installation, it says;
Right-click the downloaded file, click Extract All.
So when you do that step, it will prompt you where you would want the installation will be. It is not that clear where the location of the installation because you have to go thru the entire installation process to see it.
I had installed redis-3.0.504. Followed the installation instructions and now redis-server is running in the port
I had also installed redis in Windows services, but that is not running. I'm also not able to manually start the service. Getting the below error.
Any ideas to start the service?
Right-click in the service in Window Services and go to Properties.
Then go to Log On tab and select Local System account.
Click on the Ok button and start the service.
If you installed this via chocolatey, you need to add the following folder to allow the supplied redis.windows-service.conf to work:
C:\ProgramData\chocolatey\lib\redis-64\Logs
If you didn't install via chocolatey, a missing log folder is still likely to be the culprit.
The Redis port for Windows you are using has been deprecated.
As the last commit in that project suggests you can check out Memurai.
Memurai is a production grade software, actively maintained and freely available for development.
I'm following standard steps to install Azure IoT Edge on an AMD64 (Intel Celeron J1900) embedded PC. I'm running Windows 10 IoT Core build 17763.253 (latest LTSC version) and using offline install via remote PowerShell to work around some network issues (I was getting InvalidOperation exceptions from HTTP file download requests in PowerShell).
[192.168.137.26]: PS C:\Data\Users\Administrator\Documents> Deploy-IoTEdge -ContainerOs Windows -OfflineInstallationPath C:\Data\Users\Administrator\Documents
The container host is on supported build version 17763.
Skipping VC Runtime installation on IoT Core.
Using IoT Edge from C:\Data\Users\Administrator\Documents\microsoft-azure-iotedge.cab
Committing changes, this will cause a reboot on success. If this is the first time installation, run "Initialize-IoTEdge" after the reboot completes.
Then the system reboots, shows a quick progress bar that says "Loading files...", and then goes to a black screen. After several minutes of sitting there, it goes into the spinning-gears animation, which Bing tells me is for a system update but from which it never exits. No increase in the progress bar, nothing.
I did pull out the flash drive and inspect it on my PC. The C:\ProgramData\iotedge folder was correctly created during the install process, but that's all I was able to deduce. I'm not sure if there's a way to extract helpful logs from a flash drive or what I should do now.
What am I missing?
Note: Issue posted on GitHub as well.
You can use following command to view the logs.
. {Invoke-WebRequest -useb aka.ms/iotedge-win} | Invoke-Expression; Get-IoTEdgeLog
If the IoT Edge Security Manager is not running, you may try to check the config.yaml which is located in C:\ProgramData\iotedge folder.
More common issues troubleshooting please see this document.
I've been following the documentation on the official RabbitMQ site to install it on my Windows 7 computer. Installing Erlang and setting the environment variables has been trouble-free, but using the RabbitMQ installer has not worked out.
I have tried downloading the installer from both the GitHub and Bintray links as a regular user and administrator, but it does not seem to change the following problem: each time I double-click or right-click->Run as Administrator the installer it removes itself from the computer.
I've tried looking at processes in Task Manager, the Trash Bin, All Programs, and even in Control Panel\Programs\Programs and Features, but there is no sign that the installer has done it's job.
I ended up using Docker and Kitematic to run RabbitMQ image 3.6-management. The image works without any issues and appears to be a preferred option among my co-workers.
i have suite created in InstallShield which contains multiple packages. One of them requires .net 3.5 so in the package view i added Windows Feature NetFx3. Everything worked perfectly but today i got hands on a machine where instalation is terminated with the following errors in the log:
5-17-2017[02:03:10]: Getting feature list for initial feature items 'NetFx3'
5-17-2017[02:03:10]: Getting feature items for OS version 1000 (Client)
5-17-2017[02:03:10]: Final feature list for current item is: NetFx3
5-17-2017[02:03:10]: Installing Windows features for parcel 'PackageXY'...
5-17-2017[02:03:10]: Engine: property 'ISInstallStatus' value now 'Windows-Funktionen/-Rollen werden installiert …'
5-17-2017[02:03:10]: Engine: property 'ISParcelStatus' value now ''
5-17-2017[02:03:10]: CWindowsFeatureParcel::Install: using DismAPI on Windows 8 or newer
5-17-2017[02:03:10]: Engine: request for proxy handler, 0, 1
5-17-2017[02:03:10]: No source paths specified for DismEnableFeature
5-17-2017[02:05:19]: UI DLL: Resource 'Header_bckgnd.png' -> 'C:\Users\dummy\AppData\Local\Temp\{270DDFC5-A522-4510-8282-DE76EBB713E6}\Header_bckgnd.png'
5-17-2017[02:05:20]: UI DLL: Resource 'Header_bckgnd.png' -> 'C:\Users\dummy\AppData\Local\Temp\{270DDFC5-A522-4510-8282-DE76EBB713E6}\Header_bckgnd.png'
5-17-2017[02:05:26]: CWindowsFeatureParcel::CallDismApi result: 0x00000001
5-17-2017[02:05:26]: Windows feature install result status: 0x80070001
5-17-2017[02:05:26]: Failed installing Windows features for parcel 'PackageXY', error 0x80070001
5-17-2017[02:05:26]: Engine: property 'ISInstallStatus' value now 'IDS_SUITE_INTERRUPTED'
I have tried following:
run DISM /Online /Enable-Feature /FeatureName:NetFx3 /All /LimitAccess /Source:x:\sources\sxs and other variations of this command that i wasnt really sure what are supposed to do
disabled the feature manualy and re-enabled, multiple times in different order together with the .net 4.7 and run the setup with different configuration of the checked features.
Without luck so far, the thing that bothers me the most is its only happening on this particular Virtual Machine, which is up to date with the Windows Update.
edit: It is happening on every machine that has Creators Update installed, which comes with the .net 4.7
edit2: i did not solve this issue, i just removed the funcionality that is allowing the windows feature for the packages.
Our application requires .NET 3.5 and internal testing indicates that .net framework 3.5 still gets installed using the suite prerequisite feature install.
I have seen times in the past where I had similar issues but that was an issue with VMWare Workstation and using NAT instead of Bridged network settings. In all of these cases, as you indicated, running DISM from powershell or a cmd prompt would also fail. Switching to Bridged allowed this to work. I cannot explain why.
Unfortunately we are dependent on .Net 3.5 due to 3rd party software dependencies, one of which is SQL Server 2012 believe it or not!