Usage Note 23249: My remote method call is failing. How can I see what's happening on the server?
You can trap the SAS server log to the webAF messages window by modifying the connection object that you use to communicate with the remote server. To do this, invoke the customizer on the connection object and select the Debug tab. Then, check the Route SAS server log to client system.out option. When you run your application using this setting, all of the SAS server log information will be displayed in the webAF messages window.
You can also enable various other debug tracing features from this customizer, but make sure to disable these debug features in your production application. The extra debugging data that is sent across the wire slows your application down somewhat.
If you see errors in the server-side trace and are still unable to determine the cause of the problem, report the problem to SAS Technical Support.
Operating System and Release Information
SAS System | SAS AppDev Studio | Microsoft Windows 95/98 | 1.2 | 3.1.4 | 8.1 TS1M0 | |
Microsoft Windows 2000 Advanced Server | 1.2 | 3.1.4 | 8.1 TS1M0 | 9.1 TS1M3 SP2 |
Microsoft Windows 2000 Datacenter Server | 1.2 | 3.1.4 | 8.1 TS1M0 | 9.1 TS1M3 SP2 |
Microsoft Windows 2000 Server | 1.2 | 3.1.4 | 8.1 TS1M0 | 9.1 TS1M3 SP2 |
Microsoft Windows 2000 Professional | 1.2 | 3.1.4 | 8.1 TS1M0 | 9.1 TS1M3 SP2 |
Microsoft Windows NT Workstation | 1.2 | 3.1.4 | 8.1 TS1M0 | 9.1 TS1M3 SP2 |
Microsoft Windows XP Professional | 1.2 | 3.1.4 | 8.1 TS1M0 | 9.1 TS1M3 SP2 |
Windows Millennium Edition (Me) | 1.2 | 3.1.4 | 8.1 TS1M0 | |
*
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.
Type: | Usage Note |
Priority: | low |
Topic: | Software Components ==> webAF
|
Date Modified: | 2007-10-10 12:14:18 |
Date Created: | 2003-05-05 13:04:50 |