#599 errors towards the end of installation.

[Anonymous]

While trying to install pywin32-217.win-amd64-py2.6.exe, I get following errors towards the end of installation.

Traceback (most recent call last):

File "<string>", line 612, in <module>

File "<string>", line 322, in install

File "<string>", line 160, in LoadSystemModule

ImportError: DLL load failed: The specified module could not be found.

[Anonymous]

screenshot

[Glenn Linderman]

I get the same error trying to install pywin32-217.win-amd64-py3.3.exe

[Glenn Linderman]

Just for kicks, I added a print statement in LoadSystemModule in pywin32_postinstall.py, and the module it cannot load, on my system, is

c:\python33\Lib\site-packages\pywin32_system32\pywintypes33.dll

This probably doesn't surprise you since that is what the comments imply... The file exists in that location.

Is there something else I can do to help debug this problem?

[Mark Hammond]

These problems all appear to be specific to 3.3. Sadly pywin32-217 was built with vc2008 where 3.3 recently moved to vs2010. I'm looking into it...

[Mark Hammond]

I put a build up at http://starship.python.net/~skippy/downloads/pywin32-217.1.win-amd64-py3.3.exe - it works for me here, but it would be great if anyone experiencing this problem could test it out. It is being slow to upload, so give it 30 mins after this message was posted - the filesize is 8,441,923.

I'll make a real release soon...

[Glenn Linderman]

Build 217.1 works for me.

[D-Mac]

I get this install error with 217 on both Vista 32 and 64, w/ 32bit Python 2.6 on both. Is there a manual install method? I'd like to use the library very much. Thanks.

[D-Mac]

OK, got ambitious and looked it up myself! ;)

Here's what worked for me for others:

http://forums.arcgis.com/threads/33808-PyWin32-212.win32-py2.6-silent-install

[hasenpfeffer2]

I'll try adding on to this instead of making a new one...

I have gotten the DLL load failed error in all runs of the pywin32 win32 installer I have ever done. This is on many different machines, with different Windows versions. The post install script has never worked within the installer.

I got around the problem by running the post install script manually on the cmd line with the -install parameter. This has always worked.

Then one day I happen to install VS2008 Express Edition to do some development work with Python. Ever since I installed VS2008, the post install script now runs properly at the end of the installer.

I uninstalled VS2008 to see how the installer would react. I now get a sys.excepthook missing and stderr not found error. Though, I suspect, it was trying to print the DLL load failed exception and couldn't. Just speculation, though.

I would recommend someone try using the installer on a system that has never had VS2008 installed and see if the DLL load failed error can be reproduced.

[hasenpfeffer2]

I found some more information about my problems related to post install script failures I was experiencing.

The most interesting is that the installer does not seem to work when the logged-in account is not a local account. I am a member of Administrators on my machine, but my account is a network account, and the post install script always fails at the end of the installer with a sys.stderr not found and such. By creating a local Admin account and using that account to start the installer, then the post install script works. Can a change be made to allow non-local administrator accounts work?

I believe my original problems were not related to installing VS2008 now. I had caused most of my problems by using a custom pythonxx.dll that did not include the correct manifest for VS2008 dlls. Once I started using the shipping pythonxx.dll, then things worked mostly as expected, except for the above non-local admin problem.

Incidentally, I also found that having the pythonxx.dll in the same folder as the pywin32....exe installer caused my administrator problem to go away as well. So, normally I always get the sys.stderr missing failure. If the pythonxx.dll is in the same folder as the installer executable, then the post install script works fine even under a non-local admin account.