[pywin32-bugs] [ pywin32-Bugs-3472307 ] 64-bit installation fails when using custom folder

[SourceForge.net <no...@so...>]

Bugs item #3472307, was opened at 2012-01-11 00:51
Message generated for change (Comment added) made by ghostd0g
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=551954&aid=3472307&group_id=78018

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: installation
Group: None
Status: Open
Resolution: Works For Me
Priority: 5
Private: No
Submitted By: craigjh (craigjh)
Assigned to: Nobody/Anonymous (nobody)
Summary: 64-bit installation fails when using custom folder

Initial Comment:
(Note:  I am new to Python but an experienced IT guy).  I installed Python 3.2.2 to C:\Program Files\Python32 instead of the default location of C:\Python32.  No apparent problems with the Python installation.  I then tried to install pywin32-216.  The installation program crashes hard every time.  I uninstalled Python and then re-installed in the default location.  pywin32-216 installed without a problem.  Thought I'd report this in case I'm not the only one experiencing a problem.

Just in case it matters, this is on a Windows PC running Windows 7 Professional with all updates.  The hardware is an i7-2600K CPU, ASUS P67 motherboard, 16 Gb of RAM, & 2x2Gb drives with lots of free space.

----------------------------------------------------------------------

Comment By: ghostd0g (ghostd0g)
Date: 2012-02-08 06:15

Message:
the same happened to me (win7 sp1 x64 spanish, python 2.72 already
installed in non-default folder). running the installer as admin did not
work. but i found out that the permissions on my python folder were
apparently restricted. so i installed python again (this time for all
users) and it worked.

----------------------------------------------------------------------

Comment By: Mark Hammond (mhammond)
Date: 2012-02-03 21:20

Message:
To be clear, the problem shouldn't be caused by running the installer
without elevated permissions as the installer will attempt to elevate.  The
problem is likely to be caused by a completely different user account. 
IOW, it should happen when the elevated user can't write to the directory.

----------------------------------------------------------------------

Comment By: craigjh (craigjh)
Date: 2012-02-03 19:42

Message:
That could indeed be the problem.  My account has administrator privileges
but installs often need to be run as administrator, which I didn't do.

I am in the midst of a busy week but next week I'll have more time and will
see if this is the problem.

----------------------------------------------------------------------

Comment By: Mark Hammond (mhammond)
Date: 2012-02-03 19:35

Message:
This sounds alot like http://bugs.python.org/issue13038 - if the target
directory isn't writable you get that crash.  Is it possible the user
trying to install pywin32 doesn't have permission to write to program
files?

----------------------------------------------------------------------

Comment By: Mark Hammond (mhammond)
Date: 2012-01-28 20:23

Message:
I can't reproduce the hard-crash (and the 'Exception AttributeError:
"'NoneType' object has no attribute 'flush'"' error has already been
fixed).  I should have build 217 available any day now so if it can be
reproduced with that, please reopen this bug.

----------------------------------------------------------------------

Comment By: Mark Hammond (mhammond)
Date: 2012-01-11 16:27

Message:
hmm - that exception code 0xc0000417 = STATUS_INVALID_CRUNTIME_PARAMETER. 
I'll try and reproduce this when I get back from vacation (ie, next week)

----------------------------------------------------------------------

Comment By: craigjh (craigjh)
Date: 2012-01-11 16:13

Message:
Thanks for pointing out where the error log is.  I'm assuming that the
contents were written during the failed installation, not the subsequent
re-installation.  The log has the following:
   Traceback (most recent call last):
     File "<string>", line 604, in <module>
     File "<string>", line 332, in install
     File "<string>", line 15, in write
   AttributeError: 'NoneType' object has no attribute 'write'
   Exception AttributeError: "'NoneType' object has no attribute 'flush'"
in    <__main__.Tee object at 0x00000000040297B8> ignored

What I observed was that the installation program failed immediately after
starting it.  No user interface was displayed and I saw no error messages. 
Windows displayed a dialog box that the program was terminated.  The
WIndows Application Event Log has the following information:

Faulting application name: pywin32-216.win-amd64-py3.2.exe, version:
0.0.0.0, time stamp: 0x4981a90a
Faulting module name: pywin32-216.win-amd64-py3.2.exe, version: 0.0.0.0,
time stamp: 0x4981a90a
Exception code: 0xc0000417
Fault offset: 0x000000000000e668
Faulting process id: 0x35b4
Faulting application start time: 0x01ccd03843d887a5
Faulting application path:
Z:\Downloads\Python\pywin32-216.win-amd64-py3.2.exe
Faulting module path: Z:\Downloads\Python\pywin32-216.win-amd64-py3.2.exe
Report Id: 8d890608-3c2b-11e1-b689-00268313e1f6


----------------------------------------------------------------------

Comment By: Mark Hammond (mhammond)
Date: 2012-01-11 15:38

Message:
What do you mean "crashes hard"?  Failure should write a
pywin32_postinstall.log to your temp directory if it is just a Python
exception...

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=551954&aid=3472307&group_id=78018