VMware Cloud Community
pinky_cloudital
Contributor
Contributor
Jump to solution

Charset problem while logging MSSQL Server 2008

Hi,

we have installed vRealize Log Insight 2.5 GA (Version 2.5.0-2347850) on a VM (Content Pack MS Server installed) .

I've installed the agent on a MS Windows VM with MSSQL Server 2008. I've modified the liagent.ini  as follow.

[filelog|MSSQL]

directory=E:\MSSQL10.MSSQLSERVER\MSSQL\Log

charset=UTF-16LE

event_marker=^[^\s]

Checking Log Insight I see a problem with characters (char set ?)

2015-02-1610:41:06.135

툄撦ᱤЀ⁕#琌攀洀瀀搀戀㄀Ѐ2师 輀㌀ࠀ⃧ቃ4䌠 䀀ሀcberg02dbBĄࣿ  )￶⸆鼀̀Ѐ  (퉟

Someone know why ?

thanks

Maurizio

Labels (1)
0 Kudos
1 Solution

Accepted Solutions
pinky_cloudital
Contributor
Contributor
Jump to solution

solved using

[filelog|SQL2008]

directory=E:\MSSQL10.MSSQLSERVER\MSSQL\Log

charset=UTF-16LE

event_marker=^\d{4}-\d{2}-\d{2} \d{2}:\d{2}:\d{2}\.\d{2}

View solution in original post

0 Kudos
2 Replies
pinky_cloudital
Contributor
Contributor
Jump to solution

solved using

[filelog|SQL2008]

directory=E:\MSSQL10.MSSQLSERVER\MSSQL\Log

charset=UTF-16LE

event_marker=^\d{4}-\d{2}-\d{2} \d{2}:\d{2}:\d{2}\.\d{2}

0 Kudos
sflanders
Commander
Commander
Jump to solution

Changing the event_marker on impacts the definition of an event -- so you can handle multiple line messages. If you are seeing funny symbols then that means that you are collecting SQL trace files, which are in binary. To fix the issue, you need to change the configuration to:

[filelog|MSSQL]

directory=E:\MSSQL10.MSSQLSERVER\MSSQL\Log

exclude=*.trc

charset=UTF-16LE

event_marker=^[^\s]

The Solution Exchange listing should have been updated, but looks like it has not yet. I will follow up on this.

Hope this helps! === If you find this information useful, please award points for "correct" or "helpful". ===
0 Kudos