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

[Former Member]

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

[former_member195891]

Hi Jaenette,

Please have a look at the trace file of the preprocessor. The log file is located in <TREX dir.>/traces. The files are named TrexPreprocessor.xxxxxx.trc

A reason for the not working preprocessing could e.g. be missing proxy settings on TREX side. If you internally use proxy servers, make sure that the TrexPreprocessor.ini has the right settings in the httpclient section. Please have a look at the TREX installation guide for furhter details about the setting.

Kind regards,

Roland

[Former Member]

Dear Roland,

thanks for your reply. We finally solved the problem with a hint of SAP. Everything was fine with TREX and the indexes - the cause of the problem were missing permissions in the PCD for the KM-document-iView com.sap.km.docs.

In the logfile there was a misleading hint that the index_service user should be assisgned to the object "pcd:general/every_user/.../eu_role/.../com.sap.km.docs", which was however not possible as the permission editor did not find the (existing) service user to assign to the object.

We had copied the eu_role to customer_eu_role and gave the Portaluser folder in the PCD the permission for a user group containing customer_eu_role. This diddnt seem to be sufficient - once I assigned customer_eu_role directly the indexes worked again.

Hope this is helpful if anyone should ever be confronted with the same issue.

Kind regards,

Jeanette