Groups | Blog | Home
all groups > dotnet component services > december 2003 >

dotnet component services : Can't run queued components within 2 hosts


Eric
12/9/2003 4:21:10 AM
Hi Fellows

I'm trying to run a queued component hosting the client in one machine (WinXP professional) and the real component in another one (Windows 2003 standanlone server). However I can't figure out the correct way to install the component to make it work. I already use a com+ proxy application, install the component dll in both hosts, tryied all sort of "queue moniker" to instantiate the component and nothing work
The closest I got to make it work, was a situation where the client does create a DIRECT output queue pointing to the server's queue, however the message is never deliverd and processed onto the server.
All samples I have found (including the MSDNs) show how to use queued component in one host only. Could someone help me in configure a two host cenario

Cheers

Eric
12/9/2003 8:51:06 AM
Hi folks

Found the error, or better, the errors. The problem was fixed adding permission to Anonymous logon AND using DIRECT=TCP moniker. I have tried those, but not together. :

Now, I'd like to find-out why the DIRECT=OS or PathName= monkers doesn't work..

Cheers

AddThis Social Bookmark Button