You can schedule SAS Web Report Studio reports using either Platform Suite for SAS^® or the in-process scheduling server.

This SAS KB article explains how to increase logging for these servers in order to diagnose scheduling problems in SAS Web Report Studio 4.4 and later. You change settings in the Configuration Manager plug-in to SAS^® Management Console and in either the SAS Web Report Studio or the SAS^® BI Report Services log4j file.

Part I: Modify the log4j file

1. The log4j file that you need to modify depends on whether you are using Platform Suite for SAS or the in-process scheduler.
   • For the in-process scheduler, navigate to the following directory on the machine where SAS Web Report Studio is deployed. Make a copy of this file so that you can easily return to normal logging.

/SAS-configuration-directory/Lev1/Web/Common/LogConfig/SASWebReportStudio4.4-log4j.xml

1. • For Platform Suite for SAS, navigate to the following directory on the machine where SAS BI Report Services is deployed. Make a copy of this file so that you can easily return to normal logging.

/SAS-configuration-directory/Lev1/Applications/SASBIReportServices4.x/birepserv_log4j.xml

2. Open the active copy of the log4j file in a plain text editor.

3. The logging contexts depend on which file you are editing.

• • If you are editing the SAS Web Report Studio log4j file, then add the following logging contexts after the last <category> tag and before the <root> tag. Some of these logging contexts might already be in the file with a WARN priority value. If they are, then change the priority value to DEBUG.

    <category additivity="false" name="com.sas.report.render">
        <priority value="DEBUG"/>
        <appender-ref ref="SAS_CONSOLE"/>
        <appender-ref ref="SAS_FILE"/>
    </category>

   <category additivity="false" name="com.sas.apps.citation.model.scheduler">
        <priority value="DEBUG"/>
        <appender-ref ref="SAS_CONSOLE"/>
        <appender-ref ref="SAS_FILE"/>
    </category>
    
    <category additivity="false" name="com.sas.report.output">
        <priority value="DEBUG"/>
        <appender-ref ref="SAS_CONSOLE"/>
        <appender-ref ref="SAS_FILE"/>
    </category>
        
    <category additivity="false" name="com.sas.iquery">
        <priority value="DEBUG"/>
        <appender-ref ref="SAS_CONSOLE"/>
        <appender-ref ref="SAS_FILE"/>
    </category>
        
    <category additivity="false" name="com.sas.report.output.management">
        <priority value="DEBUG"/>
        <appender-ref ref="SAS_CONSOLE"/>
        <appender-ref ref="SAS_FILE"/>
    </category>

    <category additivity="false" name="com.sas.apps.citation.model.scheduler.ScheduleManager">
        <priority value="DEBUG"/>
        <appender-ref ref="SAS_CONSOLE"/>
        <appender-ref ref="SAS_FILE"/>
    </category> 

• If you are editing the SAS BI Report Services log4j file, then add the following logging contexts after the last <logger> tag and before the <root> tag. Some of these logging contexts might already be in the file with a WARN level value. If they are, then change the level value to DEBUG.

  <logger additivity="false" name="com.sas.report.render">
        <level value="DEBUG"/>
        <appender-ref ref="SAS_CONSOLE"/>
        <appender-ref ref="SAS_FILE"/>
    </logger>
    
    <logger additivity="false" name="com.sas.report.output">
        <level value="DEBUG"/>
        <appender-ref ref="SAS_CONSOLE"/>
        <appender-ref ref="SAS_FILE"/>
    </logger>    
    
    <logger additivity="false" name="com.sas.iquery">
        <level value="DEBUG"/>
        <appender-ref ref="SAS_CONSOLE"/>
        <appender-ref ref="SAS_FILE"/>
    </logger>
    
    <logger additivity="false" name="com.sas.report.output.management">
        <level value="DEBUG"/>
        <appender-ref ref="SAS_CONSOLE"/>
        <appender-ref ref="SAS_FILE"/>
    </logger>

4. Save the changes to the file.

Part II: Add properties using the Configuration Manager plug-in

5. Log on to SAS Management Console as an unrestricted user such sasadm@saspw.
6. On the Plug-ins tab, navigate to Application Management ► Configuration Manager ► SAS Application Infrastructure ► Web Report Studio 4.4.
7. Right-click Web Report Studio 4.4 and select Properties.
8. Click the Advanced tab.
9. Click Add.
   • For Property Name, enter wrs.scheduling.verboseScheduleStartup
   • For Property Value, enter true
10. Click OK twice to exit all of the dialog boxes.

Part III: Clear out the existing log

11. Stop your web application server.
12. Delete the existing SAS Web Report Studio log file. The log is typically located in /SAS-configuration-directory/Lev1/Web/Logs/SASServerX_Y. 
13. If you modified the SAS BI Report Services log4j file, then also delete the existing SASBIReportServices4.4.log. This log is typically located in /SAS-configuration-directory/Lev1/Applications/SASBIReportServices4.4/Logs.
14. Restart your web application server.
15. Take the steps to reproduce the issue.
16. Send copies of the SASWebReportStudio.log and the SASBIReportServices4.4.log (if applicable) that capture the issue to SAS Technical Support, along with any other requested information.

Part IV: Turn off additional logging

After you have generated a log that captures information about the problems that you are having, make a backup copy of the modified log4j file. Rename the original file back to its original name, and restart your web application server. You can leave the wrs.scheduling.verboseScheduleStartup set in the Configuration Manager.