Seq Documentation and Support

Welcome to the Seq documentation hub. You'll find comprehensive guides and documentation to help you start working with Seq as quickly as possible, as well as support if you get stuck. Let's jump right in!

Get Started    
Ask A Question



No longer receiving logs - System.IO.FileLoadException: Could not load file or assembly 'Serilog.Sinks.File

We are no longer receiving logs on SEQ since last Friday morning. Two changes occurred at that time.... TLS 1.0 was disabled on all servers. ….. (it is now re-enabled on the SEQ server only) Windows updates were run on all servers. …..(all have been removed on the SEQ server only) Full error: App host failed unexpectedly System.IO.FileLoadException: Could not load file or assembly 'Serilog.Sinks.File, Version=, Culture=neutral, PublicKeyToken=24c2f752a8e58a10' or one of its dependencies. The media is write protected. (Exception from HRESULT: 0x80070013) File name: 'Serilog.Sinks.File, Version=, Culture=neutral, PublicKeyToken=24c2f752a8e58a10' at Serilog.Sinks.RollingFile.RollingFileSink.Dispose() at Serilog.LoggerConfiguration.<CreateLogger>b__28_0() at Seq.App.FileArchive.ArchiveWriterReactor.Dispose() at Seq.Apps.GenericHost.Program.<Main>d__0.MoveNext() WRN: Assembly binding logging is turned OFF. To enable assembly bind failure logging, set the registry value [HKLM\Software\Microsoft\Fusion!EnableLog] (DWORD) to 1. Note: There is some performance penalty associated with assembly bind failure logging. To turn this feature off, remove the registry value [HKLM\Software\Microsoft\Fusion!EnableLog]. Do we need TLS 1.0 turned back on for each server from which we are gathering logs? Is there a technical guide to securing the service protocols? Many thanks...we are done.

Posted by Andrea Stub about a year ago