Question
Siemens
IN
Last activity: 16 Feb 2017 3:09 EST
sax parse error during refresh section(on client event)
Pega Version: 6.2 SP2
we are using refresh section with Data transform on a check box in a grid. at Step 4 in ReloadSection activity, we see an exception as below.
Invalid clipboard stream detected in module com.pega.pegarules.data.internal.clipboard.XMLStream.newStream(String, StorageStream). Reason: sax parse error: Content is not allowed in prolog.
in clipboard, we see that the preActivitiesParameter page doesnt contain any data transforms under it. we have the same error even if we are using plain refresh section (without activity & data transform).
same configuration is working absolutely fine in DEV and its failing in QA. Other sections with same configuration (i.e. refresh section with Data Transform) is working fine in QA. Its failing in only this case.
Accepted Solution
Pegasystems Inc.
IN
Hello Prasad,
Do you happen to have a filepath control in the same section?
For issue with Reload section failing with the same error when filepath control is present in the same section, I could find a hotfix (HFIX-5638) which addresses this issue for 6.2sp2.
Best Regards,
Mounika
Siemens
IN
hi Mounika,
Thanks for quick response. we have a filepath control in the same level but not on the same section. if we remove the file path control, its working fine(we dont have this error). HFIX-5638 is installed in DEV but not in our QA environment.
but, we have another section without filepath control and its still failing in that case.
please suggest
Pegasystems Inc.
IN
I am not sure of the exact reason, why it is failing for the other section. As a quick test please perform the below.
As the hotfix contains changes in the ReloadSection activity. Try adding the changes of the hotfix in your QA environment and let us know your observations for both the scenarios.
Best Regards,
Mounika
Siemens
IN
hi Mounika,
There was a data issue with the second section because of which we had an issue. regarding the first one, (since we are on a tight schedule) we've eliminated the refresh section and the data update has been moved to the post activity.