We have numerous COM components that we typically expose through component
services "Activation > uses SOAP" mechanism.  This has been working great on
several servers in the past (w2k3).  However, the last four servers we have
deployed for our clients - we are having problems...

An application we deploy in component services contains about a dozen dlls.
It seems that only ones NOT written in VB manage to get their proxy stub
created and are subsequently exposed through web-services (via entries in
the disco and config files).

I have painstakingly checked everything I can think of, and on the servers
where it works and the servers where it doesn't - there is no difference in
the binaries or the component services settings.

As I mentioned, strangely - COM+ dlls written in Delphi work on all
servers....

Any ideas?

Can I give you more information?

using unmanaged dlls from managed dll wrappers.
MSDN Using Asynchronous Server Socket ?
Visual Studio 2005 and framework 1.1
Generate key file in code
Web Service Deployment Issues