From: Amanda on
I saw the following error on one of our servers.

..NET Runtime version 2.0.50727.42 - Fatal Execution Engine Error (7A2B45A2)
(0).

I have looked this up in Microsoft's knowledgebase and the fix for it is for
2000 and 2003, and there is supposed to be another error in conjunction with
the above one. The server is running XP and there is no other error besides
the one above. This error caused our software to crash. It does not appear
that it was a problem with our software however. I would appreciate any
suggestions anyone has.


From: Andrew E. on
Thier is a hotfix for .NET 2.0,its 913047

"Amanda" wrote:

> I saw the following error on one of our servers.
>
> .NET Runtime version 2.0.50727.42 - Fatal Execution Engine Error (7A2B45A2)
> (0).
>
> I have looked this up in Microsoft's knowledgebase and the fix for it is for
> 2000 and 2003, and there is supposed to be another error in conjunction with
> the above one. The server is running XP and there is no other error besides
> the one above. This error caused our software to crash. It does not appear
> that it was a problem with our software however. I would appreciate any
> suggestions anyone has.
>
>
From: Amanda on
I believe that hotfix is for if "you use HTTPS to download managed code from
a source server computer. Then, you connect back to the source server
computer through a proxy. In this scenario, the application may crash."

This is not happening on the server. Thanks for the suggestion those. I
welcome any others.


"Andrew E." wrote:

> Thier is a hotfix for .NET 2.0,its 913047
>
> "Amanda" wrote:
>
> > I saw the following error on one of our servers.
> >
> > .NET Runtime version 2.0.50727.42 - Fatal Execution Engine Error (7A2B45A2)
> > (0).
> >
> > I have looked this up in Microsoft's knowledgebase and the fix for it is for
> > 2000 and 2003, and there is supposed to be another error in conjunction with
> > the above one. The server is running XP and there is no other error besides
> > the one above. This error caused our software to crash. It does not appear
> > that it was a problem with our software however. I would appreciate any
> > suggestions anyone has.
> >
> >
From: guilhermemagalhaes on
http://support.microsoft.com/kb/913384