Media Center 2004 Causing CLR2 Error?

Thread view:

Enable EMail Alerts

Start New Thread

Thread rating:

Paul B - 22 Apr 2005 18:43 GMT

Since installing .NET 2.0 Beta 2 on my MCE 2004 machine, I have been unable
to run Media Center and have been receiving the following errors in the
eventlog.

Event Type clr20r3, P1 ehrec.exe P2 5.1.2600.2180, P3 41107d79, P4 ehcir, P5
6.0.3000.0, P6 41109696, P7 12a, P8 50, P9 system.missingfieldexception, P10
NIL

This looks like the ehrec.exe program is crashing due to a conflict with
some part of the .NET Framework Beta 2, but I can't imagine why. Any
thoughts?

Reply to this Message

Henning Krause [MVP] - 22 Apr 2005 20:16 GMT

Just a guess...

perhaps, parts of the Media Center programs are written in .NET. And when
you install the Beta2, the software might run against this version of the
Framework and not against the 1.1.

If this is the cause, should adjust the settings for that program that it is
only run agains the 1.1 Framework.

You can do that by editing the ehrec.exe.config file. If it does not yet
exists, create it.

Then, ensure that it contains these lines:
<?xml version="1.0"?>
<configuration>
<startup>
<supportedRuntime version="v1.1.4322"/>
<requiredRuntime version="v1.1.4322" safemode="true"/>
</startup>
</configuration>

Greetings,
Henning Krause [MVP]
==========================
Visit my website: http://www.infinitec.de
Try my free Exchange Explorer: Mistaya
(http://www.infinitec.de/software/mistaya.aspx)

> Since installing .NET 2.0 Beta 2 on my MCE 2004 machine, I have been
> unable
[quoted text clipped - 10 lines]
> some part of the .NET Framework Beta 2, but I can't imagine why. Any
> thoughts?

Reply to this Message

Paul B - 22 Apr 2005 21:13 GMT

I thought of that actually, but ehrec.exe is not a managed assembly (per
ILDasm or Reflector). So I'm at a loss to figure out what part of its
processing (it is the automated recording process of Media Center) could be
trying to access .NET. I checked the other files in that directory and none
of them appear to be .NET assemblies.

So, for those .NET CLR 2.0 folks reading, are there any hooks into the OS
that could get triggered by a non-managed process to initiate the 2.0 CLR?

Thanks,
Paul

> Just a guess...
>
[quoted text clipped - 38 lines]
> > some part of the .NET Framework Beta 2, but I can't imagine why. Any
> > thoughts?

Reply to this Message

Joshua Flanagan - 23 Apr 2005 06:45 GMT

ehrec.exe itself might not be a managed assembly, but it might be
loading managed assemblies.
Try using Process Explorer from http://www.Sysinternals.com. It is
free, improved task manager that highlights all managed processes that
are currently running. This should help you determine exactly which
programs depend on the .NET Framework.

Joshua Flanagan
http://flimflan.com/blog

> I thought of that actually, but ehrec.exe is not a managed assembly (per
> ILDasm or Reflector). So I'm at a loss to figure out what part of its
[quoted text clipped - 50 lines]
>>>some part of the .NET Framework Beta 2, but I can't imagine why. Any
>>>thoughts?

Reply to this Message

Paul B - 23 Apr 2005 07:32 GMT

Also an excellent idea. But unfortunately ehrec.exe never actually runs, it
dies immediately on startup.

Paul

> ehrec.exe itself might not be a managed assembly, but it might be
> loading managed assemblies.
[quoted text clipped - 60 lines]
> >>>some part of the .NET Framework Beta 2, but I can't imagine why. Any
> >>>thoughts?

Reply to this Message

Rate this thread:

Media Center 2004 Causing CLR2 Error?

Free Magazines