You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
You will encounter a silent failure when attempting to install the service via terminal.
If you inspect windows event viewer you will see a KERNELBASE.dll error at the time of the installation attempt
To Reproduce
Take the cx_Freeze service sample
Remove the cx_Logging include
Build the product
Install the product
Expected behavior
Either:
No error :)
A meaningful error informing the developer that cx_logging is a required option for includes
Desktop:
Platform information: Windows 10
OS architecture (e.g. amd64): amd64
cx_Freeze version [e.g. 6.6]: Reproduced in 6.6-6.8
Python version [e.g. 3.9]: Python 3.9.6
Additional context
Not sure if action is required here, i wanted to file this issue though so either this requirement can be moved internally to cx_freeze - or if no action is required, at least this issue should show up if others encounter + google this issue in future ( took a few hours to track this down! )
The text was updated successfully, but these errors were encountered:
TechnicalPirate
changed the title
Not including cx_Logging module with windows services causes KERNALBASE.dll errors
Not including cx_Logging module with windows services causes KERNELBASE.dll errors
Nov 3, 2021
Describe the bug
Since
cx_freeze-6.6
it appears that if you do not includecx_logging
in your build optionsYou will encounter a silent failure when attempting to install the service via terminal.
If you inspect windows event viewer you will see a
KERNELBASE.dll
error at the time of the installation attemptTo Reproduce
cx_Logging
includeExpected behavior
Either:
cx_logging
is a required option forincludes
Desktop:
Additional context
Not sure if action is required here, i wanted to file this issue though so either this requirement can be moved internally to cx_freeze - or if no action is required, at least this issue should show up if others encounter + google this issue in future ( took a few hours to track this down! )
The text was updated successfully, but these errors were encountered: