Logging settings in web config/app config still relevant?

lock
push_pin
done
Answered
4

Hi,

Tony announced here that there where logging changes in NetServer 10.2.1 release, now with the latest release of SuperOffice OnSite 10.2.1, I see warning logs generated:

 

Warning      2023-02-03T09:02:50.36    SuperOffice.CRM.ArchiveLists.QueryProviderBase          No restrictions match, and getAllRows not specified in   DH (1993) - Authorized (Employee)Gebruikersniveau 0: Beheerder: heeft volledige toegang tot alle gegevens. Kan alle inhoud in het systeem beheren. MSSQL - 12 \\xx\xx (xx), Database serial #: xx, Database Expiration Date: dinsdag 13 juni 2023 xx xx xx SuperOffice 10.2.1 NetServer 10.2 Release (Build: Release_OnSite_10.2.1_2023.01.31-02) 10.2.0.0 10.2.1.1698 Release_OnSite_10.2.1_2023.01.31-02 Default xx NetServer      

Warning      2023-02-03T09:02:50.36    SuperOffice.CRM.ArchiveLists.QueryProviderBase          No restrictions match, and getAllRows not specified in   DH (1993) - Authorized (Employee)Gebruikersniveau 0: Beheerder: heeft volledige toegang tot alle gegevens. Kan alle inhoud in het systeem beheren. MSSQL - 12 \\xx\xx (crm_AllCRM), Database serial #: xx, Database Expiration Date: dinsdag 13 juni 2023 xx xx xx SuperOffice 10.2.1 NetServer 10.2 Release (Build: Release_OnSite_10.2.1_2023.01.31-02) 10.2.0.0 10.2.1.1698 Release_OnSite_10.2.1_

But warning logs are disabled in the web config:

The BatchService is also constantly logging the following line, while information log is disabled (in the SoBatchService.exe.config):

Information 2023-02-03T10:04:20.90 SuperOffice.CRM.BatchService.BatchServiceProcessor  SuperOffice Batch Service Service Found 0 task(s) to run. xxx (1957) - Authorized (System)Systeemgebruiker: Systeemintegratiegebruiker. Omzeilt alle beveiligingscontroles. MSSQL - 14 \\xx\xx (crm_allcrmtest), Database serial #: xx, Database Expiration Date: Tuesday, June 13, 2023 xx xx xx SuperOffice 10.2.1 NetServer 10.2 Release (Build: Release_OnSite_10.2.1_2023.01.31-02) 10.2.0.0 10.2.1.1698 Release_OnSite_10.2.1_2023.01.31-02 Default xx file:///D:/SuperOffice/SuperOffice Web/xx/bin/BatchService/SoBatchService.exe NetServer 

 

Are these logging settings in the relevant web config/app config file still doing anything?

 

3 Feb 2023 | 09:08 AM

All Replies (4)

Hi David, 

No. The log level is controlled via the appSettings.json file. All other Diagnostics settings are the same, such as: 

ConfigFile.Diagnostics.LogToFile = false
ConfigFile.Diagnostics.LogFolder = "C:\temp\"
ConfigFile.Diagnostics.EnableScaffolding = false
...
 
 
Best regards
3 Feb 2023 | 10:12 AM
I see a appsettings.json file in the root folder, with "SuperOffice" on level 'Warning', so that explains that. No appsettings.json exists in the batch service folder (bin\BatchService). I copied it to there and that solves the information level logging.
3 Feb 2023 | 10:18 AM
Maybe it would be an idea to remove the log level settings from the config file on update, (using soappconfig), since these are obsolete now.
3 Feb 2023 | 10:20 AM

Logged as Bug 38925, to fix the configuration and tooling.

3 Feb 2023 | 11:56 AM

Good evening! Interesting post
That answer my question I was just about to put together regarding sobatch service constantly logging even though LogInforamtion="false"
I solved by setting log-path in SoBatchService.exe.config and also after a while turning it of by setting LogToFile = "false"
For me it actually logged 3 long rows every time.
Around 50 MB of data every day (it logs every 2 second because that is default config for often it should run)
Will try to implement your fix David to get logging back.


The second question I had though is if it is by desgin or not: 

  1. The second strange thing (maybe it always has been like that) is that if I change a value in the SoBatchService.exe.config the whole SuperOffice CRM Sales application dies. (and restarts)
    1. I guess i feels the config change ? Or is this a bug?
    2. At least seting LogToFile = "False" seems to help

I am with David => Remove obsoete tings in the config-files.

Another anoying thing that finally may be solved is: (It has always been set to true before)

      <!-- Log to SuperOffice Research and Product Development (Online through a WebService) (default 'False') -->

      <add key="LogToSuperOffice" value="False" />

The last thing:
When upgrading superOffice CRM Sales and if we have created our own AppPools for some reason , it always defaults back to "SuperOffice" 
Make the installer check what appPool is used for Sales application and or netserver installations.
Ther Serive installer does not change appPools when upgrading.

//Anders

9 May 2023 | 07:10 PM
The application pools reloads because the batch service and it's config files are located in the bin folder, changes within that bin folder always cause a application pool to restart, that is normal behavior.
10 May 2023 | 08:22 AM

Add reply