Doesn't Play Well With Others
Error message explanation attempt. It's always only an attempt, isn't it. But I've got some further information on the "No Response Allowed" error reported by Ng Derrick.
No Response Allowed
When I try to forward or reply to a mail inside my e-mail using the software "Outlook", it gives me this message: Web page authoring features are not available when Word is running inside another application.
When you setup Outlook and have Word on your machine, it asks you if you would like to use Word as your default mail editor. Microsoft has a set of "web page authoring features" (WPAF) available for use in Word that let you use it to edit webpages within Word as they appear, instead of only being able to hand-write the HTML code within Word. Outlook also has an "option" to send mail in HTML format so that you can do more than just send plain text. Colors, fonts, etc. are all available, though only if you send across a Microsoft Exchange server.
But ... for some reason the author of Word's WPAF wrote them in such a fashion that it can't be used by Word if Word's being used by another application (i.e. to display an email message in Outlook).
So there's the problem. My recommendations are either get Outlook to NOT use Word as your email editor, uninstall the WPAF from Word, or turn off sending email in HTML format in Outlook. That last option may not necessarily work, but it's worth a shot.
It's the case of a late development that didn't go through full-on integrated testing, so I'd label these features that have "features" as "Doesn't Play Well With Others."
Submitted by: David Raynor
"Doesn't Play Well With Others" -- isn't that what the Judiciary has decided about Microsoft as a whole? Maybe we should send them to bed without supper and ground them for a few years until they learn better manners …
The real problem, of course, isn't whether an error message can be explained but that none of these messages should never need explanation at all.
However, in this particular instance, there should simply never have been an occasion for the error message in the first place. In this instance what the error message is reporting (badly) is simply a design flaw.