Debug Win client

In this article

    Add the following parameters to SuperOffice.ini:

    [Error]
    EnableDebug=1
    EnableOleDBLog=0
    EnableReporterLog=1
    Truncate=0
    Logpath=c:\SO_arc\data\SOError.log

    Most parameters is either on = 1 or off = 0, but 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

    The OleDBLog is only useful if you are troubleshooting anything which use our OleDBProvider, like reports.

    Logpath - make sure the path is accessible for the client you want to make the logfile for. For debugging it is most useful if this location is only used for the client with problems, so a local folder where the user have write permission is ideal.

    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, set EnableDebug=0

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

    Since the windows client use both old components and NetServer, you also need to enable debugging in the SuperOffice.config file for support to be able to trace what happens. This is done by making sure the key LogError is set to True in the section Diagnostics and also make sure it writes to a file by setting LogToFile to True. Default the LogFolder is set to %Localappdata%\SuperOffice, but you may change this to the same location as the above Logfolder in SuperOffice.ini. Note - the client needs write permission to this folder. Without write permission to this folder, Netserver will write the logfile to the same location it was started from.

    See Netserver Diagnostics below.

    Netserver diagnostics

    <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="C:\Log">
    </add>
    </Diagnostics>

    When you use SuperOffice Win the Scaffolding option is not in SuperOffice.config file at all. If asked for even more extended logging you may turn this on by adding the 
    <add key="EnableScaffolding" value="true" /> 
    key

    See also Diagnostics section of the Web.config page.

    Note: do remember to turn the logging off when it is not needed, as extended logging in Netserver will reduce performance.