Coming soon: Your brand new Help Center & Community! Get a sneak-peek here

Customer Service log files

In this article

    Logfiles from Customer Service is stored in C:\SuperOffice\Customer Service\log unless you have installed it to a different path.

    You may also view the warning log in your browser by by adding the action "dumpWarningLog" with a "date" parameter to your rms.exe/rms.fcgi. This will require sufficient rights in Customer Service.

    This only works on rms.exe/rms.fcgi and the date format you have to use is as follows: yyyy-mm-dd.

    Example: http://<your website>/scripts/rms.exe?action=dumpWarningLog&date=2013-03-05

    In addition to the logfiles generated by Customer Service, we also log information from SuperOffice NetServer, you may find the location of your NetServer installation by opening the config file stored in C:\SuperOffice\Customer Service and looking at the value after nsEndPoint:
     nsEndPoint = http://localhost/SuperOfficeNS/Services80

    Customer Service may have been installed with the remote webservices, but it will have a SuperOffice Product Configurator similar to SuperOffice Web. With this Product configurator you can enable debug logging under Diagnostics, see more info below


    SuperOffice Product Configurator

    Turn on or off debug logging

    To turn on or off debug logging for SuperOffice Web, go to Start - Programs - SuperOffice - SuperOffice 7 web - Product Configuration - SuperOffice Web



    7.web always takes a long time to start up initially because IIS needs to initiate both the .NET common language runtime and NetServer. As soon as the w3wp.exe IIS work process is up and running you'll see that the performance is way better. We do however also have some online services configurable in the web.config file. If you experience poor performance on the second login you may turn off two online checks:

    1) Logging to SuperOffice Research & Product Developement

    Go to Diagnostics and turn off Log to SuperOffice Research & Product Developement.


    2) Browser version check

    7.web also does a browser check when users connect. Because browsers update frequently, we need a way to verify that the new browser version works with 7.web. We have a central database of working browsers that we update as soon as new browser versions show up. If the browser is not supported, we can send back a suitable error message. If the central site is not available, or if the option is deactivated in the config file, then the browser check is not made. You may turn off this check in the web.config file as well.

    1. Open Web.config
    2. Find <Diagnostics> section
    3. Add this parameter: <add key="CheckBrowserVersion" value="false" />

    3) Disable PublisherEvidence for .Net Framework

    When you start a Microsoft .NET Framework 2.0 managed application that has a Microsoft Authenticode signature, the .NET Framework 2.0 managed application takes longer than usual to start.

    Add the following line to aspnet.config found on the webserver C:\Windows\Microsoft.NET\Framework64\v2.0.50727\aspnet.config and C:\Windows\Microsoft.NET\Framework\v2.0.50727\aspnet.config

    Add the generatePublisherEvidence line to the config file:

    		<generatePublisherEvidence enabled="false"/>


    Mail logging

    If you have issues with emails sent via Netserver turn on Log email. This is not a debug logging for Mail link.