Steps to check REN Server failure
The REN Server is a Real Time Event Notification system that allows reports to be printed to a separate browser window.
If you are getting “Communication with REN Server failed (HTTP 403 Forbidden) ” error message, when trying to open a report to a separate browser window or trying to ping the REN server, then follow the following steps suggested by PeopleSoft for checking REN server.
Case # 1:
Make sure that you have the proper REN server permissions configured.
Make sure that you have the proper REN server permissions configured.
Navigate to PeopleTools > Security > Permissions and Roles > Permission Lists. Select the primary permission list that is tied to the user profile that you are testing with. You will also have to grant permissions to the USER ID that is configured for your Process Scheduler database signon settings, if that user is different than the one that you are currently logged in as. Once the permission list is up, go to the PeopleTools tab. Click on the “Realtime Event Notification Permissions” link in the middle of the page. On the next page, make sure that the access code for Reporting Window is set to full access.
Next, go to the Web Libraries tab. Make sure that there is an entry for WEBLIB_RPT. If it is not there, then please add the library in. Once that is added, click on the edit link and make sure that the access permissions are set to full access.
Make sure to save the changes before exiting.
Next, navigate to PeopleTools > Portal > Node Definitions and click search to bring up all of your nodes. Sort so that your default local node is listed at the top. Click on the name link for the default local node and make sure that the Authentication Option is set to password and that a password has been entered.
Finally, navigate to PeopleTools > Security > Security Objects > Single Signon. Make sure that your default local node is listed there.
Case #2
If using an authentication domain, make sure that the REN server configuration is specifying the domain:
-Navigate to PeopleTools -> REN Server Configuration -> REN Server Cluster
-Select your REN Server Cluster
-Verify ‘Authentication Domain’ has been specified
-Verify that the domain is specified in the ‘REN Server Browser URL’
If using an authentication domain, make sure that the REN server configuration is specifying the domain:
-Navigate to PeopleTools -> REN Server Configuration -> REN Server Cluster
-Select your REN Server Cluster
-Verify ‘Authentication Domain’ has been specified
-Verify that the domain is specified in the ‘REN Server Browser URL’
Case # 3
This case applies to PeopleTools 8.44 only. If the initial PIA deployment did not specify an Authentication Domain, but the environment now has one, it is necessary to add the Authentication Domain to the active Web Profile. Navigate to PeopleTools > Web Profile. Search for and select the active Web Profile. (If you do not know what Web Profile is currently active, check your configuration.properties file. It will tell you what Web Profile is currently active). Once you have the Web Profile up, the first tab should be labeled “General”. Make sure the field for Authentication Domain field on the General tab has your company’s Authentication Domain (ex. mycompany.com). Make sure to save your changes and bounce the web server for the change to take effect, then go back and try running your Ping Test.
This case applies to PeopleTools 8.44 only. If the initial PIA deployment did not specify an Authentication Domain, but the environment now has one, it is necessary to add the Authentication Domain to the active Web Profile. Navigate to PeopleTools > Web Profile. Search for and select the active Web Profile. (If you do not know what Web Profile is currently active, check your configuration.properties file. It will tell you what Web Profile is currently active). Once you have the Web Profile up, the first tab should be labeled “General”. Make sure the field for Authentication Domain field on the General tab has your company’s Authentication Domain (ex. mycompany.com). Make sure to save your changes and bounce the web server for the change to take effect, then go back and try running your Ping Test.
Case # 4:
One customer reported that in their REN Server Configuration > REN Server Definition page, the Application Server Domain name was case sensitive. After they changed the Application Server Domain name to match how it was defined through PSADMIN (in this case, to include lowercase characters), they were able to access the REN server.
One customer reported that in their REN Server Configuration > REN Server Definition page, the Application Server Domain name was case sensitive. After they changed the Application Server Domain name to match how it was defined through PSADMIN (in this case, to include lowercase characters), they were able to access the REN server.
Case # 5:
If you are still having issues after trying the suggestions above, then try clearing cache in case some Ren configuration changes were made, but cache was not cleared afterwards. To clear cache, bring down the PIA web server and the application server and clear the cache. Also, clear the cache and cookies from your browser and close all browser sessions. Restart the PIA web server and application server. Then run ping test again.
If you are still having issues after trying the suggestions above, then try clearing cache in case some Ren configuration changes were made, but cache was not cleared afterwards. To clear cache, bring down the PIA web server and the application server and clear the cache. Also, clear the cache and cookies from your browser and close all browser sessions. Restart the PIA web server and application server. Then run ping test again.
No comments:
Post a Comment