Fatal Execution Engine Error (7A060941) (80131506)

[Vulgrin]

I have a web service that I've built and is running at a customer's
site. We have been having issues with it dying in the middle of the
day, sometimes completely silently, other times with errors in the
event log. When there are errors, there are always two:

1. Fatal Execution Engine Error
2. Service specific error, faulting mscorwks.dll

Now, I've been googling these errors, and found that there was a KB
for it here: http://support.microsoft.com/kb/913384 and
http://support.microsoft.com/kb/924895. When I first started dealing
with the error, the framework build numbers matched the KB:
2.0.50727.42. BUT, I've applied the hotfix in question and am now at
version: 2.0.50727.208 and the problem still persists.

On my Vista development machine I check my 2.0 version and I'm
actually at 2.0.50727.312. I can't seem to find any good reference on
the various build numbers and whether the current issue I'm having was
perhaps fixed in a later build.

Any advice?

Thanks

 

[Vulgrin]

I've dug around and noticed this really suspicious piece of text on
the System.Drawing.Printing namespace that I've never seen before
(http://msdn2.microsoft.com/en-us/library/
system.drawing.printing.aspx)

"Classes within the System.Drawing.Printing namespace are not
supported for use within a Windows service or ASP.NET application or
service. Attempting to use these classes from within one of these
application types may produce unexpected problems, such as diminished
service performance and run-time exceptions."

Does anyone know WHY these classes are unsafe for services and WHAT
someone would use to talk to the printer instead? I can't believe MS
is saying "don't ever talk to printers from a service." And, I can
manage the security context just fine, so I can make the service run
as a user with the proper permissions to the printers.

But basically, we're seeing a lot of instability when the service is
very busy. I'm seeing the instability the most now around when I am
tracking down printer settings like trays and paper sizes to give to
my PrintDocument object.

Any help would be appreciated.

 

[Vulgrin]

I've dug around and noticed this really suspicious piece of text on
the System.Drawing.Printing namespace that I've never seen before
(http://msdn2.microsoft.com/en-us/library/
system.drawing.printing.aspx)

"Classes within the System.Drawing.Printing namespace are not
supported for use within a Windows service or ASP.NET application or
service. Attempting to use these classes from within one of these
application types may produce unexpected problems, such as diminished
service performance and run-time exceptions."

No one out there in the entire world has any clue on this one? Can
anyone from Microsoft speak to this? I've done loads of things lately
(such as caching the printersettings objects so I don't have to talk
to the printers as much, and staggering the print jobs to not happen
simultaneously) yet I'm still hard crashing the service a couple times
a day - with no rhyme or reason or to the crashes.