On 2/12/2014 2:42 PM, Bob Hanson wrote:
[32-bit Windows XP-SP2]
On Tue, 11 Feb 2014 12:11:49 -0500, Terry Reedy wrote:
[problems installing rc1]
On 2/11/2014 10:42 AM, Duncan Booth wrote:
Does it put any useful messages in logfile.txt?
'error' occurs on 40. most are like the following
MSI (s) (40:08) [11:57:25:973]: Package to be registered:
'python-3.4.0rc1.amd64.msi'
MSI (s) (40:08) [11:57:25:973]: Note: 1: 2262 2: Error 3: -2147287038
MSI (s) (40:08) [11:57:25:973]: Note: 1: 2262 2: AdminProperties 3:
-2147287038
Here is the one for the boxed message:
Action 11:57:26: RemovePip.
Action start 11:57:26: RemovePip.
MSI (s) (40:0C) [11:57:26:426]: Note: 1: 1721 2: RemovePip 3:
C:\Programs\Python34\python.exe 4: -m ensurepip._uninstall
MSI (s) (40:0C) [11:57:26:426]: Note: 1: 2262 2: Error 3: -2147287038
Error 1721. There is a problem with this Windows Installer package. A
program required for this install to complete could not be run. Contact
your support personnel or package vendor. Action: RemovePip, location:
C:\Programs\Python34\python.exe, command: -m ensurepip._uninstall
MSI (s) (40:0C) [11:57:28:874]: Note: 1: 2262 2: Error 3: -2147287038
MSI (s) (40:0C) [11:57:28:874]: Product: Python 3.4.0b2 (64-bit) --
Error 1721. There is a problem with this Windows Installer package. A
program required for this install to complete could not be run. Contact
your support personnel or package vendor. Action: RemovePip, location:
C:\Programs\Python34\python.exe, command: -m ensurepip._uninstall
MSI (c) (98:EC) [11:57:30:204]: PROPERTY CHANGE: Deleting SECONDSEQUENCE
property. Its current value is '1'.
Action ended 11:57:30: ExecuteAction. Return value 3.
MSI (c) (98:EC) [11:57:30:204]: Doing action: FatalError
A
Can you make anything of these?
Interesting. I just had problems trying to install the 32-bit rc1
(see thread in py-dev; I think it's now "solved").
Here's what Windows Event Viewer said:
'''
Product: Python 3.4.0b3 -- Error 1721. There is a problem with
this Windows Installer package. A program required for this
install to complete could not be run. Contact your support
personnel or package vendor. Action: RemovePip, location:
C:\Python34\python.exe, command: -m ensurepip._uninstall
'''
Not sure why the installers are complaining about 3.4.0b3...?
Pip seems to be figuring into these glitches, somehow...?
(Note that both Terry and I are longtime Windows users, so likely
we're both using our own procedures which *have* worked for
years.)
In my case, the problem appears to be that 3.4.0b3 did not completely
uninstall and overwrite .0b2. Control Panel / Programs and Features
(new name for Add/Remove) had entries for both .0b2 and .0b3, which it
should not have. Trying to uninstall .0b2 gave same message. So I
re-downloaded the .0b2 file from python.org/ftp/python/3.4.0, repaired
.0b2, and then uninstalled it. The 64 bit .0c1 then seems to have
installed Ok.
--
Terry Jan Reedy
--
https://mail.python.org/mailman/listinfo/python-list
