This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author eryksun
Recipients Thrameos, WildCard65, eryksun, paul.moore, steve.dower, tim.golden, zach.ware
Date 2020-12-19.06:40:34
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1608360034.67.0.00944560349466.issue42529@roundup.psfhosted.org>
In-reply-to
Content
> ImportError: DLL load failed while importing _jpype: 
> A dynamic link library (DLL) initialization routine failed.

With loader snaps enabled for python[_d].exe (i.e. loader debug messages), you can attach a debugger to discover which DLL's init routine is failing. For example, you'll see a debug message like the following:

    xxxx:xxxx @ xxxxxxxx - LdrpInitializeNode - ERROR:
    Init routine XXXXXXXXXXXXXXXX for DLL "Path\To\DLL"
    failed during DLL_PROCESS_ATTACH

The entry point of a DLL is typically _DllMainCRTStartup, which initializes the CRT for the DLL and calls DllMain(). In any case, you can find the relative address of the entry point in the PE header, via dumpbin.exe or the debugger !dh command. Set a breakpoint on it and step through to find where it fails in comparison with a working environment.
History
Date User Action Args
2020-12-19 06:40:34eryksunsetrecipients: + eryksun, paul.moore, tim.golden, zach.ware, steve.dower, WildCard65, Thrameos
2020-12-19 06:40:34eryksunsetmessageid: <1608360034.67.0.00944560349466.issue42529@roundup.psfhosted.org>
2020-12-19 06:40:34eryksunlinkissue42529 messages
2020-12-19 06:40:34eryksuncreate