pywin32 running 32bit windows service on 64bit OS - python-3.x

I am running 32bit python application on old Windows Server 2003 using pywin32 package and it's working fine. Lately I've received new Server with windows Server 2012 64bit OS and I started installing the same application. While it didn't run under 64bit Python 3.4 I've installed 32bit version and it's working fine when I am running it from command line.
The problem starts when I want to run it as windows service. It installs and looks ok but it doesn't start.
I am receiving following error: The service is not responding to the control function.
More help is available by typing NET HELPMSG 2186.
When I check pythonservice.exe it shows me following error:
PythonService was unable to locate the service manager. Please see the event log for details
Is there any way I could run it as it does run under 32bit?
Thanks,
Mike

Related

Reaction Commerce setup on Windows 10 Home

Now its been 2 weeks and i am trying to setup the environment for reaction commerce, but i am failing everytime, i don't want to giveup on it.
I have tried on windows and linux both, following are my points:
Windows --- I have windows 10 home, i tried to install dockers and unfortunately, it is not supporting home version then i tried with virtual box, it also starting giving error.
Ubuntu 16 --- I installed the ubuntu app for windows and then i tried to set up on that, and then failed cause my system was not supporting docker.
Can anyone please help me in the setup of the environment.
Thanks in advance.
I don't know if You fixed the issue as it has been some time. But You have to install WSL2 for docker to run on windows 10 home.

Localhost failing to start after installing mifos

I installed xampp v 3.2.2, jdk 9.0.4. The xampp package has, Mysql 7.2.3. I installed mifos following the installation guide from the mifosforge.jira.com. All the modules in xampp are working fine. I attempted to launch mifos through running tomcat admin in xampp. However on attempting to start mifos, an error occurred. I am using windows 8.1, 64bit.
Can somebody please assist on how i can resolve this problem. i have attached the log file and screenshot of the event.
Screenshot

Installation of Azure Machine Learning Workbench fails on Windows 10

I tried to install the azure machine learning workbench from here. Once I double click on the downloaded MSI file, it shows the first screen about licensing terms. Once I click on Continue, it shows dependencies. When I click Install, it starts installation. It downloads Miniconda with Python 3.5.2. While trying to install asn1crypto 0.23.0, it suddenly stops and displays 'Installation fails'. I tried running the MSI file with log option but no error is reported in the log.
Here are my machine details:
Windows 10
Version 1709 (OS Build 17017.1000)
How can I troubleshoot this?
you can have a look at the installer log (%TEMP%\AmlInstaller\Logs). See if there is any obvious error... What version of windows are you running, is it a preview?

Installation of python 3.6 on windows vista failure

I am unable to complete installation of python on windows vista because the launcher is unable to find the file KB2999226. Windows Vista is no longer supported by Microsoft. Any suggestions?
Manually download the missing file KB2999226 from the following Microsoft link
https://www.microsoft.com/en-us/download/details.aspx?id=49088
Disable the Windows update service
Install the downloaded file
Install Python 3.6
Enable the Windows update service

Installers created using install4j on linux are unable to launch the application in Windows

I have an install4j setup on Linux machine. When I install the application on windows, installation process completes but then the application is not launched.
I have checked installation.log and found that an action is not executed properly and so some variables are not assigned values.
I have the same setup on Windows machine that creates installers for all platforms fine. So there is nothing wrong with the setup I have.
Install4j version I am using is 6.1.5
This happened because of the known bug in install4j version 6.1.5. Working fine for former and later versions.

Resources