Skip to Main Content
Sage 200 UKI Ideas Portal

Please note the following Sage 200 Ideas Portal Guidelines apply to the use of this portal.

Status Idea Accepted - Gauging Support
Categories Server
Created by Katja Monks
Created on Sep 17, 2026

change Sage log files (in inetpub) to using RollingFileAppender instead of FileAppender

We frequently encounter situations where log files grow to an excessive size over time. While this can be partially managed by reducing the logging level, we are currently investigating whether it would be possible to configure log management using RollingFileAppender rather than FileAppender.
The primary advantage of this approach is that once a log file reaches a predefined size threshold, a new log file would be created automatically. This would allow older log files to be archived and prevent a single log file from continuing to grow indefinitely.
In addition, a retention policy could be implemented to limit the total combined size of all log files. For example, the system could be configured to retain a maximum of 5 GB of log data, ensuring that log growth remains controlled and reducing the risk of available disk space being exhausted.
This is particularly important for hosted and cloud-based environments, where storage allocations are often considerably smaller than those found in on-premises deployments. Introducing rolling log files would provide a more robust and automated mechanism for managing log growth and would help minimise the operational impact of excessive logging.
A further consideration is that not all sites for which we provide Sage support grant our support teams remote access, as their network environments are often managed by third-party IT providers. As a result, we have limited visibility of server resources and log file growth. In many cases, log files can continue to expand unnoticed until disk space becomes critically low or fully exhausted, at which point the issue has already caused operational disruption. Implementing a rolling log strategy with size and retention limits would provide a safeguard against uncontrolled log growth, reducing the risk of storage-related incidents and minimising the reliance on proactive monitoring by customer IT teams.

Idea Benefit reducing risk of disk space becoming critically low or fully exhausted
How do you solve for this problem today? Site where we support networking are monitored for disk file size. Where sites are supported by a third party IT we won't become aware of this until the third party or the customer raises a ticket due to issues with the servers. Resulting in reactive support rather than us being able to deal with this proactively
Product Variant Sage 200 Professional, Sage 200 Professional (SPC)
  • Chris Burke
    Sep 21, 2026

    You don't need Sage to do this for you - you can just go ahead and set it up. Take for example the Self Service site - just edit the web.config file to add a new log appender definition to the <log4net> element, something like this:

    <appender name="RollingFileAppender" type="log4net.Appender.RollingFileAppender">
    <file value="Log\Rolling_Sage200SelfService.log"/>
    <appendToFile value="true" />
    <maximumFileSize value="100MB" />
    <maxSizeRollbackups value="10" />
    <rollingStyle value="Size" />
    <layout type="Sage.Common.Logging.DefaultPatternLayout, Sage.Common">
    </layout>
    </appender>


    ...then tell it to use the RollingFileAppender

    <root>
    <!--Note: to change the level of logging for the FileStorageAppender, this should be done in SAA -->
    <level value="DEBUG"/>
    <appender-ref ref="RollingFileAppender"/>
    </root>


    That's it. I do this all the time on my customer sites.