#42 Installation crash in recent win32all's.

closed-works-for-me
nobody
None
5
2012-01-28
2003-08-07
No

The win32all installer has been crashing on me for
the last few win32all releases.

This has happened for Python 2.2.3 with win32all-156
and Python 2.3 with win32all-157. It has also
happened for some previous win32all releases
(such as 153 and 155 with Python 2.3).

The error occurs during the `Completing Installation'
stage, when the message box says
`Registering COM Server AXScript Engine'. The
error message is the usual `This program has performed
an illegal operation and will be shut down' message.
Pressing the `Details' button gives:

WIN32ALL-156 caused an invalid page fault in
module MSVCRT.DLL at 016f:7800b936.
Registers:
EAX=006b61a0 CS=016f EIP=7800b936 EFLGS=00010202
EBX=00000000 SS=0177 ESP=0063cad4 EBP=0063caf0
ECX=00000120 DS=0177 ESI=01ddab0c FS=3fb7
EDX=00000000 ES=0177 EDI=00000013 GS=0000
Bytes at CS:EIP:
89 5a 04 8b 55 0c 89 4d fc 8b 5a 04 8b 52 08 89
Stack dump:
00760840 01ddab10 00000001 006b8930 00000000
000004d0 00000120 0063cb34 7800b30c 0075005c
01ddac2c 00760840 00000000 00000001 bff813f8
81d52568

(This is with Python 2.2.3 and win32all-156.)

This has happened on both WinXP and Win98SE.

Once this happens, the win32all uninstaller doesn't
work (says `can't find install.log').

If Python is installed with the `Non-Admin' option,
then win32all installs fine (presumably because it
never reaches the `Registering COM Server AXScript
Engine' stage).

I haven't seen anyone else report this, so looks like
I'm the only one. Any help is greatly appreciated.

Discussion

  • Mark Hammond

    Mark Hammond - 2003-08-08

    Logged In: YES
    user_id=14198

    Can you please see if running
    "win32comext\axscript\client\pyscript.py" also crashes for you?

    An admin install should still actually work fine - just
    can't be uninstalled, and a couple of demo COM objects won't
    be installed.

     
  • John J Smith

    John J Smith - 2003-08-08
    • status: open --> open-works-for-me
     
  • John J Smith

    John J Smith - 2003-08-08

    Logged In: YES
    user_id=830565

    I assume you mean run it after the failed installation.
    I tried it on Python 2.3, win32all-157, Win98SE, and it
    worked:

    Registered: Python
    Registration of Python ActiveX Scripting Engine complete.

    And yes, an admin install even after crashing does work,
    and I've been using it. However it would be nice to have
    a clean install (especially for eventual un-installation and
    upgradation).

     
  • John J Smith

    John J Smith - 2003-08-08

    Logged In: YES
    user_id=830565

    Okay, here is some more info.

    This sequence on a newly installed Win98SE works:

    Install Python 2.2.3
    Install win32all-152

    This sequence on a newly installed Win98SE crashes:

    Install Python 2.2.3
    Install win32all-154

    This sequence on a newly installed Win98SE *works*:

    Install Python 2.2.3
    Install win32all-152
    Uninstall win32all-152
    Install win32all-154

    And, finally, this also works on a fresh Win98SE:

    Install Python 2.2.3
    Install win32all-152
    Uninstall win32all-152
    Install win32all-154
    Uninstall win32all-154
    Uninstall Python 2.2.3
    Install Python 2.3
    Install win32all-157

    The installer crash has happened for me on at least 5 PCs
    with very different configurations (spanning Win98SE,
    Win2K, WinXP, Athlon, P3, P4, and different peripherals
    and drivers). In each case, Python and win32all were
    being installed for the first time on the PC.

    My guess is that most people are upgrading from cleanly
    installed versions of win32all, and are therefore not
    seeing the problem.

     
  • Michael Geary

    Michael Geary - 2003-08-11

    Logged In: YES
    user_id=114596

    I see a very similar crash when installing win32all-154 on a
    Python 2.2.2 installation. This is on a clean Windows XP
    virtual machine with nothing but VS.NET 2003 installed.

    If I install Python 2.2.2 on this VM and then install
    win32all-154, it crashes. If I then run the pyscript.py,
    that succeeds.

    After reverting the VM, if I install Python 2.2.2 and then
    install win32all-152, it succeeds. If I then install
    win32all-154 (letting it uninstall 152), this also succeeds.
    So the crash happens only when installing 154 without having
    previously installed 152.

    The crash is an access violation writing to location 0. Here
    is the stack trace (with apologies for its length):

    ntdll.dll!77f57e4f()
    ntdll.dll!77f93a50()
    ntdll.dll!77f93a50()
    ntdll.dll!77f57cf7()
    ntdll.dll!77f588f5()
    ntdll.dll!77f93a73()
    ntdll.dll!77f5be44()
    kernel32.dll!77e78bf1()
    kernel32.dll!77e78c14()
    kernel32.dll!77e78c14()
    msvcrt.dll!77c2ac14()
    msvcrt.dll!77c2ac2a()
    msvcrt.dll!77c2ac55()
    python22.dll!1e04f836()
    python22.dll!1e052b2d()
    python22.dll!1e052963()
    python22.dll!1e05306b()
    python22.dll!1e052ef3()
    python22.dll!1e05e84b()
    python22.dll!1e05e886()
    python22.dll!1e040f66()
    python22.dll!1e040d92()
    ntdll.dll!77f58ec1()
    msvcrt.dll!77c2ab2e()
    msvcrt.dll!77c2ab33()
    msvcrt.dll!77c2ab33()
    python22.dll!1e040ab3()
    python22.dll!1e04025b()
    ntdll.dll!77f588f5()
    python22.dll!1e03afdb()
    ntdll.dll!77f58ec1()
    msvcrt.dll!77c2ab2e()
    msvcrt.dll!77c2ab33()
    python22.dll!1e02f9ab()
    msvcrt.dll!77c2ab33()
    python22.dll!1e04f9eb()
    python22.dll!1e03fe16()
    python22.dll!1e03fe4c()
    python22.dll!1e03fac6()
    ntdll.dll!77f93a73()
    ntdll.dll!77f58a7e()
    ntdll.dll!77f58ec1()
    python22.dll!1e016137()
    python22.dll!1e015e89()
    python22.dll!1e03a90f()
    python22.dll!1e03f98f()
    python22.dll!1e00d2f8()
    python22.dll!1e04d469()
    python22.dll!1e006ccc()
    python22.dll!1e014977()
    python22.dll!1e012879()
    python22.dll!1e01376f()
    python22.dll!1e013e2f()
    python22.dll!1e0109f2()
    python22.dll!1e03f701()
    python22.dll!1e040ddc()
    python22.dll!1e02fc88()
    python22.dll!1e02fc88()
    python22.dll!1e051151()
    python22.dll!1e050dcb()
    python22.dll!1e040ab3()
    python22.dll!1e04025b()
    python22.dll!1e03afdb()
    python22.dll!1e03ac39()
    ntdll.dll!77f8d98c()
    msvcrt.dll!77c2af77()
    ntdll.dll!77f83367()
    python22.dll!1e03fe16()
    python22.dll!1e03fb04()
    user32.dll!77d48fb4()
    ntdll.dll!77f93a73()
    ntdll.dll!77f58a7e()
    ntdll.dll!77f58ec1()
    python22.dll!1e04d469()
    python22.dll!1e072ae1()
    python22.dll!1e072b09()
    python22.dll!1e072d2b()
    python22.dll!1e01349d()
    python22.dll!1e072ac9()
    python22.dll!1e072b09()
    python22.dll!1e072d2b()
    python22.dll!1e03f98f()
    python22.dll!1e00d2f8()
    python22.dll!1e04d469()
    python22.dll!1e012c54()
    python22.dll!1e01376f()
    python22.dll!1e013e2f()
    python22.dll!1e039390()
    python22.dll!1e006ccc()
    python22.dll!1e014977()
    python22.dll!1e00d427()
    python22.dll!1e04d469()
    python22.dll!1e012c54()
    python22.dll!1e01376f()
    python22.dll!1e013e2f()
    python22.dll!1e039390()
    python22.dll!1e006ccc()
    python22.dll!1e014977()
    python22.dll!1e00d427()
    python22.dll!1e04d469()
    python22.dll!1e012c54()
    python22.dll!1e01376f()
    python22.dll!1e013e2f()
    python22.dll!1e014c14()
    python22.dll!1e012d1a()
    python22.dll!1e01376f()
    python22.dll!1e013e2f()
    python22.dll!1e039390()
    python22.dll!1e006ccc()
    python22.dll!1e014977()
    python22.dll!1e006ca1()
    PyWise22.dll!00a91bd8()

    -Mike

     
  • John J Smith

    John J Smith - 2003-09-13

    Logged In: YES
    user_id=830565

    This seems to be related to bug #799063 (Registering Python
    COM Server component category crashes).

     
  • Andy Lange

    Andy Lange - 2003-10-10

    Logged In: YES
    user_id=884085

    I have seen this also - trying to install win32all-157 over
    python 2.3.2 would consistently hang my machine (win XP Pro)
    at the registration point. Sometimes it would leave the
    "Registering COM Server AXScript Engine" message up,
    sometimes it would clear that progress box and then hang.
    (All installs attempted with normal Admin option).

    Every time I finished rebooting, there would be nothing to
    install via the Windows add/remove programs control panel.
    Attempting to check the version of PythonCOM23.dll with the
    Windows properties function showed no "version" tab,
    although PyWinTypes23.dll appeared to be fine.

    I then tried the newer win32all-159, which didn't hang, but
    did give me the following error: "Registration of the
    AXScript Engine COM Server Failed. Install will
    continue....manual registration required", then
    "Exceptions.EOFError:" (nothing after the EOFError:). The
    windows uninstaller can't remove it because it can't find
    INSTALL.LOG.

    Putting the older win32all-153 on top mostly worked, except
    for problems reported with the version mismatch on
    PyWinTypes23.dll. 153 seems to have uninstalled (According
    to windows) but the dll verisons are still reported as -153,
    and the 159 version is apparently still there and still not
    removable via add/remove. I will try reinstalling (now that
    an earlier version was installed/removed) and will post
    results here.

     
  • Andy Lange

    Andy Lange - 2003-10-10

    Logged In: YES
    user_id=884085

    Well, installing and removing win32all-153 and then
    installing -157 let -157 install without any errors
    reported, so it appears that something is changed (and left
    changed) by the earlier installers that is required for more
    recent installers to work. I really don't know enough about
    what it is doing to figure out exactly what that something
    is, though.

     
  • Eric Promislow

    Eric Promislow - 2004-01-15

    Logged In: YES
    user_id=63713

    I ran into this problem as well, with version 2.3.3
    from Python.org, and win32all 163.

    This happened on both Windows Server 2003 (with
    .Net 1.0 installed), and Win2K (no .Net installed).
    I didn't try further systems.

    The event log says the crash is due to an access
    violation in RtlDestroyHeap()

     
  • Mark Hammond

    Mark Hammond - 2012-01-28
    • status: open-works-for-me --> closed-works-for-me
     

Get latest updates about Open Source Projects, Conferences and News.

Sign up for the SourceForge newsletter:





No, thanks