Discussion

1
Replies
581
Views
Close popover
Jayavardhan Tummidi (JayavardhanT0022)
USDA

USDA
US
JayavardhanT0022 Member since 2015 6 posts
USDA
Posted: May 11, 2015
Last activity: January 26, 2017
Closed

Frequent error with PEGA 7.1.7 Up-gradation

Most of the people frequently reporting about the following error when they do PEGA 7.1.7 up-gradation

ERROR - A Problem occurred. [java] com.pega.pegarules.pub.PRException: Unable to construct instance of ApplicationBundle.

[java] From: (unknown)

[java] at com.pega.pegarules.deploy.internal.archive.ApplicationBundle.initialize (ApplicationBundle.java.511)

Caused by: java.io.EOFException: Unexpected end of ZLIB input Stream.

Even, I faced the similar error when i did PEGA 7.1.7 upgrade and i fixed this issue.

Reason of this error:-

This error mostly occur when PRPC unable to deploy any jar file from the binaries 114716_Pega717\rules during the upgradation process. You probably gets this error during Rule schema upgrade process or Data schema upgrade process.

when you see this error, don't panic. but rather just follow the below instructions to resolve the error

a) Make sure you have the java PATH variable defined in your system. Because, PRPC can't extract/construct new application bundle if you not defined JAVA and PATH variables.

b) If the option "A" doesn't work which means if you are still getting the error even you defined JAVA and PATH variables than the jar files of 114716_Pega717\rules are corrupted. So you may need to use the fresh binaries by extracting the media zip file again. Because, the error "Unexpected end of ZLIB input Stream" mostly occur due to the file corruption.

I hope this would help to your upgrade process and save some time.

Thanks,

Jayavardhan

***Updated by Moderator: Marissa to update categories and change from Question to a Discussion post***

System Administration Upgrades
Moderation Team has archived post,
Close popover This thread is closed to future replies. Content and links will no longer be updated. If you have the same/similar Discussion, please write a new Discussion.