[tahoe-dev] Windows 7 build error - Python.File class does not exist in the registry - WindowsError(5, 'Access is denied')

[David-Sarah Hopwood]

On 2011-02-22 12:42, Jim Dorrington wrote:
> Hi I have been unable to install Tahoe-LAFS on my Windows system (Windows 7
> ultimate 64-bit)

Thanks for the helpful error report.

We have a couple of build machines running Windows 7 64-bit, but this is
probably a less well-tested Windows version.

> Below is a log
> Can anyone suggest where I'm going wrong?

You're not going wrong; this looks like a platform incompatibility.

It seems like you're using Python 2.6, but please give the more detailed
version string that is printed as the first line from an interactive
Python interpreter. (That is, just 'python', not 'python --version'.)

Just to rule some things out:
 - Was Python installed by the usual "Windows X86-64 MSI Installer" from
   python.org?
 - Have you done anything to change any registry entries associated with
   Python?
 - Are you running this in a user account that has had its registry
   permissions restricted more than the default for a normal user account
   on Win7 ultimate 64-bit?

> M:\Tahoe-LAFS>c:\python26\python setup.py build
...
> Setting up environment to run scripts for the current user...
> error: Setup script exited with error: I was going to associate the filetype
> .pyscript with Python.File for the current user, but th
> at won't work because the Python.File class does not exist in the registry,
> as far as I can tell.
> WindowsError(5, 'Access is denied')

This means that the setup process wasn't able to read the registry entry that
is usually added by a Python installation to point to the Python interpreter.

Specifically, the Python equivalent of the following Windows API call failed:

  RegOpenKeyExW(HKEY_CLASSES_ROOT, L"Python.File", 0, KEY_QUERY_VALUE,
                &outKey)

probably because either the HKEY_CLASSES_ROOT\Python.File entry doesn't exist
(in the setup process' possibly-virtualized view of the registry), or the
setup process' didn't have permission to read it.

Unfortunately "access denied" is sometimes used as a catchall error code to
report other kinds of problem, so we can't be absolutely sure that the
problem is the existence or permissions of that entry.

Please open 'regedit', and search using Ctrl-F for 'Python.File'. If it is
found, give the full registry path of each instance (in the status line at
the bottom of the regedit window).

-- 
David-Sarah Hopwood  ⚥  http://davidsarah.livejournal.com

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 292 bytes
Desc: OpenPGP digital signature
URL: <http://tahoe-lafs.org/pipermail/tahoe-dev/attachments/20110224/7a1968ce/attachment.pgp>