Hi there,
I have written a COM enabled .Net 2 .dll that I want to fire
from an MSMQ Trigger. I developed the solution on XP where it all works
well. However, when I tried to deploy it on a customer site, it does not
work. From what I can gather, it is something to do with security settings
on 2003 server. If I give the NETWORK_SERVICE user full access to the
directory where the .dll is installed, I then get a message in the Event Log
from MSMQ, "The COM object may not be registered, or the executable may not
exist in your path." I know it is registered, so that is a red herring.
Without that access, I don't even get an error message, the trigger simply
does not fire. If I give the group everyone aceess from the root of C
down, and the registry roots and DCOM default permissions, will this be
enough to get round the security? What else would I need access to?
Thanks.
Posted by Waldy on December 11, 2007, 6:37 am
Please log in for more thread options
That message was a red herring. If you receive "The COM object may not be
registered, or the executable may not
XML Sitemap