All geek questions in one place

MSMQ does not call COM

I created a COM object with C # and let VS register it for me. I can see this in the registry, and if I create a test application, I can add a link to it, and it works as expected with all available and functional methods.

Now, if I try to use it in an MSMQ rule, nothing happens. He will not be called. Is it because it is a .NET assembly? Is it because I don't have VS Pro? Do you have any idea?

+1
source share
3 answers

Have you accidentally registered your component on a mapped network drive? MSMQ runs on another WinStation for interactive WinStation. Network drives that are displayed in the interactive WinStation are not displayed in other WinStations, which may lead to the symptom you described (component not found).

+1
source

You need to check the system event log for error messages (eventvwr.exe). If your component is registered and MSMQ is configured correctly to activate your component, but it does not work, most likely the problem is related to permissions. The event log should contain information about the span.

0
source

!!!

. EXE . 2 .

, , . COM- . .

I thought that passing parameters to my COM object is just fine, but maybe not. Maybe I'm doing something wrong. I will create COM without parameters and see if I can force COM to call.

If anyone as an example of creating objects for accepting parameters, please let me know.

0
source

Source: https://habr.com/ru/post/1719322/

More articles:


All Articles