[python-win32] python-win32 Digest, Vol 140, Issue 1

[Blair Hall]

I am still stuck on this problem.

I have posted a more detailed account here

http://stackoverflow.com/questions/29597999/incorrect-dll-is-loaded-from-windows-path-instead-of-manifest

_ctypes.pyd calls LoadLibraryA("msvcr90.dll") and a version of msvcr90.dll
is found in the Windows PATH, despite the fact that I have included the
correct version and a manifest, as described on the internet in may places.

Is there is something wrong with the way that I have created my DLL?

As far as I can see, the only place that msvcr90.dll is loaded during the
registration process is the one one shown on the link above. If I remove
the path pointing to the wrong DLL, then the LoadLibrary call still seems
to fail, it does not succeed in loading the copy of msvcr.dll that I
supply, but that failure does not cause the registration of my DLL to fail
(indeed, the error dialog that pops up when the wrong msvcr90.dll is loaded
can just be canceled: the COM server then registers and operates
correctly).

This behaviour suggests to me that the manifest I supply when distributing
the DLL is not being used correctly.

Can no one offer any help?

Send python-win32 mailing list submissions to
To subscribe or unsubscribe via the World Wide Web, visit
https://mail.python.org/mailman/listinfo/python-win32
or, via email, send a message with subject or body 'help' to
You can reach the person managing the list at
When replying, please edit your Subject line so it is more specific
than "Re: Contents of python-win32 digest..."
1. Re: Error R6034 when I import uuid (Roger Upole)
----------------------------------------------------------------------
Message: 1
Date: Wed, 5 Nov 2014 15:37:51 -0500
Subject: Re: [python-win32] Error R6034 when I import uuid
Content-Type: text/plain; charset="utf-8"
This appears to be due to way rpcrt4.dll is loaded by ctypes. If a
side-by-side assembly has already loaded a version that?s not
compatible with the activation context of Python itself, ctypes will
attempt to use it anyway.
Roger
I have a small python COM server that worked fine with Excel until I
decided to import the standard Python 'uuid' module.
Now I get the Windows Runtime error R6034 "An application has made an
attempt to load the C runtime library incorrectly"
I there anything that I can do to fix this?
--------------------------------------------------------------------------------
_______________________________________________
python-win32 mailing list
https://mail.python.org/mailman/listinfo/python-win32
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <
http://mail.python.org/pipermail/python-win32/attachments/20141105/9bf7f239/attachment-0001.html
------------------------------
Subject: Digest Footer
_______________________________________________
python-win32 mailing list
https://mail.python.org/mailman/listinfo/python-win32
------------------------------
End of python-win32 Digest, Vol 140, Issue 1
********************************************

[Tim Roberts]

Post by Blair Hall
_ctypes.pyd calls LoadLibraryA("msvcr90.dll") and a version of
msvcr90.dll is found in the Windows PATH, despite the fact that I have
included the correct version and a manifest, as described on the
internet in may places.
Is there is something wrong with the way that I have created my DLL?

I'm surprised at both of these actions. MSVCR90, from Visual Studio
2008, still uses the "side-by-side" loading mechanism. The operating
system is supposed to look in the version-tagged side-by-side
repository, not in the path nor in the local directory.

Can you show us your manifest?