Sage 200 - Troubleshooting log files

Sage 200 Standard / Education Online:

Sage 200 Desktop log file

To find the installation of the application and the StandardDesktop.exe.config file location you can get this by opening regedit. Once open if you browse to the following location:
HKEY_CURRENT_USER > Software > Sage > MMS

In this location, you will see an entry for 'ClientInstallationLocation' if you double click on this and copy the value. You can then paste this into the address bar of Windows Explorer.

Increase Logging

In the application location, you will find a file called StandardDesktop.exe.config. Open this file using notepad. In this file, you need to amend the following section to increase logging:

<log4net>
  <root>
    <level value="ERROR" />
     <appender-ref ref="FileAppender">
     <!--<appender-ref ref="TraceAppender"/> -->
     <!--<appender-ref ref="DebugAppender"/> -->
 </root>

Change the word "Error" to "Debug" on the third line and save the file. Do not forget to change this back once done or the log file will continually grow and quite quickly become to large.

Viewing the log File

The log file itself is in a different location:

Browse to C:\Users\(username)\AppData\Local\Sage\Sage200 and open the file Sage200Desktop.log.

NOTE: In case you cannot find the location of the log file the StandardDesktop.exe.config specifies where the log file will be alongside file value =:

<appender name="FileAppender" type="log4net.Appender.FileAppender">
 <file value="${LOCALAPPDATA}\Sage\Sage200\Sage200Desktop.log" />
 <appendToFile value="true"/>

Sage 200 Professional

Sage 200 Desktop log file

To find the installation of the application and the Sage200Desktop.exe.config file location you can get this by opening regedit. Once open if you browse to the following location:
HKEY_CURRENT_USER > Software > Sage > MMS

In this location, you will see an entry for ‘ClientInstallationLocation’ if you open this up and copy the value. You can then paste this into the address bar of windows explorer.

Increase Logging

In the application location, you will find a file called Sage200Desktop.exe.config. Open this file using notepad. In this file, you need to amend the following section to increase logging:

<log4net>
 <root>
  <level value="ERROR" />
   <appender-ref ref="FileAppender">
   <!--<appender-ref ref="TraceAppender"/> -->
   <!--<appender-ref ref="DebugAppender"/> -->
 </root>

Change the word "Error" to "Debug" on the third line and save the file. Do not forget to change this back once done or the log file will continually grow and quite quickly become to large.

Viewing the log File

The log file itself is in a different location:

Browse to C:\Users\(username)\AppData\Local\Sage\Sage200 and open the file Sage200Desktop.log.

NOTE: In case you cannot find the location of the log file the Sage200Desktop.exe.config specifies where the log file will be alongside file value =:

<appender name="FileAppender" type="log4net.Appender.FileAppender">
 <file value="${LOCALAPPDATA}\Sage\Sage200\Sage200Desktop.log" />
 <appendToFile value="true"/> 

Sage 200 Professional API

The API log file is stored in C:\Inetpub\Sage 200 App Services\Sage200NativeAPI\Log.

By default, the logging for Sage 200 Professional API is set to DEBUG. You can change the settings my amending Web.Config files stored in C:\Inetpub\Sage 200 App Services\Sage200NativeAPI.

Open this file using notepad. In this file, you need to amend the following section to change logging:

<log4net>
 <root>
  <level value="DEBUG" />
   <appender-ref ref="FileAppender">
  </root>

Change the work "DEBUG" to "ERROR" and save the file.

Self Service and Secured Service log files

Increase Logging

• Open System Administration
• Click on the Logging option on the left-hand side and change the level of logging to Debug

Viewing the Log File

There are three log files available for 2013 and above which can be found in the following locations:

• C:\inetpub\Sage 200 App Services\Sage200SecuredServices\Log
• C:\inetpub\Sage 200 App Services\Sage200Services\Log
• C:\inetpub\Sage 200 Self Service\Sage200SelfService\Log

Understanding the Sage 200 Logging Levels

The logging levels in Sage 200 web services are controlled by two factors, in this order.

• The level in the web.config file
• The level set in the system administration (SAA) tool

The setting in the System Administrator (SAA) tool is cached and will take a minute of so to affect the active logging levels.

When the service starts up it will read the logging level from the web.config file so will start logging in debug mode. After about a minute it will look to the level set in the system administrator (SAA) tool and change the logging level to the appropriate mode.

Also when changing the logging level in the System Administrator (SAA) tool you may have to wait a minute or so for it to become effective.

Upgrading your licence

Need a little more room? To add extra companies, users, employees or more to your software licence, leave your details and we'll be in touch.

Leave your details