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

dll's in wrong folder after installation #595

Closed
ghost opened this issue May 17, 2012 · 8 comments
Closed

dll's in wrong folder after installation #595

ghost opened this issue May 17, 2012 · 8 comments

Comments

@ghost
Copy link

ghost commented May 17, 2012

Using the installer for build 216 and 217 I had an error at the end which I've attached to this bug report.

Win32com didn't import properly. The reason for this is that three dll's were in the wrong folder.

* pywintypes26
* pythoncomloader26
* pythoncom26

They needed to be moved to win32 folder. This problem was reported on stack overflow nearly a year ago and the fix is still the same. http://stackoverflow.com/questions/7238403/import-win32api-error-in-python-2-6

I use Python 2.6 32-bit version on Windows 7 64-bit version.

Reported by: robert-whitley

Original Ticket: pywin32/bugs/595

@ghost
Copy link
Author

ghost commented May 17, 2012

Build 217 error using installer

Original comment by: robert-whitley

@ghost
Copy link
Author

ghost commented May 17, 2012

The install script should copy them there (or to system32) - I expect that error is the problem.

When exactly during the install process does this happen - right at the end? Is this reproducible - ie, can you uninstall then reinstall and see the same issue?

Thanks!

Original comment by: mhammond

@ghost
Copy link
Author

ghost commented May 17, 2012

The problem happens right at the end.

I tried build 217, uninstalled, tried again, uninstalled, tried build 216, uninstalled, tried 217 again. On each of these occasions I had the same error.

Original comment by: robert-whitley

@ghost
Copy link
Author

ghost commented May 17, 2012

What is the most recent thing shown in the main installer window when this happens? There might even be a pywin32_postinstall.log (or something like that :) in your temp directory - could you grab that while the error dialog is up and attach it here? I'm going to need help to work out exactly when and why it happens...

Original comment by: mhammond

@ghost
Copy link
Author

ghost commented May 17, 2012

Install with error - Build 217

Original comment by: robert-whitley

@ghost
Copy link
Author

ghost commented May 17, 2012

I found the log in the temp directory but it was empty so I didn't bother uploading it.

I have uploaded what the installer looks like when it errors.

Original comment by: robert-whitley

@ghost
Copy link
Author

ghost commented Jul 5, 2012

The postinstall log file contains the following, which is the same as the error message in the dialog:

Traceback (most recent call last):
File "<string>", line 612, in <module>
File "<string>", line 322, in install
File "<string>", line 160, in LoadSystemModule
File "C:\Python33\lib\imp.py", line 181, in load_module
raise ImportError(msg, name=name)
ImportError: Don't know how to import pywintypes (type code 3

And is the same as the topic of errors towards the end of installation. - ID: 3530195

However, manually copying the .dll files from pywin32_system32 to win32 doesn't help. Neither does moving them.

Original comment by: guruglenn

@ghost ghost assigned ghost and unassigned ghost Oct 24, 2017
@Avasam
Copy link
Collaborator

Avasam commented Mar 14, 2024

.exe/binary installers are now deprecated #1939 and wheels for all bitness are available on PyPI

@Avasam Avasam closed this as completed Mar 14, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant