title: Why does this pyd file not import on some computers?
body: <p>My python project has a C++ component which is compiled and distributed as a .pyd file inside a Python egg. I've noticed that it seems to be incompatible with only some of our our brand new 64 bit Windows servers. We have 4 (allegedly) identically provisioned machines - each of them runs Windows 2003 server 64 bit edition, but 2 of these machines do not allow me to call functions in the egg.</p>
  
  <p>After some experimentation I was able to find a recipe for <a href="http://pastebin.com/m6d6aef7e" rel="noreferrer">producing a reproducible error</a>. The problem seems to occur when Python tries to import the pyd file.</p>
  
  <p>I copied the pyd to a temp folder and ran Python.exe from that location, incidentally we are still using the 32bit edition of Python 2.4.4 since none of our libraries have been ported to 64 bit architecture yet. Next I try to import my module (called pyccalyon). The first time I try this I get an error message: </p>
  
  <pre><code>"ImportError: DLL load failed: The specified module could not be found"
  </code></pre>
  
  <p>Next time I try this the python interpreter crashes out: no stacktrace at all! </p>
  
  <p>Naturally you are suspecting my PYD - the odd thing about this is that it's already in use on thousands of PCs and 10s of other servers, many of which are identical spec'd 64 bit machines. The project is continuously tested both in development and after release, so if this thing were so tinder-box unstable we'd have known about it a very long time ago. This component is considered to be stable code so it's surprising that it's breaking so spectacularly. </p>
  
  <p>Any suggestions to what I can do to debug this troublesome library? Crazy ideas welcome at this point because we've exhausted all the sensible ones.</p>
  
  <p>Thanks!</p>
  
  <p><strong>Update 0</strong>: Okay using Process monitor I was able to compare one 64bit server that fails with another that works just fine. I found that the breakage seems to occur due to a missing DLL, SysWOW64/mscoreee.dll - any idea what this component is and where I can get it? I can refer this back to our IT provisioning people who can install stuff.</p>