Sending message to message queue on my machine.....Error "Invalid queue path name" [closed] - msmq

This question is unlikely to help any future visitors; it is only relevant to a small geographic area, a specific moment in time, or an extraordinarily narrow situation that is not generally applicable to the worldwide audience of the internet. For help making this question more broadly applicable, visit the help center.
Closed 9 years ago.
I am sending a message to a pretty standard message queue that I have created on my machine running Windows Server 2008 R2.
QueueName:
directionsTest
MachineName:
usernameDev
When I attempt to send the message to the queue, I receive the error. :
Invalid queue path name.
Where I am perplexed is that I am actually sending this message via an SSMS query window, we have stored procedures that send these messages to queues and we just provide machine name, queue name, and the message. So, this is basically a saved query that I have used numerous times, in fact I used this exact same query at the end of last week. Since then I have not changed the query/my machine/ the queue/ and the stored procedure that creates and sends these messages have not changed. So, I am unsure why this is giving me this error.
I have tried just about everything under the sun, I have tried creating new queues on my computer and receive the same error. I have also ensured that everyone has all access to these queues. Any ideas on what would cause this error to just pop up? I have scoured the web and I have found no clues as to what could be causing this issue. (**I have also tested sending to queues on different servers and this works without error)
Thanks for any advice/direction in advance.

Check the spelling of your queue name format.
If you use something like
YOURMACHINENAME\private$\YourQueueName
you should instead try this:
FormatName:DIRECT=OS:YOURMACHINENAME\private$\YourQueueName
Please note that the first part may be case-sensitive.

Related

Process mail bursts one at a time

we receive bursts of mails from our IDS that we are postprocessing to create incident reports, forward them to request tracker, etc. Right now, we have one script that does all the postprocessing that is called by procmail according to rules in /etc/aliases. Something like:
ids-report: "|/opt/ids/process.pl"
Now, the problem is that running many instances of this script because of mail bursts can lead to memory depletion and some synchronization nastyness.
In my script, I tried using Sys::RunAlone, but found it suboptimal.
I would like procmail to feed my script one mail from queue at a time, but I have not found a way to do it.
Do you guys have any idea, what could I do? Out-of-the-box solutions are welcomed too...
Thanks.
Why not save every mail to a file or database as soon as you receive them and process the saved records one at a time from another script ?
If you post some code you may receive more (and possibly better) answers :)
I second Georgi Rangelov's answer but if you are seriously asking how to run only one message at a time in Procmail, the answer is to use a lock file.
:0:only1.lock
| /opt/ids/process.pl
This means, if the file only1.lock exists, wait. Once it's gone, create it, run the pipe, and then remove the lock file when done.
See also http://porkmail.org/era/procmail/mini-faq.html#locking
"IMAP with idle" mailbox as buffer/pipeline of email messages
You may deliver messages to IMAP mailbox. You can use fetchmail with --idle (to get real time processing) and --mda (to execute your script).
You can make procmail deliver messages to maildir as use dovecot even without daemon running to allow fetchmail access maildir using IMAP protocol.
P.S. I may provide a few more details if you are interested. AFAIR I had used it to handle spams catched by my spamtrap server.

Lync 2013: ConferenceFailureException "maxConferencesExceeded"

After some googling I found that this reason if caused by too many scheduled conferences by my Application Endpoint. My only problem is, how do I delete/remove currently stored scheduled conferences for my application endpoint, when the only access I have to my server is through PowerShell??
EDIT:
Just found a command that actually could increase number of scheduled meetings per organizer (Set-CsUserServicesConfiguration -MaxScheduledMeetingsPerOrganizer 2000), but it didn't change the issue. I'm still receiving MaxConferencesExceeded error. Any ideas??
Use Get-CsUserServicesConfiguration to make sure the change has actually occurred, and/or setting it globally to make sure it has the correct context for your users.
I've also found with a large pool, it can take a while to kick in.
Have you tried republishing your Lync topology after making the change? A bit dramatic, but can help with Lync gets itself into a knot with changes.

good architecture for quartz based email processor

I need to write a windows service to send emails. The emails will likely be stored in a database table and they should be sent as early as convenient. It would be advantages to have multiple threads sending messages as there will be hurts at certain times of the day however it is not good to send the same message multiple times.
So I'm having a little bit of trouble understanding in this kind of scenario how I can best leverage quartz.net to alleviate some of queueing and concurrency issues. So my architecture questions are:
1. For this kind of scenario, is it best for a Job to check if there are emails to send or should a job be to actually send one email?
2. If the answer to 1) is to check for emails to be sent then that would leave me with a concurrency issue and I would need to use DisallowConcurrentExecution which would result in only 1 email being sent at a time?
3. If there answer to 1) is send a single email then I take it the job details would need to reflect the specific ID of the email to be sent?
4. In either case - two web users could trigger the creation of the same email job (concurrently). So it doesn't seem that Quartz really helps solve my problem - it might provide a nice architecture for a unit of work and controlling polling frequency but not really the core of my problem? Or am I mssing / over thinking something?
Finally, just to be clear, each email relates to a specific Order so there is ID and state potential. So because two web users can send the same email at the same instant in time should not result in two emails being sent.
Look forward to any advice.
Thanks
Josh
Quartz.Net would meet your scheduling needs.
However, you have conflicting needs. You want "more than one thread" to send the emails, but you also want "Do not want duplicate emails".
The DisallowConcurrentExecution will prevent multiple instances of the same job running at the same time. However, if you have only one instance of the job running, you don't know which individuals emails have been sent or not sent.
If you only keep "these emails have been sent, and these haven't" in memory.....you're always at risk of sending duplicates.
You can solve this, but you're gonna have to have a "pessimistic" flag on which emails have already been sent. Like at the database level.
So if you want multiple threads to send emails...that's ok. But your "get some emails to send" code is going to have to 'mark' the emails it is working on. (So the next thread doesn't get them). Then you have to mark them again right after they are sent.
Quartz is good for scheduling the "when" your jobs run. But it doesn't have the ability to "track" which emails you need to send and which ones have already been sent. That's gonna be your responsibility.
I had this similar problem....where I had many many users trying to "get at" a bunch of to-do items. Thus why I wrote this blog entry for Sql Server. I needed to "mark" the rows, but also had to order them before I marked them.
http://granadacoder.wordpress.com/2009/07/06/update-top-n-order-by-example/
I also added some "hints".......
WITH ( UPDLOCK, READPAST , ROWLOCK ) –<<Optional Hints
because so many different users were trying to "get-at" the items.
(Think about how T1cket M#ster has to work.......there has to be some pessimistic locking on the tickets....and they have a timer that releases the locks if you don't buy the tickets in time).
Hope that helps.

Email message recall does it actually work? [closed]

Closed. This question is off-topic. It is not currently accepting answers.
Want to improve this question? Update the question so it's on-topic for Stack Overflow.
Closed 11 years ago.
Improve this question
I was asked to recall a message I sent out to remove some personal info from it and replace it with a generic made up person as an example.
Does message recall really work?
It's my opinion because you get told a message has been recalled it just causes you to want to find out what was in the original message. All you do is find someone who had already read it.
Can exchange server be adjusted to not tell users when a message is recalled or replaced?
What about bcc, recall doesn't seem to work on these and global emails tend to be the ones you really need to recall.
EDIT Also people with smartphones which is common now don't seem to get email retrieved from their phone either
In most cases, it's too late, it just let's me know there was an email you didn't want me to read.
Only works on unopened mail, for users of MS Exchange/Outlook.
read this blog post and comments for more information.
To add a bit of information, if the message is displayed in a preview pane, it is considered read making recalling impossible.
We did some testing just yeasterday and discovered that the recall feature is pretty lame. As mentioned above it is only recalled if it is unread (or unpreviewed). In the case where it has been read, the recall only makes the message MORE obvious. Not the desired effect by far.
Only works on unopened mail, local to the server you sent it on. (as far as I know, I suppose it could work on server farms/clusters too?)
If the recipient is offline and message is not delivered to his PST by the Exchange server, then RECALL works and you get the message accordingly.
Thanks & Regards,
Ajay
Yes it is true that the Recall This Message Outlook functionality very often does not work.
WinDeveloper just released a server-side solution for Excahnge 2007/2010. It works equally well for both emails addressed to local recipients and for emails sent to foreign recipients. For more details:
WinDeveloper vs Native Exchange Message Recalling
http://www.windeveloper.com/recall/recall_features.htm
Message Recalling Works! Here is how
http://www.windeveloper.com/recall/recall_howitworks.htm

MS hotfix delayed delivery [closed]

Closed. This question is off-topic. It is not currently accepting answers.
Want to improve this question? Update the question so it's on-topic for Stack Overflow.
Closed 10 years ago.
Improve this question
I just requested a hotfix from support.microsoft.com and put in my email address, but I haven't received the email yet. The splash page I got after I requested the hotfix said:
Hotfix Confirmation
We will send these hotfixes to the following e-mail address:
(my correct email address)
Usually, our hotfix e-mail is delivered to you within five minutes. However, sometimes unforeseen issues in e-mail delivery systems may cause delays.
We will send the e-mail from the “hotfix#microsoft.com” e-mail account. If you use an e-mail filter or a SPAM blocker, we recommend that you add “hotfix#microsoft.com” or the “microsoft.com” domain to your safe senders list. (The safe senders list is also known as a whitelist or an approved senders list.) This will help prevent our e-mail from going into your junk e-mail folder or being automatically deleted.
I'm sure that the email is not getting caught in a spam catcher.
How long does it normally take to get one of these hotfixes? Am I waiting for some human to approve it, or something? Should I just give up and try to get the file I need some other way?
(Update: Replaced "me#mycompany.com" with "(my correct email address)" to resolve Martín Marconcini's ambiguity.)
Took about a day for me when I requested one so I suspect some sort of manual/semi-automated process has to complete before you get the e-mail.
Give it a day before you start bugging them ;)
It usually arrives within the first hour. BUt the fact that it reads me#mycompany.com could either because you put it there to protect your privacy (in which case forget about this) or that the system didn't catch your email and they sent it to me#mycompany.com.
If the email address was ok and you didn't get it, somehow it bounced or it won't arrive. I'd suggest you contact them again providing an alternate email (gmail or such) to make sure that you don't experience any problems.
Last time I received a hotfix it took them 10 minutes.
Good luck with that!