cancel
Showing results for 
Search instead for 
Did you mean: 

Download file fails with 404 error in SLD export of business system

Former Member
0 Kudos

Hi all,

We just upgraded to 2004s, and when I try to export BS to a file, I get a 404 resource does not exist error. I wanted to find out which service needs to be activated in either the J2EE stack or the abap stack to allow the download.

thanks,

chris

Accepted Solutions (0)

Answers (3)

Answers (3)

Former Member
0 Kudos

HI,

see this

/people/krishna.moorthyp/blog/2006/07/23/http-errors-in-xi

Regards

Chilla

Former Member
0 Kudos

Hi Chandra,

Thanks but there's nothing relevant in the blog. This is on the J2EE side and it's clearly a bug.

J Wolff

Former Member
0 Kudos

Hi Richard,

I'm seeing the same issue. This looks like a bug.

On the page the filename is: export_20070503_210109_60722.zip

In the link the filename is: export_20070503_210109_60723.zip

The file that actually gets written is: export_20070503_210109_60724.zip

You can work around it by going to the following directory and manually copying the file:

..../j2ee/cluster/server0/temp/webdynpro/web/sap.com/tcsldwd~businesssystem/Applications/com.sap.sld.wd.businesssystem.BusinessSystem/

Thanks,

J Wolff

Former Member
0 Kudos

Yes, the file is generated in the path you have mentioned, but it generates the link incorectly for some reason.

Thanks for the pointing.

Murad.

agasthuri_doss
Active Contributor
0 Kudos

Hi,

1) Did you maintain Client, userid, password, and lang information in SICF transaction -> sap/xi/engine ? Double click on service and check whether you have entered correct information.

2)Access the trace file and search for traces with severity ERROR, WARNING or stack traces.

If we do not find an error in the log file or the error message does not explain the problem sufficiently, access the default Trace. The default trace file contains detailed messages for developers. Extract the relevant trace information e.g. using the time stamp or the message ID.

If this does not explain the problem in more detail, increase the trace level and reproduce the problem. Then restart message processing using the message display tool. Mark the message and select repeat.

3)Check the Note-803145

4) 404 is an HTTP response code that indicates that the resource in question could not be found. Usually this is due to an incorrect URL check all URLs.

5)The SOAP message that sent might not have an envelope.

Regards

Agasthuri Doss