cancel
Showing results for 
Search instead for 
Did you mean: 

HTTP error: 500 Internal Server Error - Cannot Process via OAM1

Former Member
0 Kudos

We've got document imaging set-up for invoices, delivery notes, confirmations, etc etc and for some reason we encounter HTTP 500 error for a few of these everyday. We archive over 50K PDF's a day.The situation seems to be of a random nature.

We we try to re-process these failed HTTP 500 thru OAM1 (Execute LUW) and it always returns an error message "Function module does not exist or EXCEPTION raised".

I ran it under debug and found the following messages:

~response_<HTTP/1.1 500 Internal Server Error |

~server_pr<HTTP/1.1 ; |

~status_co<500 |

~status_re<Internal Server Error |

x-powered-<Servlet 2.4; Tomcat-5.0.28/JBoss-3.2.8.SP1 (build: CVSTag=JBoss<

content-ty<text/html;charset=utf-8 |

content-le<1000 |

date |Thu, 29 May 2008 00:21:54 GMT |

server |Apache-Coyote/1.1 ; |

connection|close |

~remote_ad< |

~uri_schem<NONE |

However, when I run other failures (non-HTTP 500) they process successfully and the same messages under debug are:

~response_<HTTP/1.1 201 Created |

~server_pr<HTTP/1.1 ; |

~status_co<201 |

~status_re<Created |

x-powered-<Servlet 2.4; Tomcat-5.0.28/JBoss-3.2.8.SP1 (build: CVSTag=JBoss<

content-le<0 |

date |Thu, 29 May 2008 00:17:48 GMT |

server |Apache-Coyote/1.1 ; |

connection|close

Has anybody encountered this situation?

Does anyone know another way of how to successfully process these errors?

I have gone thru each of the HTTP 500 messages on SDN but non seems to be the issue we're having.

OSS was not much useful either.

I'll really appreciate your help.

Thanks.

Soyab

Accepted Solutions (0)

Answers (1)

Answers (1)

Former Member
0 Kudos

The interesting thing to note is that HTTP 500 failed documents from out test system to the test archiove server will process successfully.

Also, when I connect the test SAP system to the production archive server the HTTP 500 failed record will process succsessfully.

It implies something is incorrectly set-up in our production SAP system but what?

Thanks.

Soyab