# Filebeat with MSSQL - text not decode properly - utf-16le

**URL:** https://discuss.elastic.co/t/filebeat-with-mssql-text-not-decode-properly-utf-16le/360536
**Category:** Beats
**Tags:** filebeat
**Created:** [May 30, 2024, 6:51am UTC](https://discuss.elastic.co/t/filebeat-with-mssql-text-not-decode-properly-utf-16le/360536 "2024-05-30T06:51:21Z")
**Posts on this page:** 1
**Page:** 1

<div class="post-metadata">

### Author: ![seymanurmutlu](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/seymanurmutlu/32/134927_2.png) [@seymanurmutlu](https://discuss.elastic.co/u/seymanurmutlu)
#### Post date: [May 30, 2024, 6:51am UTC](https://discuss.elastic.co/t/filebeat-with-mssql-text-not-decode-properly-utf-16le/360536/1 "2024-05-30T06:51:21Z")

</div>

Hello,

I am using filebeat on Windows 10 sending logs to a remote server. But lines are not decoded correctly.

Files are on hex format if I use this configuration on filebeat.yaml ;

```auto
# ------------- MSSQL -------------
filebeat.modules:
  - module: mssql
    log:
      enabled: true
      var.paths: ['Z:\Audit\*.sqlaudit']

```

Files are not correctly decoding if I use this configuration on filebeat.yaml ;

```auto
# ------------- MSSQL -------------
filebeat.modules:
  - module: mssql
    log:
      enabled: true
      var.paths: ['Z:\Audit\*.sqlaudit']
      input:
        encoding: utf-16le
        multiline.pattern: '^\d\d'
        multiline.negate: true
        multiline.match: after

```