Problem Note 69335: The Platform Web Services web application log is not created when the SAS® Grid Manager web application loads first
 |  |  |  |
Under normal operations, the log file PlatformWebServices.log is created in the path SAS-Configuration-directory/Lev/Web/Logs/SASServer14_1 when the web application server starts.
Most commonly, this log file is not created under the following conditions:
- The Platform Web Services application fails to start (check server.log for errors).
- The GUI_LOGDIR environment variable is not set and exported in setenv.sh (see SAS Note 68189, "The PlatformWebServices.log file is not populated in the correct location" )
If these two issues have been ruled out, another possible cause is that the SAS Grid Manager application is loading before Platform Web Services, which can trigger a failure in the logging function used by Platform Web Services.
The start-up order can be confirmed in the file SAS-Configuration-directory/Lev/Web/SASServer14_1/logs/server.log. If the /PlatformWebServices lines appear after the /SASGridManager lines, but no errors are present and the Platform Web Services log file is not being created, perform the following steps:
- Stop the web application server using the command, SAS-Configuration-directory/Levn/Web/SASServer14_1/bin/tcruntime-ctl.ext stop, where ext is the extension appropriate for your environment.
- Move these files out of the path SAS-Configuration-directory/Levn/Web/SASServer14_1/conf/Catalina/localhost
- PlatformWebServices.xml
- SASGridManager.xml
- Move the files back in to that path, being sure to move in the PlatformWebServices.xml file first.
- Start the web application server using the following command: SAS-Configuration-directory/Levn/Web/SASServer14_1/bin/tcruntime-ctl.ext start
- Confirm in the server.log file the Platform Web Services application is starting before SAS Grid Manager, and that the PlatformWebServices.log file is created in SAS-Configuration-directory/Lev/Web/Logs/SASServer14_1/.
If, after you perform the actions above, Platform Web Services is still not starting before SAS Grid Manager, perform the following steps:
- Stop the web application server using the command, SAS-Configuration-directory/Levn/Web/SASServer14_1/bin/tcruntime-ctl.ext stop, where ext is the extension appropriate for your environment.
- Rename the file SAS-Configuration-directory/Levn/Web/SASServer14_1/conf/Catalina/localhost/PlatformWebServices.xml to PlatformWebServices.xml.orig.
- Copy the contents of PlatformWebServices.xml.orig between the <Context...> and </Context> tags.
- Make a back-up copy of the SAS-Configuration-directory/Levn/Web/SASServer14_1/conf/server.xml file.
- Within the <Host...> </Host> tags in server.xml, add the <Context...></Context> segment from PlatformWebServices.xml.orig.
- Take a backup of this new server.xml file.
- Start the web application server using the following command: SAS-Configuration-directory/Levn/Web/SASServer14_1/bin/tcruntime-ctl.ext start
- Confirm in the server.log file that the Platform Web Services application is starting before SAS Grid Manager, and that the PlatformWebServices.log file is created in the SAS-Configuration-directory/Lev/Web/Logs/SASServer14_1/ directory.
These changes might need to be repeated following any updates to SASServer14 that modify the server.xml file.
Operating System and Release Information
| Product Family | Product | System | Product Release | SAS Release | ||
| Reported | Fixed* | Reported | Fixed* | |||
| SAS System | Platform Web Services for SAS | Microsoft® Windows® for x64 | 1.7 | 9.4 TS1M7 | ||
| 64-bit Enabled AIX | 1.7 | 9.4 TS1M7 | ||||
| 64-bit Enabled Solaris | 1.7 | 9.4 TS1M7 | ||||
| HP-UX IPF | 1.7 | 9.4 TS1M7 | ||||
| Linux for x64 | 1.7 | 9.4 TS1M7 | ||||
| Solaris for x64 | 1.7 | 9.4 TS1M7 | ||||
| Type: | Problem Note |
| Priority: | high |
| Date Modified: | 2022-06-24 13:54:04 |
| Date Created: | 2022-06-23 15:26:08 |