Reading Custom Log

[Lee]

When my application reads my custom error log with VB.NET the entry reads
simiar to the one below, but when it receives the EntryWritten event, the
Text is correct. How do I fix this

The message '0' for application 'WMInv' could not be formatted using
library(ies): ''. The log entry contains the following replacement
strings:'clsWil sonInv:UpdateSh ippingDB:Error in :Update
System.Data.Sql Client.SqlError : Procedure or function gsptblGrainAcco unting
has too many arguments specified.
'

[Dave]

RE: Reading Custom Log

The message you listed here is interesting because of the empty string where
the library should be:

library(ies): ''.

It should read:

libary(ies):
'C:\WINNT\Micro soft.NET\Framew ork\v1.1.4322\E ventLogMessages .dll'.

The fact that .NET was unable to determine the event message source from the
registry must be the cause of your problem, but why it would succeed when you
receive the event notification I don't know.

Please re-check your registry and consider running some diagnostics such as
RegMon (http://www.sysinternals.com/ntw2k/source/regmon.shtml) to detect key
access failures.

The registry should look like:
HKEY_LOCAL_MACH INE
SYSTEM
CurrentControlS et
Services
Eventlog
<event log name>
<event source name>

EventMessageFil e="C:\WINNT\Mic rosoft.NET\Fram ework\v1.1.4322 \EventLogMessag es.dll"


"Lee" wrote:
[color=blue]
> When my application reads my custom error log with VB.NET the entry reads
> simiar to the one below, but when it receives the EntryWritten event, the
> Text is correct. How do I fix this
>
> The message '0' for application 'WMInv' could not be formatted using
> library(ies): ''. The log entry contains the following replacement
> strings:'clsWil sonInv:UpdateSh ippingDB:Error in :Update
> System.Data.Sql Client.SqlError : Procedure or function gsptblGrainAcco unting
> has too many arguments specified.
> '[/color]