Deadletters
  Home FAQ Contact Sign in
 
Advanced search
MATCHING GROUPS



more...
POPULAR GROUPS

more...

found 24 articles for 0.304 sec
On Feb 20, 4:50 pm, "Yoel Arnon" <y...@msmq.biz> wrote: > Hi, > "Exists" will not work with the deadletter queue. This is a system queue > that always exists. Just try using it. > > BTW it will probably work only on the machine with the specified QM GUID > (c382cb83-73a5-c2b9-00a0-216fa6a87965), and not with remote machine, because > Windows CE does not fully support Active Directory integration     

Group: microsoft.public.msmq.programming · Group Profile · Search for Deadletters in microsoft.public.msmq.programming
Author: Doc
Date: Feb 25, 2008 07:25

Hi, "Exists" will not work with the deadletter queue. This is a system queue that always exists. Just try using it. BTW it will probably work only on the machine with the specified QM GUID (c382cb83-73a5-c2b9-00a0-216fa6a87965), and not with remote machine, because Windows CE does not fully support Active Directory integration. If want to write a code that will work from any machine, either
Show full article (2.83Kb) · Show article thread
On Feb 20, 2:10 pm, "Yoel Arnon" <y...@msmq.biz> wrote: > Hello, > From the same device, you can simply open the queue using > System.messaging.MessageQueue with path equals > "FormatName:MACHINE=c382cb83-73a5-c2b9-00a0-216fa6a87965;DEADLETTER" > > Alternatively, you can try "FormatName:direct=os:.\system$;deadletter" from > the local machine or "FormatName:direct=os:<machine > name>\system$     

Group: microsoft.public.msmq.programming · Group Profile · Search for Deadletters in microsoft.public.msmq.programming
Author: Yoel Arnon
Date: Feb 20, 2008 13:50

On Feb 20, 2:10 pm, "Yoel Arnon" <y...@msmq.biz> wrote: Hello, From the same device, you can simply open the queue using System.messaging.MessageQueue with path equals "FormatName:MACHINE=c382cb83-73a5-c2b9-00a0-216fa6a87965;DEADLETTER" Alternatively, you can try "FormatName:direct=os:.\system$;deadletter" from the local machine or "FormatName:direct=os:<machine \system$
Show full article (2.27Kb) · Show article thread
Hello, From the same device, you can simply open the queue using System.messaging.MessageQueue with path equals "FormatName:MACHINE=c382cb83-73a5-c2b9-00a0-216fa6a87965;DEADLETTER" Alternatively, you can try "FormatName:direct=os:.\system$;deadletter" from the local machine or "FormatName:direct=os:<machine name>\system$;deadletter". For details, see http://msdn2.microsoft.com/en-us/library/ms895244     

Group: microsoft.public.msmq.programming · Group Profile · Search for Deadletters in microsoft.public.msmq.programming
Author: Doc
Date: Feb 20, 2008 11:29

The following works fine under ActiveDomain MSMQ: m_qDeadLetter = new MessageQueue(".\\DeadLetter$"); But under Workgroup throws the following error: A workgroup installation computer does not support the operation. at System.Messaging.MessageQueue.GetMachineId I also tried: .\System$\Deadletter$ .\System$\Deadletter DIRECT=OS:.\Deadletter$ DIRECT=OS:.\SYSTEM$;DEADLETTER But no
Show full article (1.55Kb) · Show article thread
I had meesages sent from the server fall in to the Deadletter queue on the Pocket PC ie When the client the PPC is off the network for more than 10 mins . Their are no errors in the MSMQ log file . Infact i have set 90 days for the registry keys Connection time out and ideal time out . Any ideas on solving this . Can i acess the Deadletter queue on the Pocket pc and read those mesages.     

Group: microsoft.public.msmq.programming · Group Profile · Search for Deadletters in microsoft.public.msmq.programming
Author: Doc
Date: Feb 20, 2008 11:27

Thanks Yoel, It appears to be working okay now that I better understand the time to reach queue versus time to be received relationship. I have set the time to reach queue to a nominal value of 15 minutes and set the time to be received to 45 minutes. That may be more than necessary but testing shows the transactions are completing successfully now and no messages are showing up in the
Show full article (1.36Kb) · Show article thread
    

Group: microsoft.public.msmq.programming · Group Profile · Search for Deadletters in microsoft.public.msmq.programming
Author: Yoel Arnon
Date: Feb 20, 2008 11:10

Show full article (1.00Kb) · Show article thread
    

Group: microsoft.public.msmq.programming · Group Profile · Search for Deadletters in microsoft.public.msmq.programming
Author: Doc
Date: Feb 20, 2008 07:21

Show full article (0.35Kb)
    

Group: microsoft.public.msmq.programming · Group Profile · Search for Deadletters in microsoft.public.msmq.programming
Author: Uri Kluk
Date: Apr 5, 2007 15:14

Show full article (0.49Kb)
    

Group: microsoft.public.windowsce.embedded · Group Profile · Search for Deadletters in microsoft.public.windowsce.embedded
Author: Prawin
Date: Nov 23, 2006 02:38

Show full article (0.41Kb)
    

Group: microsoft.public.msmq.programming · Group Profile · Search for Deadletters in microsoft.public.msmq.programming
Author: intractably
Date: Jul 24, 2006 17:00

Show full article (0.24Kb)
    

Group: microsoft.public.msmq.programming · Group Profile · Search for Deadletters in microsoft.public.msmq.programming
Author: JMZ
Date: Mar 31, 2008 06:23

Show full article (2.92Kb) · Show article thread
1 · 2 · 3 · next