If I use the edit feature to copy text from the body of a message in Outlook
2007 I get the following error when I try to start Word 2007.
..NET Runtime version 2.0.50727.1433 - Fatal Execution Engine Error
(79FFEE24) (80131506)
Word 2007 does not open.
If I close Outlook and reopen it the error goes away. Also if I leave Word
open while performing the edit in Outlook it does not generate the error.
Does anyone have a resolution for this issue?
Re: Runtime error after using edit in Outlook 2007
Have you run Office Diagnostics yet?
--
Milly Staples [MVP - Outlook]
Post all replies to the group to keep the discussion intact.
After furious head scratching, ChrisO asked:
| If I use the edit feature to copy text from the body of a message in
| Outlook 2007 I get the following error when I try to start Word 2007.
| .NET Runtime version 2.0.50727.1433 - Fatal Execution Engine Error
| (79FFEE24) (80131506)
| Word 2007 does not open.
| If I close Outlook and reopen it the error goes away. Also if I leave
| Word open while performing the edit in Outlook it does not generate
| the error. Does anyone have a resolution for this issue?
Re: Runtime error after using edit in Outlook 2007
After running the diagnostics it did not find any issues. I did see a post at
another Microsoft site about issues with the .Net program. Please let me know
if you have any other suggestions.
Thank you.
"Milly Staples [MVP - Outlook]" wrote:
> Have you run Office Diagnostics yet?
>
> --
> Milly Staples [MVP - Outlook]
>
> Post all replies to the group to keep the discussion intact.
>
> After furious head scratching, ChrisO asked:
>
> | If I use the edit feature to copy text from the body of a message in
> | Outlook 2007 I get the following error when I try to start Word 2007.
> | .NET Runtime version 2.0.50727.1433 - Fatal Execution Engine Error
> | (79FFEE24) (80131506)
> | Word 2007 does not open.
> | If I close Outlook and reopen it the error goes away. Also if I leave
> | Word open while performing the edit in Outlook it does not generate
> | the error. Does anyone have a resolution for this issue?
>
>
>