The troubleshooting tips in this note should help if you encounter problems when you run SAS^® Stored Processes on the SAS^® Stored Process Server using the SAS Stored Process Web Application.

1. Specify the &_debug=trace option in the URL when you submit the request. This specification provides a trace of the execution in your web browser, as shown below.
   
   http://your-server.com:8080/SASStoredProcess/do?_program= %2FSamples%2FStored+Processes%2FSample%3A+Hello+World&_debug=trace
2. Alternatively, you can specify the &_debug=trace,time,log option in the URL when you submit the request. In addition to providing an execution trace, it also indicates the execution time that is required for each step.
3. The stored-process server creates log files in a location that is similar to the following:
   .../Lev1/SASMain/StoredProcessServer/logs/

Different releases of the SAS^®9 Stored Process Web Application create a log file on the middle-tier server at a different location and increasing debugging information is done differently. See the appropriate SAS release levels below for further information about the SAS Stored Process Web Application log files.

SAS^® 9.13 Notes

In SAS 9.13, the SAS Stored Process Web Application creates a log file on the middle-tier server in the following location:

If necessary, you can produce more detailed logging information in the stp.log file about the execution of the SASStoredProcess servlet (which runs on your middle-tier web server) by using the following approach.

1. Make a backup copy of the logging_config_stp.xml file. This file should be located on your web-server machine at a path that is similar to the following:
   .../Lev1/web/Deployments/Portal/logging_config_stp.xml
2. Modify the logging_config_stp.xml file, as follows.
   
   • Change the RootLoggingContext priority from WARN to DEBUG.
   • Change the com.sas.services.storedprocess priority from WARN to DEBUG.
3. Restart SAS Remote Services and your servlet container (or example, your Tomcat server) to activate the changes.
4. Submit a stored-process request from the web interface, as shown in the example below:
   
   http://your-server.com:8080/SASStoredProcess/do?_program= %2FSamples%2FStored+Processes%2FSample%3A+Hello+World&_debug=trace,time,log
5. After you complete this test, you should restore the original settings in your logging_config_stp.xml file. You need to restore the settings because using the DEBUG option results in slower performance.
6. Restart SAS Remote Services and your servlet container (for example, your Apache Tomcat server) to activate the changes.

SAS^® 9.2 Notes

In SAS 9.2, the sAS Stored Process Web Application creates a log file on the middle-tier server in the following location:

If necessary, you can produce more detailed logging information in the SASStoredProcess9.2.log file about the execution of the SASStoredProcess servlet (which runs on your middle-tier web server) by using the following approach.

1. Log on to SAS^® Management Console.
2. On the Plug-ins tab, select Environment Management ► Foundation Services Manager ► SASStoredProcess9.2.Local.Services ► Core ► Logging Service.
3. Right-click Logging Service and select Properties. The Logging Service Properties dialog box appears.
4. Click the Service Configuration tab and then click Configuration. The Logging Service Configuration dialog box appears for the application.
5. On the Contexts tab, click New to open the New Logging Service Context dialog box.
6. For Name specify com.sas.services.storedprocess.
7. For Outputs, select SAS_LS_CONSOLE and SAS_LS_FILE.
8. For Priority, select DEBUG.
9. Click OK to exit from each window.
10. To enforce the changes that you have made, restart the SAS web application.
11. After you complete this test, you should set the priority to WARN for com.sas.services.storedprocess. You need to do this because the DEBUG priority result in slower performance.

For more information, see Administering Logging for SAS Web Applications.

SAS^® 9.3 Notes

In SAS 9.3, the SAS Stored Process Web Application creates a log file on the middle-tier server in the following location:

If necessary, you can produce more detailed logging information in the SASStoredProcess9.3.log file about the execution of the SASStoredProcess servlet by using the following approach.

1. Make a backup copy of the SASStoredProcess-log4j.xml file. This file is located on your web-server machine in a path that is similar to the following:
   
   .../Lev1/Web/Common/LogConfig/SASStoredProcess-log4j.xml
2. Modify the SASStoredProcess-log4j.xml file by changing the com.sas.services priority from WARN to DEBUG
3. Restart the SAS Web Application Server to activate the changes.
4. Submit a stored-process request from the SAS Stored Process Web Application interface, as shown below.
   
   http://your-server.com:8080/SASStoredProcess/do?_program= %2FSamples%2FStored+Processes%2FSample%3A+Hello+World&_debug=trace,time,log
5. After you complete this test, you should restore the original settings in your SASStoredProcess-log4j.xml file because the DEBUG priority results in slower performance.

Additional SAS^® 9.3 Note

The following approach can be used to produce some additional logging without having much impact on performance

.

This approach produces additional logging about the names of stored processes that were executed, the users who submitted the requests and the beginning and ending execution times of each request.

1. Modify the SASStoredProcess-log4j.xml file by changing the com.sas.services.storedprocess.webapp logger priority from WARN to INFO.
2. Restart the Web Application Server to activate the changes.

For more troubleshooting ideas, see SAS Notes 12571 , 14764 , 17604, and 17336

Operating System and Release Information

Product Family	Product	System	SAS Release
			Reported	Fixed*
SAS System	SAS Integration Technologies	Microsoft Windows XP Professional	9.1 TS1M3 SP3
		Microsoft Windows XP 64-bit Edition	9.1 TS1M3 SP3
		Microsoft Windows NT Workstation	9.1 TS1M3 SP3
		Microsoft® Windows® for 64-Bit Itanium-based Systems	9.1 TS1M3 SP3
		Microsoft Windows Server 2003 Enterprise Edition	9.1 TS1M3 SP3
		Microsoft Windows Server 2003 Standard Edition	9.1 TS1M3 SP3
		Microsoft Windows 2000 Server	9.1 TS1M3 SP3
		Microsoft Windows Server 2003 Datacenter Edition	9.1 TS1M3 SP3
		Microsoft Windows 2000 Professional	9.1 TS1M3 SP3
		Microsoft Windows 2000 Datacenter Server	9.1 TS1M3 SP3
		Microsoft Windows 2000 Advanced Server	9.1 TS1M3 SP3
		64-bit Enabled HP-UX	9.1 TS1M3 SP3
		HP-UX IPF	9.1 TS1M3 SP3
		Linux on Itanium	9.1 TS1M3 SP3
		Linux	9.1 TS1M3 SP3
		64-bit Enabled Solaris	9.1 TS1M3 SP3
		OpenVMS Alpha	9.1 TS1M3 SP3
		64-bit Enabled AIX	9.1 TS1M3 SP3
		Tru64 UNIX	9.1 TS1M3 SP3

* For software releases that are not yet generally available, the Fixed Release is the software release in which the problem is planned to be fixed.

---

When you run SAS® Stored Processes on the SAS® Stored Process Server using the Stored Process Web Application and you encounter problems, these troubleshooting tips should help.

Type:	Usage Note
Priority:
Topic:	System Administration ==> Servers ==> Integration Technologies

Date Modified:	2012-06-01 13:13:47
Date Created:	2006-08-02 17:38:43