Home | Contact Us | FAQ | Search & Site Map | Link to Us
Sign In | Join | Other 45 Sites in Network
HomeAnnouncementsFree MagazinesWhite PapersSubmit Content
Discussion GroupsASP.NETWindows FormsLanguages.NET FrameworkVisual Studio.NET
Articles.NET FrameworkASP.NETToolsWindows Forms
.NET DirectoryOpen Source ProjectsUser GroupsWeb Resources
Related Topics
Visual Basic 6SQL ServerMS AccessOther DB ProductsMS Server ProductsMore Topics ...

.NET Forum / .NET Framework / Distributed Applications / April 2004

Tip: Looking for answers? Try searching our database.

Queued Components not recieving messages

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
Nigel - 23 Apr 2004 21:41 GMT
Environment COM+, msmq, sERVER 200

I am executing the following

iQc = (IQEmpInsert) Marshal.BindToMoniker(@"queue:/new:Business.busEmployee")
iQc.Insert ("","cnnString")

Everything seems to work fine except the COM+ component never gets the message, no messages show up in the queue and no MSMQ triggers are fired

when I call the COM+ component directly
iQc = (IQEmpInsert) new Business.busEmployee()
iQc.Insert ("","cnnString")

No problem

Any help will be greatly appreciated

PS. is there a Trace I can enable
Marcelo Dabanovich Lavio - 24 Apr 2004 03:16 GMT
Hi Nigel,

Just a checklist:

1. Did you call Marshal.ReleaseComObject(iQc) just after you call the
business method on the queued component recorder?

Your code should look like:

iQc = (IQEmpInsert)
Marshal.BindToMoniker(@"queue:/new:Business.busEmployee");
iQc.Insert ("","cnnString");
Marshal.ReleaseComObject(iQc);

2. Did you click on "Refresh" on the view of the application queues? The MMC
will not show you updated data, no matter how many messages are inserted or
removed from that queues. You must "Refresh" to see the actual data.

3. Why do you have any MSMQ triggers set to fire from COM+ application
queues? Are you just trying to receive a notification if something new
"appears" in the queues?

4. Is your queued COM+ Server application running? Did you start it? Are the
"Queued" and "Listen" options of the Queuing tab of the COM+ Server
application properties both set? In case they are not both set, please mark
both the checkboxes, shutdown and restart the COM+ Application.

I'm using queued components on a very large project, based on Windows 2003
Server, COM+ 1.5, MSMQ 3.0 (MSMQ Triggers are not installed), .NET 1.1,
without any problem so far.

HTH,
Marcelo Lavio

> Environment COM+, msmq, sERVER 2003
>
[quoted text clipped - 14 lines]
>
> PS. is there a Trace I can enable ?
Nigel - 24 Apr 2004 13:51 GMT
Thanks but I double checked all these and used the Marshal.ReleaseComObject (iQc)

Still not working

I also moved the code to the COM+ server and called SetComplete()  no difference

I also checked the Queue check box on the Components Interface
and  have a break point set on the .NET method hosted in the  dllhost.exe process which never gets hit when called via the queued interface

I tried stopping the MSMQ service and get the expected error

Is there a way to enable tracing. I get nothing in the Eventlog, No messages stuck in the queue

The triggers were just for testing purposes
Nigel - 24 Apr 2004 19:36 GMT
Problem solved
I had Authentication Checked on the Queue
(playing around a bit to much)

Thanks Marcelo. for making me double check

Nigel

Free Magazines

Get these publications absolutely FREE for up to 12 months. There are no hidden fees and no obligation. Simply choose a title, complete the application form and submit it. Read more ...

Oracle MagazineNetwork ComputingComputer WorldBio-IT WorldeWeekInformation WeekInfosecurity
 
Sign In
Join
My Latest Posts
My Monitored Threads
My Blog
My Photo Gallery
My Profile
My Homepage

Start New Thread
Enable EMail Alerts
Rate this Thread



©2008 Advenet LLC   Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.