Skip to content
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

Install failure of 2.6a1 on Windows XP without VS8 installed #46509

Closed
jkleckner mannequin opened this issue Mar 7, 2008 · 8 comments
Closed

Install failure of 2.6a1 on Windows XP without VS8 installed #46509

jkleckner mannequin opened this issue Mar 7, 2008 · 8 comments
Labels
topic-installation type-bug An unexpected behavior, bug, or error

Comments

@jkleckner
Copy link
Mannequin

jkleckner mannequin commented Mar 7, 2008

BPO 2256
Nosy @loewis, @tiran
Files
  • debuglog.txt.zip: Zip compressed debug log file
  • Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.

    Show more details

    GitHub fields:

    assignee = None
    closed_at = <Date 2008-04-10.22:00:45.413>
    created_at = <Date 2008-03-07.23:33:46.121>
    labels = ['type-bug', 'expert-installation']
    title = 'Install failure of 2.6a1 on Windows XP without VS8 installed'
    updated_at = <Date 2008-04-10.22:00:45.412>
    user = 'https://bugs.python.org/jkleckner'

    bugs.python.org fields:

    activity = <Date 2008-04-10.22:00:45.412>
    actor = 'loewis'
    assignee = 'none'
    closed = True
    closed_date = <Date 2008-04-10.22:00:45.413>
    closer = 'loewis'
    components = ['Installation']
    creation = <Date 2008-03-07.23:33:46.121>
    creator = 'jkleckner'
    dependencies = []
    files = ['9634']
    hgrepos = []
    issue_num = 2256
    keywords = []
    message_count = 8.0
    messages = ['63371', '63383', '63406', '64256', '65275', '65277', '65287', '65324']
    nosy_count = 4.0
    nosy_names = ['loewis', 'christian.heimes', 'michaelurman', 'jkleckner']
    pr_nums = []
    priority = 'critical'
    resolution = 'fixed'
    stage = None
    status = 'closed'
    superseder = None
    type = 'behavior'
    url = 'https://bugs.python.org/issue2256'
    versions = ['Python 2.6']

    @jkleckner
    Copy link
    Mannequin Author

    jkleckner mannequin commented Mar 7, 2008

    When I install 2.6a1 onto a Windoze machine I get a dialog:
    There is a problem with this Windows Installer package.
    A program run as part of the setup did not finish as expected.
    Contact your support personnel or package vendor.

    Note that it didn't have VS2008 or any other new code installed.
    The problem appears related to Tkinter but that isn't clear.

    When running the Python console, running
    import Tkinter

    results in an error saying that _tkinter can't be loaded.
    DLL load failed. The system can't find _tkinter.pyd

    _tkinter.pyd and tcl84.dll and tk84.dll are in DLLs and
    appear to have reasonable permissions.

    I suspect something in the install failed to set something
    in the registry.

    This is on a current-patch XP
    system and that I also tried python-2.6.13944.msi
    from the buildbot just in case after uninstalling/reinstalling
    with no difference.

    Attached is a compressed log of the install.

    Perhaps this "PROPERTY CHANGE: Deleting SECONDSEQUENCE"
    is the problem?

    Here is an excerpt from the log file:

    Property(S): Privileged = 1
    Property(S): DATABASE = C:\WINDOWS\Installer\5f5ad0.msi
    Property(S): OriginalDatabase = C:\cygwin\tmp\python-2.6a1.msi
    Property(S): UILevel = 5
    Property(S): Preselected = 1
    Property(S): CostingComplete = 1
    Property(S): OutOfDiskSpace = 0
    Property(S): OutOfNoRbDiskSpace = 0
    Property(S): PrimaryVolumeSpaceAvailable = 0
    Property(S): PrimaryVolumeSpaceRequired = 0
    Property(S): PrimaryVolumeSpaceRemaining = 0
    Property(S): SOURCEDIR = C:\cygwin\tmp\
    Property(S): SourcedirProduct = {0BA82E1B-52FD-4E03-8610-A6C76238E8A8}
    Property(S): ProductToBeRegistered = 1
    MSI (s) (FC:D0) [16:38:30:939]: MainEngineThread is returning 1603
    MSI (s) (FC:C0) [16:38:30:939]: Destroying RemoteAPI object.
    MSI (s) (FC:54) [16:38:30:939]: Custom Action Manager thread ending.
    MSI (c) (E0:54) [16:38:30:954]: Back from server. Return value: 1603
    MSI (c) (E0:54) [16:38:30:954]: Decrementing counter to disable
    shutdown. If counter >= 0, shutdown will be denied. Counter after
    decrement: -1
    MSI (c) (E0:54) [16:38:30:954]: PROPERTY CHANGE: Deleting SECONDSEQUENCE
    property. Its current value is '1'.
    Action ended 16:38:30: ExecuteAction. Return value 3.
    MSI (c) (E0:54) [16:38:30:954]: Doing action: FatalError
    Action 16:38:30: FatalError.
    Action start 16:38:30: FatalError.
    Action 16:38:30: FatalError. Dialog created
    Action ended 16:38:32: FatalError. Return value 2.
    Action ended 16:38:32: INSTALL. Return value 3.
    MSI (c) (E0:54) [16:38:32:375]: Destroying RemoteAPI object.
    MSI (c) (E0:2C) [16:38:32:375]: Custom Action Manager thread ending.
    Property(C): X = C:\Python26\Tools\pynche\X\
    Property(C): UpgradeCode = {65E6DE48-A358-434D-AA4F-4AF72DB4718F}
    Property(C): ProductName = Python 2.6a1
    Property(C): ProductCode = {0BA82E1B-52FD-4E03-8610-A6C76238E8A8}
    Property(C): ProductVersion = 2.6.101
    Property(C): Manufacturer = Python Software Foundation

    @jkleckner jkleckner mannequin added topic-installation type-bug An unexpected behavior, bug, or error labels Mar 7, 2008
    @michaelurman
    Copy link
    Mannequin

    michaelurman mannequin commented Mar 8, 2008

    The failure is signaled by the return code from the call to compileall.py:
    MSI (s) (FC:D0) [16:38:27:394]: Note: 1: 1722 2: CompilePyc 3:
    C:\Python26\python.exe 4: -Wi "C:\Python26\Lib\compileall.py" -f -x
    bad_coding|badsyntax|site-packages "C:\Python26\Lib"

    The install succeeds anyway because this is after InstallFinalize. That
    makes this a wart that will likely fail similarly on Vista under UAC (if
    not already handled by being conditioned out). This should probably be a
    scheduled between InstallFiles and InstallFinalize with
    inscript+noimpersonate.

    @jkleckner
    Copy link
    Mannequin Author

    jkleckner mannequin commented Mar 8, 2008

    I uninstalled and re-ran the install without the "compile all" selected.

    The install didn't report errors.

    running:
    python -c "import test.testall"
    results in a traceback with the message:
    import _socket
    ImportError: DLL load failed: The system could not find the file
    specified.

    What sorts of things should I probe into?

    @tiran
    Copy link
    Member

    tiran commented Mar 21, 2008

    We are still having trouble with msvcrt90.dll and SxS assemblies (side
    by side assembly dlls). Chris suggested to modify the manifest of the
    Python dlls (pyd) files to look for the private copy of msvcrt90.dll in
    the parent directory ..\.

    @jkleckner
    Copy link
    Mannequin Author

    jkleckner mannequin commented Apr 9, 2008

    Ping.

    @jkleckner
    Copy link
    Mannequin Author

    jkleckner mannequin commented Apr 9, 2008

    It appears that bpo-2563 may be a dependency.

    @loewis
    Copy link
    Mannequin

    loewis mannequin commented Apr 10, 2008

    Ping.

    Does the problem still exist in 2.6a2? It shouldn't.

    @jkleckner
    Copy link
    Mannequin Author

    jkleckner mannequin commented Apr 10, 2008

    I hadn't seen any comment here that I should try it again until your
    question (that was why the ping).

    I did try it again and my application worked.

    Thanks!

    @loewis loewis mannequin closed this as completed Apr 10, 2008
    @ezio-melotti ezio-melotti transferred this issue from another repository Apr 10, 2022
    Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
    Labels
    topic-installation type-bug An unexpected behavior, bug, or error
    Projects
    None yet
    Development

    No branches or pull requests

    1 participant