Skip to Content
avatar image
Former Member

KM index Error when index Contract document

Hi

We have ESourcing and Portal. The KM is configured to display the contract document through the KM folder ESourcing.

We have created the 3 indexes:

CONTEXT_CLAUSES_INDEX

CONTEXT_MA_INDEX

CONTEXT_SA_INDEX

Some of the documents could be indexed (very little no. of docs could be index) while other documents had error.

From the Portal, a lot of the documents had such error :

Document ID Return Code Return Message Document Status Action Retry Count

/Esourcing/-2147483548/-2147483548/1818/-2147379219 6500 HTTP Status Code 500: Internal Server Error Preparation Failed Index 3

Any assistance would be appreciated.

Thanks.

Regards

mike

Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

1 Answer

  • avatar image
    Former Member
    Aug 23, 2010 at 03:03 PM

    6500 HTTP Status Code 500: Service Unavailable

    This usually happens after cycling the instance as TREX comes up before the Java stack and so a lot

    of messages are skipped over in the preprocessing stage. Reindex the indexes to fix the outstanding

    documents status.

    Add comment
    10|10000 characters needed characters exceeded

    • Former Member Former Member

      Hi Mike,

      I am configuring KM & TREX for E-Sourcing and ran in to a weird error. Here is what I did:

      1) Deployed the SRMKMXCLMJAVA file on Java portal.

      2) Configured Basic Authentication as mentioned in guide by configuring E-Sourcing Repository Manager. Did'nt perform any of the SSO steps.

      3) Setup KM (Contractgen*) properties in E-Sourcing.

      4) Created 3 indices context_ma_index, context_sa_index, context_clauses_index.

      5) This is where I got the error. While I try to assign the datasource root --> Esourcing --> Enterprise Context ID --> Enterprise Sub Context ID --> Class ID, it gave an error "The repository needs the properties service to be attached to a classification index".

      6) I edited the E-Sourcing Repository manager and select "com.sapportals.wcm.repository.manager.generic.search.SimplePropertySearchManager" in property search manager. Restarted J2EE.

      7) Now the root --> Esourcing --> Enterprise Context ID --> Enterprise Sub Context ID --> Class ID does'nt exists. There is no Esourcing under root while adding data source.

      I didn't created that data source to begin with and am wondering why did they disappeared. Am I missing anything?

      Thanks

      BA