Enable debug log (win)

Add the following parameters to SuperOffice.ini:

[Error]
EnableDebug=1
EnableOleDBLog=1 (may be set to a value between 1 and 5)
EnableReporterLog=1
Truncate=0
Logpath=c:\SO_arc\data\SOError.log

EnableOleDBLog supports several levels:

1 = SQL logging only
2 = also report component creation/destruction
3 = report method calls
4 = report sub method calls
5 = report mindnumbing detail

Note: If you enable the comprehensive error logging function, you must remember to disable it afterwards, or the hard disk will fill up. To disable it, enter the following:

[Error]
EnableDebug=0

To also get debug info from NetServer you need to edit SuperOffice.config

This will generate a logfile with <todaysdate>.log in the folder you specify in the LogFolder key

<SuperOffice>
<Diagnostics>
<!-- Log errors (default 'True'). -->
<add key="LogError" value="True">
</add>
<!-- Log warnings (default 'False') -->
<add key="LogWarning" value="False">
</add>
<!-- Log general information. This includes successful SQL's passed to the database.
Only permit this option while debugging a bug. This will be a severe performance hit!
(default 'False') -->
<add key="LogInformation" value="False">
</add>
<!-- Log failed authentications (default 'True') -->
<add key="LogFailureAudit" value="True">
</add>
<!-- Log sucessfull authentications (default 'False') -->
<add key="LogSuccessAudit" value="False">
</add>
<!-- Log to the OS event log (default 'True') -->
<add key="LogToEventLog" value="False">
</add>
<!-- Log to SuperOffice Research and Product Development (Online through a WebService) (default 'False') -->
<add key="LogToSuperOffice" value="False">
</add>
<!-- Log to a LogFile (default 'False') -->
<add key="LogToFile" value="True">
</add>
<!-- Folder (e.g. UNC path) where the logfile is to recide. Note that the owner of the process needs to have access to manipulate files in this folder -->
<add key="LogFolder" value="%localappdata%\SuperOffice">
</add>
</Diagnostics>