cancel
Showing results for 
Search instead for 
Did you mean: 

Web dynpro test suite - file upload error - Error when uploading

former_member117942
Participant
0 Kudos

Hi all,

I've a problem during file upload in PPM web dynpro application.
When I try to attach a file (is not a size problem or filename path), the system returns this error:

"Error when uploading; the file name is invalid or the file is too large".

parameter icm/HTTP/max_request_size_KB is not the cause of this problem; I've also try to set to -1 (deactivation of parameter) but with no success.

I've also applied note oss Note 1736212 - FileUpload: File is not uploaded.

Also if I tried to test the web dynpro abap WDR_TEST_EVENTS in SE80 --> Test webdynpro and then click on FileUpload url; the error reported is the same.

I reported below support packages of my system:

SAP_BASIS 731 0004 SAPKB73104

SAP_ABA 731 0004 SAPKA73104

PI_BASIS 731 0004 SAPK-73104INPIBASIS

ST-PI 2008_1_710 0006 SAPKITLRE6

SAP_BW 731 0004 SAPKW73104

MDG_FND 731 0001 SAPK-73101INMDGFND

SAP_BS_FND 731 0001 SAPK-73101INSAPBSFND

WEBCUIF 731 0001 SAPK-73101INWEBCUIF

CPRXRPM 500_702 0007 SAPK-50007INCPRXRPM

Thanks.

   Maurizio

Accepted Solutions (0)

Answers (2)

Answers (2)

Former Member
0 Kudos

Hi Maurizio & Janice,

That is a issue with standard SAP which we got in upgrade , open a message to SAP and that should fix that.

We had the same kind of issue and SAP replied with the Note 1736212 we applied it and it solved the issue .

Thanks

Phani

Former Member
0 Kudos

We finally got the issue resolved.  At OSS's response, we applied note 1736212 and note 1776744 which brought in an additional 15 notes.  We were using SNOTE to apply but ran out of memory in our TST system, so had to apply each of the 17 notes separately.  This did fix our TST system.

We also used SNOTE in our DEV system.  It did not run out of memory but brought in all of the 17 notes.  However we got an error on the nw_ur_mimes.zip file.  Un-applying and re-applying this last 1776744 note fortunately fixed that problem.

Janice

Former Member
0 Kudos

We are in the process of testing our upgrades at a similar level of support packs and are encountering the same error.  The application was working fine before the upgrade.

Janice