Increase the Logging level in SAS® Financial Management 5.62


When unexpected behavior or an exception that necessitates in-depth analysis occurs, you are typically required to increase the logging level either on the server side or the client side. This SAS KB article explains how to increase the logging level for SAS Financial Management 5.62. 

Table of Contents

Increase the Logging Level on the SERVER Side 

There are two methods available for enabling debugging, and it is essential to understand the distinctions between them: 

Typically, in production environments, SAS recommends that you use the first method to minimize the impact for the end-users. 

SAS Web Administration Console Method 

  1. Open a browser and enter the following URL: http://ServerName:port/SASAdmin. Log on as sasadm@saspw. 
  2. In the left pane, select Application Management ► Financial Mgmt 5.62 ► Logging.
    In the left pane, Application Management ► Financial Mgmt 5.62 ► Logging
  3. In the table in the right pane, do as follows:
    • If the Context column contains the logger that you want to modify (that is, com.sas.solutions.finance), select the desired crossing: the logger as row, and the debug level as column.  
    • If the logger is not in the Context list, you can enter a new logger in the Enter new logging context: field. Then, adjust the associated level using the drop-down list. 
  4. To activate the new debug level, click the Set Options button. 
    Click the "Set Options" button in the right pane

Log4j Method 

  1. On the middle-tier server, move the <SASConfig>\Lev1\Web\Common\LogConfig path and back up the original files.
    • SASFinance-log4j.xml
    • SASFMSFormMgr-log4j.xml
    • SASODCS-log4j.xml
      Note: The SASFMSFormMgr-log4j.xml file generates more details about the SAS Financial Management Web Application.  
  2. If the logger exists and you need to update the logging level, change the logging level from WARN to DEBUG. 
    The logging level changed from WARN to DEBUG
  3. If the logger does not exist, add the logger directly to the file by copy and pasting from a similar entry. Make the necessary changes, or use the following strings:  

    <Logger name="com.sas.solutions.finance" level="DEBUG" additivity="false"> 
    <AppenderRef ref="SAS_CONSOLE" /> 
    <AppenderRef ref="SAS_FILE" />         
    </Logger> 

  4. To activate the change, you must restart SASServer3 and SASServer4. Note that the SASServer starting process completes when you find the startup in string for the actual date and time in the server.log (for Windows) and in catalina.out (for Unix). 

Note: The previous SAS® Financial Management 5.x versions use a different syntax in Log4j XML files. For more information, see SAS Note 19864, “Instructions for increasing the SAS® Financial Management logging level.”

Increase the Logging Level at the CLIENT Side 

For the SAS® Financial Management Microsoft Excel Add-in, complete the instructions in SAS Note 46178, “Generating the SAS® Add-In for Microsoft Office log with SAS® Financial Management release 5.3 and later.” Do not forget to change the Debug Level to 3. 

For SAS® Financial Management Studio, complete the following steps: 

  1. Create a backup copy of the <SASHome>\SASFinancialManagementStudio\5.62\log4j2.properties file. 
  2. Open the file and change the rootLogger.level = debug option, as shown in the image below: 
    Change the rootLogger.level = debug option.
  3. Save and close the file. 

Then, you can open SAS® Financial Management Studio and reproduce the issue. After reproducing the issue, additional DEBUG information is located in the log, which is generated in C:\Users\<user>\SAS\FinancialManagementStudio\5.62. (Note that this is the default path.)