PAS73 error when submitting print jobs via CPS - Managed Cloud Print - c06326353

Within the ECP environment, if any CPS upgrades are done on the local server (as opposed to being done via AWS scripts), there may be PAS73 error shown when testing a print job to the load balancer address.

You will notice that the CPS PrintAnywhere Server URI value is set to "http://localhost/PasServlet/PasServlet", yet PAS is on a different physical server. This is due to the passervlet.properties being modified in a AWS environment to point to the PAS AWS LB address (eg. http://internal-AMATA-PASLoadBalan-1C4VGTNG5BTBZ-2658906.us-east-2.elb.amazonaws.com/PasServlet/PasServlet) instead of the default 127.0.0.1.

To resolve, choose 1 of 2 options:

1. (Recommended) - Stop and Start the CPS instances in Opsworks. This will trigger the proper configuration scripts to modify the configuration files on CPS. Do not reboot - this is not the same process.
   • Completing this step will bring the system back in terms of configuration to how they were done when using the AWS script to complete the installation
2. Manually modify the Apache Tomcat\webapps\PasServlet\WEB-INF\passervlet.properties file to point to the PAS loadbalancer address.
   • Using this step allows quick recovery of the system, only to be used as a quick fix, but step 1 should be completed at a later time.

To collect the PAS LB URI from AWS (this should also be stored on the client's Confluence page related to their AWS deployment):

• In OpsWorks choose one of the PAS servers for your client
• Under the Elastic Load Balancing header on the right, click the LB link shown
• Full DNS will now be displayed for you to copy/paste