C#
An object-oriented and type-safe programming language that has its roots in the C family of languages and includes support for component-oriented programming.
10,292 questions
Getting RPC_E_WRONG_THREAD when calling the call back method on the .Net object from the native C++
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(70.4, 82%, 16%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3E6%3C/text%3E%3C/svg%3E)
62387145
1
Reputation point
Hi,
I am getting below error when I call the call back method on the .Net CLR object interface from a C++ application.
"RPC_E_WRONG_THREAD The application called an interface that was marshalled for a different thread."
I get the .Net object interface as a parameter from a 3rd party .Net component, then I marshal this interface in C++ by calling "CoMarshalInterThreadInterfaceInStream" to use this .Net object in the newly created thread in my C++ application. And in the thread function, I un marshal the .Net object by calling the "CoGetInterfaceAndReleaseStream". Marshaling and Un Marshaling is working fine, but when I call the .Net object interface function from the thread, it return the "RPC_E_WRONG_THREAD" error.
Please let me know how can I fix this issue.
C#
C++
C++
A high-level, general-purpose programming language, created as an extension of the C programming language, that has object-oriented, generic, and functional features in addition to facilities for low-level memory manipulation.
3,540 questions
{count} votes
-
RLWA32 40,756 Reputation points2022-05-20T12:18:01.563+00:00 What happens if you try to call a method on the interface from the first thread that initially receives it?
-
62387145 1 Reputation point
2022-05-20T14:07:41.71+00:00 @RLWA32 : Yea, first thread is working without any issue.
I am getting this issue in the new thread I created, I have Marshaled in the first thread, then I un-marshaled in the new thread, no issues found during the Marsha and Un-Marsha, but when I call the interface method from the new thread, I am getting the "RPC_E_WRONG_THREAD The application called an interface that was marshalled for a different thread." error. -
RLWA32 40,756 Reputation points
2022-05-20T14:18:51.02+00:00 Have you initialized COM on the secondary thread? If yes, what threading model?
What threading model is used by the .Net object?
Try using RoGetAgileReference and IAgileReference to marshal the interface between threads.
-
62387145 1 Reputation point
2022-05-20T15:32:01.87+00:00 @RLWA32 :
Yes, I have initialized the COM on the secondary thread. its an STA threading model. I have other C++ interface, which I am able to Marshal and Un-Marshal, and able to call the method without any issues. Only issue with the .Net object.
I dont know what is the threading model used in the .Net object, its from third party.I tried using RoGetAgileReference and IAgileReference to marshal the interface between threads, but same result.
-
RLWA32 40,756 Reputation points
2022-05-20T15:52:30.31+00:00 Is the thread that first receives the interface also an STA thread? If you're not doing user interface work on these threads try using the MTA for them.
-
-
RLWA32 40,756 Reputation points
2022-05-20T17:13:44.96+00:00 If you're not doing UI work on the secondary thread try putting that one in the MTA.
There isn't much to go on here. Maybe you can get support from the author of the.net object.
-
Sign in to comment