custom logging sink for logging application block

[Ollie Riches]

I have written a custom logging sink for the enterprise library logging
application block (June 2005). I have been able to configure it as expected
from the UI config tool (EntLibConfig.exe).

I have built a console application to test it with and I am getting the
following error message write to the default trace log when I attempt to use
my custom logging sink.

'An error occurred while the Distributor was processing the message. Please
check your configuration files for errors or typos. Verify that your sinks
are reachable (queues exist, permissions are set, database exists, etc...)'

This might be security related can anyone give me the answer on how to fix
this?

I can see from VS that the module for my custom logging sink is loaded at
runtime but I am unable to break into the assembly which indicates to me
that any of the 'LogSink' overridden methods are not being called.

Cheers

Ollie Riches

[Ollie Riches]

found the problem was that my class derived from 'SinkData' was returning
'NULL' for the property 'TypeName'

Ollie
"Ollie Riches" <ol**********@phoneanalyser.net> wrote in message
news:eq**************@TK2MSFTNGP10.phx.gbl...

I have written a custom logging sink for the enterprise library logging
application block (June 2005). I have been able to configure it as expected
from the UI config tool (EntLibConfig.exe).

I have built a console application to test it with and I am getting the
following error message write to the default trace log when I attempt to
use my custom logging sink.

'An error occurred while the Distributor was processing the message.
Please check your configuration files for errors or typos. Verify that
your sinks are reachable (queues exist, permissions are set, database
exists, etc...)'

This might be security related can anyone give me the answer on how to fix
this?

I can see from VS that the module for my custom logging sink is loaded at
runtime but I am unable to break into the assembly which indicates to me
that any of the 'LogSink' overridden methods are not being called.

Cheers

Ollie Riches