Skip to Content

Archived discussions are read-only. Learn more about SAP Q&A

TREX Indexing: HTTP Status Code 500: Internal Server Error (6500)

Dear all,

we are confronted with a strange phenomenon regarding the indexing of documents in external repositories.

KM File System Repositories are successfully integrated into both the test- (TP1) and productive portal (PP1). On the testportal indexing (TREX) works perfectly, on the productive portal we set up the network path, KM File System Repositories and indexes (+ authorisations) in exactly the same way and pointing to the same path. However searching in test and prod for the same word with the same user (same roles & authorisations) has different results.

In PP1 the index monitor shows the following errors for most documents (Queue-Einträge anzeigen):

Rückgabewert: 6500

Rückmeldung: HTTP Status Code 500: Internal Server Error

Dokumentstatus: Vorverarbeitung fehlgeschlagen

It is also interesting that TREX finds some documents in PP1, in the preview-area the following error text is displayed: "Portal Runtime Error An exception occurred while processing a request for :iView :N /AComponent Name :N /AAccess denied ( Object :portal _" instead of the correct preview-text in TP1 "Richtlinien für IT-Anforderungen..."

The only difference between TP1 and PP1 is that PP1 is integrated into the same domain name area as the file servers. Seeing the integrated file system repositories work fine in both TP1 and PP1 (KM Navigation iViews pointing to the same file network paths) the indexes should work on both systems too. We also checked the network authorisations and couldn't find any reason for the difference of TP1 and PP1.

Has anyone got an idea what the problem/solution could be?

Thanks alot in advance!

Jeanette

Not what you were looking for? View more on this topic or Ask a question