Error attaching file size 10 MB
Hi Everybody,
I really would appreciate some help about the following issue:
When attaching a file larger than 10 MB to a Content in the Knowledge Management app the user sees the Error Harness saying 'Please Contact You Administrator'. The described error happens to be found ONLY in quality and production enviroment.
In order to resolve the issue I've done all the following actions, none of them worked:
-I've created a DSS to set the prcofing uploading file size, with a value grater than 10 or equal to the pyMaxDragDropAttachSizeMB.
-I've increased the size of the transaction log size in DB quality envinroment.
The tracer detects the following fail when reloading the harness (the language is italian but I think the error is comprehensible)
Impossibile trovare una 'RULE-OBJ-ACTIVITY' con il nome 'PYUPLOADFILE' valida per 'PegaFW-KM-Work-Content'. Nel rulebase sono state trovate regole 4 con questo nome ma nessuna corrispondeva a questa richiesta. The 4 rules named 'PYUPLOADFILE' defined in the rulebase are: 4 unrelated to applies-to class 'PegaFW-KM-Work-Content', for example: {Data-NLP-, Rule-NLP-, Rule-, Data-WorkAttach-File}.
I've checked in develop and test enviroments and PYUPLOADFILE' with class 'PegaFW-KM-Work-Content' does not exists.
I Would really appreciate some help regard this issue.
Thanks,
Giulia
https://collaborate.pega.com/question/export-images-rte-control-word
Capgemini
IN
Hi,
This should be something related to access group to application pointing. Check the access group in test is having the same rulesets that you have it in Dev.
Looks like pzMultiFilePath does refer to pyUploadFile activity, now depending on the step page it may find the activity or may not find. Please check the step page as well.
-Saikat
Updated: 28 Dec 2020 14:56 EST
Capgemini
IT
Hi Sakat,
Thank you for your fast reply. I've already checked the RS of the AG in Quality with the one in DEV and they are the same. Also, I've checked the activity and the step page is configured correctly.
Also, no modifications have been done to the activity or the Knowledge Management Application.
Any other hints?
Thank you,
Giulia
Capgemini
IN
Hello,
Go through the code for the control which is invoking the pyUploadFile activity, there must be something different.
Thanks
Saikat
Capgemini
IT
Hello Saikat,
The control which is invoking the pyUploadFile activity has not been customized whatsoever and is the same as the one present in the other environments, also the error is detected when the harness is reloaded.
Thanks,
Giulia
Aaseya IT Services Pvt LTD
SA
After changing the DSS, did you perform a server restart? I think, you need to do application server restart when you update the upload attachment size DSS
Capgemini
IT
Hi PrakashDeep,
Yes, the application server was restarted after I've updated the attachment size DSS.
Thanks,
Giulia
Aaseya IT Services Pvt LTD
SA
https://collaborate.pega.com/question/how-change-maximum-file-size-attachments
Please refer to mentioned link. Same issue was reported there and it was resolved. For you reference, i am copying the same content here.
Here is an update. You don't need to use above DSS "prconfig/Initialization/MaximumFileUploadSizeMB/default". Instead, there is another DSS, "repository/maxFileSizeInMemory" and you can accomplish any file size requirement using SS, and this DSS.
To conclude, if you want to set maximum file size for both "Drag & Drop" and "Select file button" to be the same value,
AND if you want to set them all lower than 45MB, you can accomplish this by using only SS ("pyMaxDragDropAttachSizeMB").
OR if you want to set them all higher than 45MB and lower than 1GB, you should use DSS ("repository/maxFileSizeInMemory") and SS ("pyMaxDragDropAttachSizeMB").
https://collaborate.pega.com/question/how-change-maximum-file-size-attachments
Please refer to mentioned link. Same issue was reported there and it was resolved. For you reference, i am copying the same content here.
Here is an update. You don't need to use above DSS "prconfig/Initialization/MaximumFileUploadSizeMB/default". Instead, there is another DSS, "repository/maxFileSizeInMemory" and you can accomplish any file size requirement using SS, and this DSS.
To conclude, if you want to set maximum file size for both "Drag & Drop" and "Select file button" to be the same value,
AND if you want to set them all lower than 45MB, you can accomplish this by using only SS ("pyMaxDragDropAttachSizeMB").
OR if you want to set them all higher than 45MB and lower than 1GB, you should use DSS ("repository/maxFileSizeInMemory") and SS ("pyMaxDragDropAttachSizeMB").
OR if you want to set them all higher than 1GB and lower than 2047MB (maximum size), you should also use DSS ("prconfig/initialization/maximumfileuploadsizemb/default") first to unlimit the 1GB restriction, and then use DSS ("repository/maxFileSizeInMemory") and SS ("pyMaxDragDropAttachSizeMB").
- "prconfig/initialization/maximumfileuploadsizemb/default" DSS:
- This is not specific to file attachments from UI but for files upload to app server in general. This DSS does not exist as out-of-the-box, and you need to create it if needed. Reboot is required when you change the value. When this DSS does not exist, system limits any files upload to 1GB (implicit default).
- The maximum value you can set in this DSS is 2047MB. You can save it with higher value, but system will actually overwrite it by 1GB at runtime.
Hope this helps.
Thanks,
Updated: 4 Jan 2021 10:09 EST
Capgemini
IT
Hi PrakashDeep,
I am in the scenario where there is only the SS "pyMaxDragDropAttachSizeMB", not saved in the app RS and as it is configured both in development and test environment. As a matter of fact, the funcionality works correctly in development and test environemnt but not in quality and production.
Also, the issue is presented when the size of the file attached is 10 MB, far below 45 MB either when using drag and drop feature or Select File button.
Also, the control is pzMultiFilePath which has the configuration showed in the image attached.
Giulia