"pikachusalad" wrote:

> I'm getting this also.  Apparently, nobody else in the world is...besides us.
>
> Event Type:    Error
> Event Source:    .NET Runtime
> Event Category:    None
> Event ID:    1022
> ...
> Description:
> .NET Runtime version 2.0.50727.42 - Failed to CoCreate profiler.

"William Sullivan" wrote:

> I keep getting these two error evens in my event log, and I can't find any
> information on what the cause is:
>
> .NET Runtime version 2.0.50727.42 - CLR 2.0 does not support profilers
> written for CLR 1.x
>
> .NET Runtime version 2.0.50727.42 - Failed to CoCreate profiler.
>
> Fifty million frigging times I get this in the Event Log.  I think it has
> something to do with writing to the event log.  ALSO, how the heck do you get
> rid of this nonsense prepended to every EventLog message my windows service
> writes:
>
> The description for Event ID ( 0 ) in Source ( MyWickedYetAnnoyingC#Service)
> cannot be found. The local computer may not have the necessary registry
> information or message DLL files to display messages from a remote computer.
> You may be able to use the /AUXSOURCE= flag to retrieve this description; see
> Help and Support for details. The following information is part of the event:

"Kevin Burton" wrote:

> Any resolution? I am getting this same error
>
> The description for Event ID ( 0 ) in Source ( Application ) cannot be
> found. The local computer may not have the necessary registry information or
> message DLL files to display messages from a remote computer. You may be able
> to use the /AUXSOURCE= flag to retrieve this description; see Help and
> Support for details. The following information is part of the event:
> ApplicationException occured 1 times.
>
> I am just copying the code in the examples on Microsofts web site.
>
>             Dim log As New EventLog
>             log.Source = "Application"
>             ' Write an informational entry to the event log.
>             For Each key As Object In errorHashtable.Keys
>                 log.WriteEntry(String.Format("{0} occured {1} times", key,
> errorHashtable.Item(key)))
>             Next
>             log.Close()
>
> Thank you.
>
> Kevin
>
> "William Sullivan" wrote:
>
> > I keep getting these two error evens in my event log, and I can't find any
> > information on what the cause is:
> >
> > .NET Runtime version 2.0.50727.42 - CLR 2.0 does not support profilers
> > written for CLR 1.x
> >
> > .NET Runtime version 2.0.50727.42 - Failed to CoCreate profiler.
> >
> > Fifty million frigging times I get this in the Event Log.  I think it has
> > something to do with writing to the event log.  ALSO, how the heck do you get
> > rid of this nonsense prepended to every EventLog message my windows service
> > writes:
> >
> > The description for Event ID ( 0 ) in Source ( MyWickedYetAnnoyingC#Service)
> > cannot be found. The local computer may not have the necessary registry
> > information or message DLL files to display messages from a remote computer.
> > You may be able to use the /AUXSOURCE= flag to retrieve this description; see
> > Help and Support for details. The following information is part of the event:

> Nope, but we are holding meetings the third tuesday every month.  Coffee and
> donuts provided.
>
> "Kevin Burton" wrote:
>
> > Any resolution? I am getting this same error
> >
> > The description for Event ID ( 0 ) in Source ( Application ) cannot be
> > found. The local computer may not have the necessary registry information or
> > message DLL files to display messages from a remote computer. You may be able
> > to use the /AUXSOURCE= flag to retrieve this description; see Help and
> > Support for details. The following information is part of the event:
> > ApplicationException occured 1 times.
> >
> > I am just copying the code in the examples on Microsofts web site.
> >
> >             Dim log As New EventLog
> >             log.Source = "Application"
> >             ' Write an informational entry to the event log.
> >             For Each key As Object In errorHashtable.Keys
> >                 log.WriteEntry(String.Format("{0} occured {1} times", key,
> > errorHashtable.Item(key)))
> >             Next
> >             log.Close()
> >
> > Thank you.
> >
> > Kevin
> >
> > "William Sullivan" wrote:
> >
> > > I keep getting these two error evens in my event log, and I can't find any
> > > information on what the cause is:
> > >
> > > .NET Runtime version 2.0.50727.42 - CLR 2.0 does not support profilers
> > > written for CLR 1.x
> > >
> > > .NET Runtime version 2.0.50727.42 - Failed to CoCreate profiler.
> > >
> > > Fifty million frigging times I get this in the Event Log.  I think it has
> > > something to do with writing to the event log.  ALSO, how the heck do you get
> > > rid of this nonsense prepended to every EventLog message my windows service
> > > writes:
> > >
> > > The description for Event ID ( 0 ) in Source ( MyWickedYetAnnoyingC#Service)
> > > cannot be found. The local computer may not have the necessary registry
> > > information or message DLL files to display messages from a remote computer.
> > > You may be able to use the /AUXSOURCE= flag to retrieve this description; see
> > > Help and Support for details. The following information is part of the event:

"Damien" wrote:

> William Sullivan wrote:
> > Nope, but we are holding meetings the third tuesday every month.  Coffee and
> > donuts provided.
> >
> > "Kevin Burton" wrote:
> >
> > > Any resolution? I am getting this same error
> > >
> > > The description for Event ID ( 0 ) in Source ( Application ) cannot be
> > > found. The local computer may not have the necessary registry information or
> > > message DLL files to display messages from a remote computer. You may be able
> > > to use the /AUXSOURCE= flag to retrieve this description; see Help and
> > > Support for details. The following information is part of the event:
> > > ApplicationException occured 1 times.
> > >
> > > I am just copying the code in the examples on Microsofts web site.
> > >
> > >             Dim log As New EventLog
> > >             log.Source = "Application"
> > >             ' Write an informational entry to the event log.
> > >             For Each key As Object In errorHashtable.Keys
> > >                 log.WriteEntry(String.Format("{0} occured {1} times", key,
> > > errorHashtable.Item(key)))
> > >             Next
> > >             log.Close()
> > >
> > > Thank you.
> > >
> > > Kevin
> > >
> > > "William Sullivan" wrote:
> > >
> > > > I keep getting these two error evens in my event log, and I can't find any
> > > > information on what the cause is:
> > > >
> > > > .NET Runtime version 2.0.50727.42 - CLR 2.0 does not support profilers
> > > > written for CLR 1.x
> > > >
> > > > .NET Runtime version 2.0.50727.42 - Failed to CoCreate profiler.
> > > >
> > > > Fifty million frigging times I get this in the Event Log.  I think it has
> > > > something to do with writing to the event log.  ALSO, how the heck do you get
> > > > rid of this nonsense prepended to every EventLog message my windows service
> > > > writes:
> > > >
> > > > The description for Event ID ( 0 ) in Source ( MyWickedYetAnnoyingC#Service)
> > > > cannot be found. The local computer may not have the necessary registry
> > > > information or message DLL files to display messages from a remote computer.
> > > > You may be able to use the /AUXSOURCE= flag to retrieve this description; see
> > > > Help and Support for details. The following information is part of the event:
>
> I do not know what is causing these profiler error messages. But to get
> rid of the annoying "The description of Event ID ( 0 ) in Source..."
> message, it usually suffices to do the following:
>
> Open Regedit. Navigate to
> HKLM\SYSTEM\CurrentControlSet\Services\EventLog\Application\<Name of
> Event Source>
>
> Where <Name of Event Source> is whatever name you're doing logging
> under. Under this key, there should be a value called EventMessageFile,
> which should be a REG_SZ containing the path to EventLogMessages.dll,
> within the appropriate framework directory (e.g.
> c:\windows\microsoft.net\framework\v2.0.50727\EventLogMessages.dll).
>
> This will stop the additional extraneous comments in the event log. It
> won't stop the messages being created (which, as I said, I do not know
> the cause of).
>
> Damien
>
>