This article explains how to enable different debugging options that can be used for troubleshooting SAS Enterprise Miner issues. These instructions apply to the SAS Enterprise Miner Client and SAS Enterprise Miner Server versions released on SAS^® 9.3 and SAS^® 9.4.

Client Debugging

• If you are launching the SAS Enterprise Miner Client from Start Programs ► SAS, complete the following steps to enable logging:

  1. Back up the existing log4j.properties file if it exists in the \SASHome\SASEnterpriseMinerClient\version directory. Replace the file with the debug log4j.properties file that is contained in the attached log4j.zip file. Unzip the file to retrieve the log4j.properties file.
  2. Locate the em.ini file in the \SASHome\SASEnterpriseMinerClient\version directory.
  3. Right-click the em.ini file and select Open With ► WordPad.

  4. Modify the value of the APPLOGLOC parameter in that file. Specify the following setting:
     applogloc=em.log

  5. Save the em.ini file.
  6. Launch SAS Enterprise Miner, and re-create the issue. The em.log file is created in the \SASHome\SASEnterpriseMinerClient\version directory.
  7. When using SAS^® Enterprise Miner^™ Client 14.1, you can send the em_date-timestamp.log file for the time of test. The em_date-timestamp file is created by default under C:\Users\userid\AppData\Local\SAS\SASDeploymentWizard. Note that AppData is a hidden folder, so you need to change Folder view settings to show hidden files.
• If you are launching the SAS Enterprise Miner Client using Java Web Start, enable Java console logging. See SAS KB0036243 "How to enable logging when SAS^® Enterprise Miner™ is launched from Java Web Start (JWS)."

Middle tier Debugging

Complete the following instructions when SAS Technical Support requests that you enable SAS Enterprise Miner middle tier debugging.

1. Log on to the middle tier machine using a SAS Administrator account.
2. Stop the SAS Web Application Server instance where SAS Enterprise Miner is deployed. Typically, this server is SASServer11_1 or SASServer1_1.
3. In the /SASConfig/Lev#/Web/Common/LogConfig directory, create a backup of the SASEnterpriseMiner-log4j.xml file.

4. Edit the SASEnterpriseMiner-log4j.xml file by modifying the following loggers. Change the priority value from WARN to DEBUG:

   <category additivity="false" name="com.sas.analytics.eminer" > <priority value="WARN"/> <category additivity="false" name="com.sas.analytics.eminer" > <priority value="DEBUG"/>

   <category additivity="false" name="com.sas.analytics.eminer.midtier" > <priority value="WARN"/> <category additivity="false" name="com.sas.analytics.eminer.midtier" > <priority value="DEBUG"/>

    
5. Save the SASEnterpriseMiner-log4j.xml file.
6. Start the SAS Web Application Server instance (SASServerX_Y). Typically, SASServerX_Y is SASServer11_1 or SASServer1_1 where SAS Enterprise Miner is deployed.

7. After recreating the problem, send the following log files:

   • SASEnterpriseMiner.log from the /SASConfig/Lev#/Web/Logs/SASServerX_Y directory.
   • server.log from the /SASConfig/Lev#/Web/WebAppServer/SASServerX_Y/logs directory

Beginning with SAS Enterprise Miner 14.1, you can enable dynamic middle tier debugging. See SAS Note 57104, "Enabling dynamic logging in SAS^® Enterprise Miner™ without requiring a middle-tier restart."