Task Manager

Is there a specific task you can end instead of killing everything? 

a4wContainer.exe

But if you are on RDP session, that will kill everyone working in Sage, will it not?  Also, using RDP, users do not have access to task manager, by the time they call IT hundreds of emails are already sent?  Sage should develop another options for users specifically.

Everyone uses terminal server now or cloud apps, you would think there would be a better way?

No, it won't.  You pick only that user's a4wcontainer.

What Jay said, and if you're worried about finding the right one in time, in Task Manager under the Users Tab, just force sign-off the user in question so they're logged out, terminating all of their Sage processes. 

Thank you both for your reply.  My thought is for the user. When this type of error/action is performed by the user, it is immediate panic. If it is printing, not big deal you can cancel the print or turn off the printer.  It is not so easy if you are emailing documents.  If the user does not have access to the task manager, or don't know how to use the task manager (most users), then there is no quick way to stop the process. I was hoping that there would be an easy way for the user to stop the process. 

But thank you, I really appreciate the input.

This type of self-managed emailing is possible but you would need to buy a more functional email module that has many more features including queue management, delayed emailing, etc.  Consider something like Pacific Technology's Key Communications module or something like Print Boss (?) in the USA, from memory that's very popular over there.  Good luck!

Teach them Ctrl-Alt-End so that they can bring up their own task manager on the RDP session and kill it off.

Hi BNS7110,

Since you know what program that should be killed, one last resource would be creating a batch or PowerShell script and have it as an icon for each user who may risk sending hundreds of emails. The mission of this batch or script is to kill a4wContainer.exe running under the user who triggered the batch.