Getting File not found exception while Parsing excel file
Hi All,
I am uploading the excel file using file path control and trying to parse it using OOTB activity MSOParseExcelFile. I am getting File not found exception while Parsing excel file.
Also the pyFileUpload property is not being populated in pxRequestor Page. So I am hardcoding path and passing it as a parameter to MSOParseExcelFile activity, but still getting the below error in logs.
2016-08-09 13:24:32,305 [-bio-8080-exec-19751] [dalProcess] [ ] [ FXMM:01.01.01] (rseExcelFile._baseclass.Action) ERROR pegacloud.io|ip-10-123-0-55.eu-west-1.compute.internal - java.io.FileNotFoundException: file://default:/Users/584539/Desktop/TestingExportData1.xlsx
2016-08-09 13:24:32,306 [-bio-8080-exec-19751] [dalProcess] [ ] [ FXMM:01.01.01] (rseExcelFile._baseclass.Action) ERROR pegacloud.io|ip-10-123-0-55.eu-west-1.compute.internal - Error in parsing Excel file C:\Users\584539\Desktop\TestingExportData1.xlsx
Error in Tracer : Getting the below error message in tracer The uploaded file template could not be recognized. Please upload a valid file. Refer to template OpInfo_tmp1 for details.
The uploaded file is same as template but still getting the error.
Please help. Thanks In Advance.
***Updated by moderator: Lochan to add Category***
Accepted Solution
Capgemini
IN
Hi,
Sorry for delayed response.
As you are uploading it in screenflow, it might not upload the file in each stage. May be upload it after the screen flow got complete. Just an assumption.
Can you try the below.
Create a button on the screenflow to upload.
On the button invoke local action. In the local action you will have one flow action referred. On the section of the flow action use the filePath control. Now on the post processing of the flow action try to parse the excel.
If you already fixed the problem , let us know your approach.
-Saikat
Pegasystems Inc.
GB
Are you running your Browser and PRPC on the same physical host ?
I'm just note sure what this PATH here refers to :
C:\Users\584539\Desktop\TestingExportData1.xlsx
Isn't that the original path on the client ? Rather than being the path on the PRPC side ?
Sounds like the Upload is failing here - rather the processing of the file ? (that's only a guess at this point though).
Cognizant Technology Solutions
NL
Cognizant Technology Solutions
NL
PEG
IN
Capgemini
IN
Hi ,
There can be two scenario.
1. File is not uploaded in server properly. Remember that the filepath upload the file on submit of the flow action not immediately. You need to create a pop up which hold the file path and on submit of that pop up need to parse the file.
2. File is not same as the file you specify in the template. Try uploading the template it self. If you get the error then it should be the first issue.
-Saikat
Cognizant Technology Solutions
NL
Hi Saikat..Thanks for your reply.. I think i have the first issue mentioned by you.
I am using a screen flow and I have three screens . On submit of screen1 i need to parse the excel file.
Firstly if I am Parsing on post processing activity of screen1 issue exists , Secondly even if I parse it during pre processing acivity of screen2 that is when the screen 1 is submitted still the file is not getting uploaded, getting the file not found excpetion.
In the pxRequestor page pyFileUpload proprety is not setting , For testing I hardcoded the value of the pyFileUpload property on pxRequestorPage it is still not working.
Please help. Thanks in advance.
Accepted Solution
Capgemini
IN
Hi,
Sorry for delayed response.
As you are uploading it in screenflow, it might not upload the file in each stage. May be upload it after the screen flow got complete. Just an assumption.
Can you try the below.
Create a button on the screenflow to upload.
On the button invoke local action. In the local action you will have one flow action referred. On the section of the flow action use the filePath control. Now on the post processing of the flow action try to parse the excel.
If you already fixed the problem , let us know your approach.
-Saikat
Capgemini
IN
You can also follow the debugging steps:
Check the folder location of service import export path. If the file is there or not? You can also check pxProcess.pxServiceExportPath property is there or not? Ideally the file location would be exportpath+fileName.
When you hardcoded it, what was the value you have hardcoded?
-Saikat
Capgemini
IN
You can also follow the debugging steps:
Check the folder location of service import export path. If the file is there or not? You can also check pxProcess.pxServiceExportPath property is there or not? Ideally the file location would be exportpath+fileName.
When you hardcoded it, what was the value you have hardcoded?
-Saikat