This implies Windows found the .pyd, but failed to locate a DLL this
.pyd depends on. It seems possible you are failing to load the MS CRT,
but you may like to run the 'depends' tool over that .pyd to check if
any other DLLs are referenced which don't exist, or to try and get some
clue why they can't be found when loaded by the user running IIS (eg, if
you rely on a PATH being setup for your current user, that will probably
fail when executed by IIS)
Cheers,
Mark
--
You received this message because you are subscribed to the Google Groups "isapi_wsgi-dev" group.
To post to this group, send email to isapi_w...@googlegroups.com.
To unsubscribe from this group, send email to isapi_wsgi-de...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/isapi_wsgi-dev?hl=en.
I can imagine this would be the case if the CRT DLLs were installed in
the Python directory; that relies on the fact python.exe is the 'host'
executable, which clearly is not true in an IIS environment. I'd
*expect* things to work better if you used the stand-alone "vs 2008
redistributables" installer, which should in theory install them
globally where they will be found regardless of configuration. Sadly, I
can't recall how Python 2.6 installs these DLLs...
Cheers,
Mark
I can imagine this would be the case if the CRT DLLs were installed in the Python directory; that relies on the fact python.exe is the 'host' executable, which clearly is not true in an IIS environment. I'd *expect* things to work better if you used the stand-alone "vs 2008 redistributables" installer, which should in theory install them globally where they will be found regardless of configuration. Sadly, I can't recall how Python 2.6 installs these DLLs...
Right - this is probably another example of
http://bugs.python.org/issue7833.
*sob* :)
Mark
Thanks, I had no idea that was what the error message meant.
I ran depends.exe against osutil.pyd and found three unresolved dependencies:
msvcr90.dll
gpsvc.dll
ieshims.dll
The last two are set up by IIS, so you're right - it is the MS CRT.
I built Mercurial myself (because that's what the instructions in hgwebdir_wsgi.py instructed), using Visual Studio 2008 Express. I looked at osutil.pyd in a binary distribution available from the Mercurial site and it had no problems linking to msvcr90.dll; when I replaced my version with this version, IIS worked just fine.
So, it seems the problem was with the way I built Mercurial (python setup.py install). How can I cause distutils to build the .pyd such that I don't have this dependency problem when running under IIS?
--
Nicholas Riley <njr...@illinois.edu>
So, it seems the problem was with the way I built Mercurial (python setup.py install). How can I cause distutils to build the .pyd such that I don't have this dependency problem when running under IIS?