An Error 404 page is displayed when trying to access the PGP Universal Web Messenger login page after performing a PUP update to PGP Universal Server 3.2.1 when both database modifications and simple customizations have been performed.
To work around this issue, access the server via a secure SSH client and type the following commands:
1.pgpsysconf --stop tomcat
2.pgpsysconf --stop pgprep
3.cp /usr/lib/omf/b.war /var/tomcat/webapps/b.war
4. rm -rf /var/tomcat/webapps/b
.pgpsysconf --start tomcat
6.pgpsysconf --start pgprep
Accessing the PGP Universal Server command line for read-only purposes (such as to view settings, services, logs, processes, disk space, query the database, etc) is supported. However, performing configuration modifications or customizations via the command line may void your Symantec Support agreement unless the following procedures are followed.
Any changes made to the PGP Universal Server via the command line must be:
·Authorized in writing by Symantec Support.
·Implemented by a Symantec Partner, reseller or Symantec Technical Support.
·Summarized and documented in a text file in /var/lib/ovid/customizationon the PGP Universal Server itself.
Changes made through the command line may not persist through reboots and may be incompatible with future releases. Symantec Technical Support may also require reverting any custom configurations on the PGP Universal Server back to a default state when troubleshooting new issues.
Imported Document ID: TECH186829
Subscribing will provide email updates when this Article is updated. Login is required.
Thanks for your feedback. Let us know if you have additional comments below. (requires login)
Subscribed to the Article.
Unable to subscribe
Thanks for your additional feedback !!!
Enterprise Support Virtual Agent
Rate Me :
Tell us more:
Welcome! My name is Sami, the Enterprise Support Virtual Agent answering technical support questions.