I finally figured it out today:
- the ASP.NET application is running with anonymous login enabled and so the
identity of the user that invokes the queued component is anonymous
- the message queue of the queued component on the server (created by
regsvcs) does not allow anonymous users to access the queue. This is a
change in Win 2003 where anonymous users are not part of the "Everyone"
group
- And so I had to enable "Anonymous Logon" access to that queue
Thanks for your time!
[quoted text, click to view] "Tomas Restrepo (MVP)" <tomasr@mvps.org> wrote in message
news:#H$J##vhDHA.2420@TK2MSFTNGP10.phx.gbl...
> Viju,
>
> > I have a logging service (in C#) that runs as a COM+ queued component.
The
> > clients that invoke this component can be on the same or different
> machine.
> > This was working fine in Win 2K but doesn't on Win 2003. Here is what I
> have
> > done:
> > - the queued component installs fine on a Win 2003 server and is running
> > (server)
> > - the application proxy is exported and then imported on another Win
2003
> > machine (client)
> > - on the client machine our ASP.NET application invokes the queued
> component
> > and is able to send messages. I verified this by pausing the "Outgoing
> > Queue" (new in Win 2003) that MSMQ creates on the client machine. When I
> > resume the paused outgoing queue the messages disappear and I assume
they
> > have been forwarded to the server machine.
> > - using network monitor on both machines I can see the two machines
> > communicating but my queued component doesn't appear to be invoked.
> >
> > I have logon audited and network access to COM+ services enabled also.
Any
> > clues?
>
> Is your queued component transactional? If so, do you have Network access
> enabled for the DTC as well as DCOM?
> Also, make sure you have MSMQ configured correctly (my guess is that if
you
> have hardened mode enabled, it won't work, but I could be wrong...)
>
> --
> Tomas Restrepo
> tomasr@mvps.org
>
>
