DLL load failed: specified module could not be found

[Tim Valenta]

I was doing some reading on this problem, since I've been having the exact behavior as described in the archives:

http://www.mail-archive.com/mod...@googlegroups.com/msg01234.html

Was there ever a decent solution, aside from compiling it myself as the thread later described?  If not, I'm quick to ditch windows and just put this witchcraft on my linux box.  Just curious though.  I know there's been some work going into new releases of mod_wsgi, 2.x and 3, so I'm not sure where it stands.  The thread I've referenced was taking place in January, and now we're almost out of April.

Thanks,

Tim

[Graham Dumpleton]

2009/4/28 Tim Valenta <tonights...@gmail.com>:

The solution that seems to work for:

> [Sun Jan 25 18:17:03 2009] [error] [client 127.0.0.1] import
> _socket
> [Sun Jan 25 18:17:03 2009] [error] [client 127.0.0.1] ImportError: DLL
> load failed: The specified module could not be found.

is to reinstall your Python installation. You must do it as an account
that has Administrator privileges and when asked whether to install it
for all users you must say yes. This was possibly not done this way
when first done.

Try that first.

Please state exactly which version of Python (including patch level)
you had installed previously and what version you reinstalled it with.

Graham

[Tim Valenta]

Thanks for the reply.  I was the one handling the Python installation, as I'm just dealing with my local home machine.  I'm the only user account, therefore the admin.  I'm not sure about the "for all users" thing.  I'll have to check on that.

Python version is 2.6.1 (should have said that before). I don't follow your comment about the version I "had installed previous and what version [I] reinstalled it with".  I've only got one installation of Python, being the aforementioned.

I will verify this evening that I've done those things.

Tim

[Graham Dumpleton]

2009/4/29 Tim Valenta <tonights...@gmail.com>:

> Thanks for the reply.  I was the one handling the Python installation, as
> I'm just dealing with my local home machine.  I'm the only user account,
> therefore the admin.  I'm not sure about the "for all users" thing.  I'll
> have to check on that.
> Python version is 2.6.1 (should have said that before). I don't follow your
> comment about the version I "had installed previous and what version [I]
> reinstalled it with".  I've only got one installation of Python, being the
> aforementioned.

If you reinstall Python but this time use later 2.6.2, because it is
only a patch revision, it will install over the top of your existing
Python 2.6 installation. So, in terms of differences in versions, was
referring more to patch revision level.

Reinstalling has worked before. In one of those cases 2.6.2 was
installed over the top of 2.6.1. It is not known 100% whether using
2.6.2 is fixing it or whether it is just the reinstall, as think
others reinstalled the same version, ie., 2.6.1.

Graham