Error caught for Report scheduler
We need to generate a Licence Usages summary report for the first monday of every month and this report need to be send all the stack holder in the pdf format.
We tried to schedule it in case manager portal, but we are not receiving mail even though mail id is correct
What are the steps to reproduce the issue?
1. Need to login the case manager portal. 2. Need to select the gear icon on the report which need to be scheduled. 3. Fill the required details(mail id) .Then submit.
There is no error message we are receiving while scheduling. However upon tracing the Schedule agent we found error like .
"Section 'pzRDExportWrapper' execution error on page 'reportPage' of class 'Rule-Obj-Report-Definition'. : Fail to save: an error occurs while saving the package : org.apache.xml.serializer.ToXMLSAXHandler cannot be cast to org.apache.xml.serializer.SerializationHandler.
Kindly help with you suggestions
***Edited by Moderator Marije to add Support Case Details; BUG**
Updated: 10 Jun 2022 9:02 EDT
Pegasystems Inc.
GB
@LivyaJ02 please can you confirm that you have logged a support ticket for this? I was able to find one logged by your company.
I believe that is the correct procedure for your particular scenario as this will require an in-depth investigation.
One thing that might be worth checking:
--> Does this schedule involve an export to Excel?
Two suggestions:
1. We have identified that fontconfig and it's dependency packages are missed in our Open jdk 8. Can you test by running the below command and restart the server?
Command:
yum install fontconfig
Article on which this suggestion is based:
2. This issue can be caused when there are multiple version jar files. The way to check are to run SQL
SELECT DISTINCT pzjar FROM .pr_engineclasses WHERE pzjar LIKE 'poi%';
Then to delete the older version of poi classes from pr_engineclasses table.
From the pr_engineclasses table, remove the POI entries which are below Apache POI 4.0.1.
For example:
DELETE FROM rulesschema.pr_engineclasses WHERE pzjar LIKE 'poi-3.15.jar'
DELETE FROM rulesschema.pr_engineclasses WHERE pzjar LIKE 'poi-3.17.jar'
@LivyaJ02 please can you confirm that you have logged a support ticket for this? I was able to find one logged by your company.
I believe that is the correct procedure for your particular scenario as this will require an in-depth investigation.
One thing that might be worth checking:
--> Does this schedule involve an export to Excel?
Two suggestions:
1. We have identified that fontconfig and it's dependency packages are missed in our Open jdk 8. Can you test by running the below command and restart the server?
Command:
yum install fontconfig
Article on which this suggestion is based:
2. This issue can be caused when there are multiple version jar files. The way to check are to run SQL
SELECT DISTINCT pzjar FROM .pr_engineclasses WHERE pzjar LIKE 'poi%';
Then to delete the older version of poi classes from pr_engineclasses table.
From the pr_engineclasses table, remove the POI entries which are below Apache POI 4.0.1.
For example:
DELETE FROM rulesschema.pr_engineclasses WHERE pzjar LIKE 'poi-3.15.jar'
DELETE FROM rulesschema.pr_engineclasses WHERE pzjar LIKE 'poi-3.17.jar'
DELETE FROM rulesschema.pr_engineclasses WHERE pzjar LIKE 'poi-4.0.0.jar'
Can you run the following queries as mentioned in the above support articles:
UPDATE PegaRULES.pr_engineclasses set pzcodeset='pega-enginecodenouse'
WHERE PegaRULES.pr_engineclasses.pzjar like '%serializer%' or PegaRULES.pr_engineclasses.pzjar like '%xalan%';
commit;
Note: Please take the backup for "engineclasses" before commiting the above query and Restart the Server.
As per the Team, Provided update command won't create any impact Issue as it is related to the serializer jars. Usally JBOSS server,will have one serializer in the JBOSS and one more at prpc level.
This both Jar files conficts and will usually result in Serializer related issue. So at that point we will make our Pega-Version of serializer to not be used.
If you have questions about this update or about the case in general, please add a note to the case you have already logged.
UST Global
IN
Thankyou so much for your quick response.
Yes we have raised a ticket for the same #INC-228059
--> Yes this schedule involve an export to Excel
We will try the two suggestions you have provided and let you know.