Using Classic Outlook on Windows for personal email, calendar, and contact management
Same problem, from multipke sources. Very annoying.
This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
Hi all, today I got an error message when opening Ms. Outlook with the following error message (We cannot render a new actionable message right now. Please close an existing one in Microsoft Outlook and retry) As for what I have done =
*Update office version
*Re-install O365
but neither of those things solved the problem, really appreciate if anyone in this forum can give more advice.
(no problem sending messages via OWA)
Using Classic Outlook on Windows for personal email, calendar, and contact management
Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.
Same problem, from multipke sources. Very annoying.
I had just one user with this issue in a company of just over 100. I had her case open because I could not find an answer anywhere. Now, this may not be a fix but when working on another Outlook issue for her I rebuilt the .ost and this error also went away. It is an easy solution to try. I hope it works for you.
We just had this issue come up with a computer in our management.
We found that installing the Actionable Messages Debugger cleared the issue.
We haven't seen the error come back, and aren't sure if this is a 100% resolution. But it seems to work for now.
https://appsource.microsoft.com/en-us/product/office/wa104381686?tab=overview
Another option you could try would be to roll back the version of Office.
Hi MSFT,
I have been assisting a user on this and we've been struggling to find the answer to this issue as it shows up at random times.
Considering basic troubleshooting has been done (i.e. recreated mail profile, repaired/reinstalled MSO/Outlook).
Can you please confirm if this is indeed a bug as it only started happening during the most recent updates, for over a week or so? It was not an issue prior to that. Reading this forum made me realize that many users started having this issue almost within the same timeframe. Can someone from Microsoft please verify if this is being addressed and do we have an ETA for the fix?
We'd really appreciate your help.
Thank you.
Yeah, I have got one user too who is getting the same error.