/
Accessing the Debug Log
Accessing the Debug Log
The FuseIT SFDC Explorer uses log4net internally to capture log events. These can be useful in tracking what the tool is doing at any point in time.
In the .config file a log4net section defines the level of logging and where it is persisted.
Config
<configSections> <!-- ... --> <section name="log4net" type="log4net.Config.Log4NetConfigurationSectionHandler, log4net" /> <!-- ... --> </configSections>
The default configuration with a new installation is to keep a rolling log file. You may need to adjust the default priority setting under the root element to DEBUG to see all the possible log messages.
log4Net configuration
<log4net> <appender name="RollingLogFileAppender" type="log4net.Appender.RollingFileAppender"> <file value="log.txt"/> <appendToFile value="true"/> <rollingStyle value="Composite"/> <datePattern value="yyyyMMdd"/> <maxSizeRollBackups value="10"/> <maximumFileSize value="1MB"/> <layout type="log4net.Layout.PatternLayout"> <conversionPattern value="%date [%thread] %-5level %logger [%property{NDC}] - %message%newline"/> </layout> </appender> <root> <!-- Use ALL, DEBUG, INFO, WARN, ERROR, FATAL or OFF --> <priority value="INFO"/> <appender-ref ref="RollingLogFileAppender"/> </root> </log4net>
The executable will need permission to write to the file path defined in the appender. You may need to adjust the file path the the logger is writing to or grant the required permissions to the working folder.
, multiple selections available,
Related content
Logging
Logging
More like this
Application log
Application log
More like this
Testing a new or updated installation
Testing a new or updated installation
More like this
Critical update: Salesforce Upgrade to TLS 1.2
Critical update: Salesforce Upgrade to TLS 1.2
More like this
General Settings
General Settings
More like this
FuseIT SFDC Data Exporter
FuseIT SFDC Data Exporter
More like this