Skip to main content

This content has been archived and is no longer being updated. Links may not function; however, this content may be relevant to outdated versions of the product.

Support Article

Error deploying war files



Administrator upgraded Pega(PRPC) from 7.1.5 to 7.1.6 and to 7.1.7.
Database upgraded server was successful i.e. with out any error reported but not able to deploy the war files. 

Error Messages

HTTP Status 404 - /prweb/PRServlet/
type Status report
message /prweb/PRServlet/
description The requested resource (/prweb/PRServlet/) is not available.

Steps to Reproduce

We delete old war files, prweb, prhelp and prsysmgmt and replace with new from 7.1.7
When tried to start Tomcat again, Tomcat doesn't deploy new wars.

Root Cause

It was concluded that database upgrade didn't complete correctly.
This was concluded based on following investigation:
Compared previous update log with update logs on test system and found that in previous instances for some reason it picked up pega.codeset.version=07-10-13. Which means upgrade tried to update the database from 07-10-13 to 07-10-13(which is same and is 7.1.6 codeset).
Also confirmed that pzcodesetversion='07-10-15'(with is 7.1.5 codeset) COUNT is 82629 after latest upgrade, Which is what expected as per trial upgrade on test system and this count was 2 on previous upgrade run.


Revert the virtual server to 7.1.6 working check point made before initiating upgrade and perform using 7.1.7 Automatic upgrade path rather than manual.

Published January 31, 2016 - Updated October 8, 2020

Was this useful?

0% found this useful

Have a question? Get answers now.

Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best.

Pega Community has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice
Contact us