Deadly Catastrophic Error in Outlook.com
-
I have been observing this hitch in the ratio of 1:7 emails. What happens is when the send button is clicked, a quick popup near right says 'Could not send message'. When you click that popup, the compose box opens little elevated. In this scenario neither can you send the email nor you can save a draft of it. Attempting to save a draft gives the message that item does not exist. The only way to escape this whirlpool is to discard and confirm your intent to discard the message., Looks like it is something like Trappable Error in Classic ASP where the only fix was to restart the IIS or the web server computer itself. Some patterns that seem to be contributing to this error are like inline images in email. Looking at the quality of the application, I really doubt if Microsoft has cared to test the application or is in a mad rush to compete with its rivals. How many of you have experienced this issue?
-
It is significant error because the primary objective of sending email is not met. We use Outlook.com primarily to send email and that purpose is defeated right in the Compose page itself, which is unacceptable.
-
It is significant error because the primary objective of sending email is not met. We use Outlook.com primarily to send email and that purpose is defeated right in the Compose page itself, which is unacceptable.
Deepak Vasudevan wrote:
We use Outlook.com
Now, that's deadly and catastrophic!!!
Skipper: We'll fix it. Alex: Fix it? How you gonna fix this? Skipper: Grit, spit and a whole lotta duct tape.
-
I have been observing this hitch in the ratio of 1:7 emails. What happens is when the send button is clicked, a quick popup near right says 'Could not send message'. When you click that popup, the compose box opens little elevated. In this scenario neither can you send the email nor you can save a draft of it. Attempting to save a draft gives the message that item does not exist. The only way to escape this whirlpool is to discard and confirm your intent to discard the message., Looks like it is something like Trappable Error in Classic ASP where the only fix was to restart the IIS or the web server computer itself. Some patterns that seem to be contributing to this error are like inline images in email. Looking at the quality of the application, I really doubt if Microsoft has cared to test the application or is in a mad rush to compete with its rivals. How many of you have experienced this issue?
-
I have been observing this hitch in the ratio of 1:7 emails. What happens is when the send button is clicked, a quick popup near right says 'Could not send message'. When you click that popup, the compose box opens little elevated. In this scenario neither can you send the email nor you can save a draft of it. Attempting to save a draft gives the message that item does not exist. The only way to escape this whirlpool is to discard and confirm your intent to discard the message., Looks like it is something like Trappable Error in Classic ASP where the only fix was to restart the IIS or the web server computer itself. Some patterns that seem to be contributing to this error are like inline images in email. Looking at the quality of the application, I really doubt if Microsoft has cared to test the application or is in a mad rush to compete with its rivals. How many of you have experienced this issue?
-
I have raised this issue in Microsoft Answers but not sure if we can escalate this. It should be considered as a showstopper issue. The primary objective of the page is getting defeated.
-
He givveth with one hand: [Now any Windows 10 user can complain to Microsoft using the Feedback Hub | PCWorld](http://www.pcworld.com/article/3073453/windows/now-any-windows-10-user-can-complain-to-microsoft-using-the-feedback-hub.html) :thumbsup: ..and taketh away with the other: "The company has released its Feedback Hub to all Windows 10 users [from the Windows Store]" X|
Ah, I see you have the machine that goes ping. This is my favorite. You see we lease it back from the company we sold it to and that way it comes under the monthly current budget and not the capital account.
-
Must... Send... E-mail... Facebook and twitter must be down.
I wanna be a eunuchs developer! Pass me a bread knife!
-
I haven't seen it happen.
Slogans aren't solutions.
Nor have I. But then, I wouldn't touch Outlook.com with a ten foot cattle prod. I use Live Mail instead.
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
-
It is significant error because the primary objective of sending email is not met. We use Outlook.com primarily to send email and that purpose is defeated right in the Compose page itself, which is unacceptable.
