-
Notifications
You must be signed in to change notification settings - Fork 92
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Server 2016 NCPA 3.1.2.0 won't start #1242
Comments
This seems to be an issue with the python version upgrade. For now, if you back up your configurations and uninstall NCPA, you should be able to install NCPA cleanly and then replace your configuration files and it will be upgraded. I will try to get a patch out for this ASAP. |
Thanks for looking into this, Will give this a try tomorrow, I temporarily downgraded it, but be good to be on the newer version, |
You can also just delete your python3.dll and python311.dll before running the upgrade. To cleanly remove the old files, you can also remove the lib folder. I haven't done extensive testing on removing the lib, listener and .dll files, but a brief test indicates that it should be fine to remove each of them. |
This will be fixed in 3.1.3, which should release early next week. |
Thank you |
Hi All,
Just upgraded ncpa to 3.1.2.0 on an server 2016 server, which the webpage says is still supported but fails to start with this error.
If you need more information let me know, otherwise will downgrade it for now.
Faulting application name: ncpa.exe, version: 3.1.2.0, time stamp: 0x6778e63b
Faulting module name: python311.DLL, version: 3.11.8150.1013, time stamp: 0x65c2ad06
Exception code: 0xc0000005
Fault offset: 0x000000000009f907
Faulting process id: 0x1d44
Faulting application start time: 0x01db6b2c3c3f7958
Faulting application path: C:\Program Files\Nagios\NCPA\ncpa.exe
Faulting module path: C:\Program Files\Nagios\NCPA\python311.DLL
Report Id: f7394ce6-d328-441c-9513-9d62779c8762
Faulting package full name:
Faulting package-relative application ID:
Kind Regards
The text was updated successfully, but these errors were encountered: