# Filebeat MSSQL Module - Log Unreadable
**URL:** https://discuss.elastic.co/t/filebeat-mssql-module-log-unreadable/329066
**Category:** Beats
**Tags:** beats-module, filebeat
**Created:** [March 31, 2023, 3:33pm UTC](https://discuss.elastic.co/t/filebeat-mssql-module-log-unreadable/329066 "2023-03-31T15:33:16Z")
**Posts on this page:** 3
**Page:** 1
### Author:  [@OscarFilho](https://discuss.elastic.co/u/OscarFilho)
#### Post date: [March 31, 2023, 3:33pm UTC](https://discuss.elastic.co/t/filebeat-mssql-module-log-unreadable/329066/1 "2023-03-31T15:33:16Z")
I installed filebeat 8.7 on my SQL Server and enabled the MSSQL module.
Filebeat is normally collecting the logs from the folders I configured, but the original log message is unreadable:
> 72.\u0000\u0000\u0000\u0000��\r��\n\u0000\u0000\<\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000
I'm sending these logs to logstash and it sends them to the Elastic Cloud cluster, but I couldn't read anything.
Someone can help me?
---
### Author:  [@Rios](https://discuss.elastic.co/u/Rios)
#### Post date: [March 31, 2023, 9:13pm UTC](https://discuss.elastic.co/t/filebeat-mssql-module-log-unreadable/329066/2 "2023-03-31T21:13:36Z")
AFAIK, you have to set encoding to UTF-16.
---
### Author:  [@system](https://discuss.elastic.co/u/system)
#### Post date: [April 28, 2023, 11:13pm UTC](https://discuss.elastic.co/t/filebeat-mssql-module-log-unreadable/329066/3 "2023-04-28T23:13:43Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.