I've got a standard enterprise library text formatter, with the default formatting. The log file is properly created, but remains empty. If I remove the last formatting option, with the extended properties (see below) it starts working. If I put it back, the log remains empty and I have no clue where to search for the error.
template="Tim...
Extended Properties: {dictionary({key} - {value}{newline})}"
(Yes I can run it with that exact abbreviated template to trigger the error). If I remove the {dictionary({key} - {value}{newline})} part it starts logging. The problem only occurs on the test server, on my local dev machine it works as expected, outputting my extended properties.
I've tried setting up a separate logging errors destination, but with no luck. Nothing gets logged there.
The ExtendedProperties dictionary must not contain nulls. This causes logging to fail because Enterprise Library does not expect null objects in this dictionary. To diagnose if this is your problem, you configure the 'Logging Errors & Warnings' category to log somewhere, then you should be able to see any errors that are occuring when logging.