>No - loEventLogRecord.Keywords is not null it is 36028797018963968 (which is correct for the hex value in the event log). Exception (as commented in code) is when accessing KeywordsDisplayNames. Exception type is System.Diagnostics.Eventing.Reader.EventLogNotFoundException. Don't you see the same behaviour ?

I finally found what was causing this. On that new environment, when the migration was done, the EventViewer.Keyword field was defined as Integer instead of BigInt. Once I made that change, I started to see the values. I have some like -9223372036854775808. I guess in such circumstances, as the value was not fitting, a null was being put.

Thanks for everything, that allowed me to see additional things in regards to all this.