Calling a COM call back object's method fails if it is in Windows 98 
Author Message
 Calling a COM call back object's method fails if it is in Windows 98

We have a method in a COM+ component that, as a parameter, takes a pointer

to a COM component interface on the client machine. The server then calls

methods in the client-side component.

We have set the security settings in the client, and it works perfectly

under Window 2000. The problem is that one of our developers just tried it

from his Win98 machine and when it tries to call back into the client, we

get the following HRESULT error:

0x800706BB: The RPC server is too busy to complete this operation.

Any ideas on the cause?

What is basically happening on the client side is that it is creating an

instance of yet another COM object on the client machine, and returning the

interface pointer back to the COM+ object.

Thanks for any ideas that you guys may have.

Tue, 09 Dec 2003 21:51:52 GMT  
 [ 1 post ] 

 Relevant Pages 

1. Using a COM object in .NET that calls back to the invoking .NET class

2. Calling methods through a late-bound COM object in C#

3. Fail to call COM objects into C# web applications

4. Exception in the call of the COM-object method

5. Dynamic Method call ( Invoke method ) failing in service when compiled as ReleaseMinDependancy

6. Q: (DCOM) Can instantiate objects but can't call methods

7. Calling Windows COM object from C on Unix?

8. 15th Testing Computer Software '98 Conference -- Call for Papers

9. Enable COM clients call methods inside COM events

10. COM client crashes calling COM method

11. stdout from a system() call back into calling program

12. Call Back Functions call from within a DLL


Powered by phpBB® Forum Software