Frank Løvendahl Nielsen

@andreasbraidt But try do your parameter configuration: ``` ``` So neither use `@` nor `:` in the `` declaration.

Have you tried replacing `:message:` with `'message'` to see if it passes the sql statement? Else try use the Log4NetHelper with InternalDebug, it usually reveals startup problems in regards of...

I will 👀 at this Oracle behavior, and what has been "default" previously.

Can you show the full stacktrace?

That is the callstack, i rather see the stacktrace (as text) and if possible with all inner exceptions. I am pretty sure it is not the appender that is the...

My answer is that a `null` is being passed to the logger property `userid` which leads to the `NOT NULL violation` from the database. This also explains why the console...

well, it is either a misconfiguration or data is actually null. The Appender just pass the data it get. You can post your log4net config, and the appender config -...

Seems correct, I would put the `\"userid\"` in the console logger, and disable the database appenders. Then you can see if `userid` is null (empty) while logging.