TREX: on SKPR07 "index possible" is red

We have configured the connection between SM7.0 and TREX7.1.
On the txn TREXADMIN, every service is green.
However on SKPR07, the 3 radio buttons (index possible, etc) are red.
If we do a "full text search" on SOLAR01, we get no documents even we see the desired doc there directly.
Would you please share your opinions?
Thanks! Points guaranteed.

My issue is different:
1) On TREXADMIN, the httpservice is green, all other services are green as well;
2) Only on SKPR07 the radio buttons such as "index possible" are red;
3) On solar01 we cannot do full text search even we maintained SKPR06 .
Any idea?
Thanks!

Similar Messages

Trex: Preparation failed: index operation

Hi gurus,
We have a Trex 7.0 server working on a seperate server. When I look at Index Administration, the statuses of the indexes are all green. But when i look at the indexing monitor, one of our indexes is in red status, It says Indexed:13342, Errors: 15610.
When I click on the Errors link, It says: "Trex: Preparation failed: index operation".
I searched the trace files but couldn't find sthg useful.
Any suggesstions?
Tolga

Hi Tolga,
please check your installation with the information mentioned by Jochen Goeeninger (long post) in the following thread Trex HTTP Server not seen in Portal
Furthermore try to open one of the documents you are trying to index via HTTP from the TREX Server.
With the result of that, I would suggest to open support message under http://service.sap.com/message
Hope this helps,
Robert

TREX is not indexing certain excel files

Hi Experts,
TREX is not indexing certain excel-files correctly. I get a "no message found error" (14047) Trex: Preparation failed: index operation by certain excel files - but not by all. I found out what they have in common: some have filters activated and some have a lot of columns or rows.
Is there any way to avoid these errors and index them correctly?
TREX: 7.0.47
Portal: 7.01 SP7
Thank you in advance
Best Regards
Norman

Hi Norman,
Did you review note 1528705? It has a fix for this issue.
Best regards,
Duncan

Trex is not indexing Outlook messages .msg

Hi Everybody,
Does anyone know why TREX is not indexing .msg (Outlook mail) files?
In [Help.sap.com|http://help.sap.com/saphelp_nw04s/helpdata/en/55/cb634114b78047e10000000a1550b0/frameset.htm] it says it should be supported...
Any ideas?
Thanks in advance,
Fede

Thanks Raghu!
You solved my problem!!
The definitive solution was:
In portal (SysAdm > SysConf > KM > CM > Utilities > MIME Types) I've added this settings:
Name "msg"
Default Extension ""
Extension "msg"
Locale ""
MIME Type "application/vnd.ms-outlook"
Resource Bundle File ""
Resource Key ""
In <disk_drive>:\usr\sap\trex_<instance_number>\TREXValidMimeType.ini, I've added the following rows:
application/vnd.ms-outlook
message/rfc822
Now TREX is indexing .msg outlook files!
Thanks Again,
Fede

TREX does not index all documents fro document class SOLARGNSRC

Hi all,
I've setup a connection between a TREX server (which is also used by a portal system) and Solution Manager. I've gone through the settings in SAP Note 750623 and I was able to create a index, the queue and even bypass the basic authentication in the preprocessing for document class SOLARGNSRC
According to everything I've read, this should be enough to be able to index all documents in Solution Manager and find them with Full Tex Search. But this doesn't work. From the 50.000 documents in de class (35.000 English and 15.000 German) only 6300 documents are passed to TREX. Most of them are German HTML links to help.sap.com. I can see in the trace files that the URL's to some documents in the content server are passed to TREX. I can open dthe document using the links but I cannot find the documents using the full text search which I think means that nothing was really indexed.
Questions:
1. Has anyone been able to succesfully index Solution Manager documents for full text search purposes?
2. Why are only 10% of the documents passed to TREX? Is there a specific setting for this?
3. Why does TREX use the Content Server HTTP links to index the documents and not the RFC connection?
Cheers
Marcel Rabe

Yep, all lights green
SSR maintained. DRFUZZY as Search Engine (I have not tried Verity)
Return Code? Interesting, I don't get an return code when I trigger the Index/Deindex. I just see the hourglass for about 5 minutes (when I run it in the foreground) and after that its back to the way it was. No messages. Nothing appears in the application logs as far as I can see.
The program RSTIRIDX is scheduled in the background and runs every hour minutes for about 10 seconds without an error.
TREX Version 7.00.39.00
Five languages actived, including German and English. In SKPR07 under Indexed documents I can see that 300 German and 6000 English documents have status indexed.
No proxy server. Systems sit within the same network segment
Thnx for your help. I posted a message with SAP as well as this seems strange to me.
Marcel

TREX does not index documents

Now this one is a bit strange. We have created an index on a file system repository that contains a number of different types of files including plain text, MS-Word, Excel and Acrobat PDFs. The queue now has a red status showing a sizeable number of documents failed the preparation, but a few are ready to be transmitted.
We found that none of the MS-Word, Excel and Acrobat documents passed the preparation stage. Anything that passes preparation is either a directory or a plain text file, though this is not consistent either since a number of files that did not pass preparation where als plain text files.
What gives? Am I missing something here? Any hints would be very much appreciated.

Hello Wolfgang,
we faced exactly the same problem. To be more precisely, documents with more than 10kb were not indexed. The reason for this is, that doc´s smaller than 10kb are automatically transmitted to TREX by the crawler. For documents bigger than 10kb the crawlers only transmit the URI and then the TREX fetches them by itself.
The URL´s that are sent to TREX are normally built by the URL generator using the host entry. If you have a clustered landscape this might not work, because the Firewall, Load-Balancers, WebServers, or external authentication Systems might cause problems when they are directly called by TREX via the normal portal URL.
In this case you must specify the name of a specific server (e.g. http://server.com:50000) as Alternative Host in the URL Generator Service. But be careful with that setting. A wrong setting might crash your system (happened on our productive layer unfortunately).
If you use SSL for the communication between TREX and portal it even gets more complicated. Fortunately I did not have to deal with that.
Thus, if you have clustered system, be sure that the communication TREX to Portal can take place without problems. Take a look at the trace files of the TREX preprocessor, this should give you a hint on this.
Hope this helps.
Kind regards,
Christopher Höfele

TREX upgrade and index corruption

What are the dangers with upgrading TREX 6.1 from SP 9 to SP 16?
Is there the possibility that the existing indexes get corrupted?
Thanks, Davide

Hi Davide,
There is no danger of upgrading from TREX 6.1 SP9 to TREX 6.1 SP16.
Indexes do not get corrupted with the upgrade.
Regards,
Srini

TREX doesn't index some PDF documents ...

Hello all,
we have installed EP'04s and TREX ver. 7.00.42.00. It works well except one thing. TREX is not able to index some PDF documents. Most of them is indexed correctly but some documents not. Actually the problematic PDF documents are indexed but their content is not. In search result is displayed message "No document excerpt available" for the documents.
I found SAP Note 622419 that could relate with that but I don't know how can I check:
1. What encoding was used in particular PDF form.
2. What fonts or what font types were used in particular PDF form.
Do you have any idea how to find out these information about a document? Or do you know where could be problem when TREX are able to index content of just some PDF documents?
Regards,
Zbynek

Thank you, that was what I needed.
So now I know the test PDF document use only TrueType fonts. That means its content should be indexable for TREX but it isn't. There is just message "No document excerpt available" for this document in search results.
Could someone look at the document and try to index it? It can be downloaded from http://www.volny.cz/kabrtz/TREX/indexing_test.pdf
Regards,
Zbynek

Trex 7.0 index issue

Hi All,
In our portal system which is on SAP Netweaver 7.0 ehp1 with Trex 7.0 version, there is a strange behaviour.
The index corresponding to the repositories although they get created on reindexing every time allow for searching for the documents on the portal for few hours only.
After few hours , the number of documents indexed is greatly reduced at times to even 0 and hence the search does not yield any results.
Hence, the search only works few hours from the point the reindex is done and stops working after few hours.
Any suggestions for resolving this strange behaviour is highly appreciated.
Regards,
Murali Narayanan

Hi Murali,
Can you give us a little more information about the problem that you're seeing? Is this happening to just one index or multiple? What type of repositories are these that you are indexing? Is there a rebuild schedule set up on the index so that they automatically rebuild every day?
Looking at the TREX monitor, how many documents are showing up in the 'OK' column for your index?
-Stephen Spalding

TREX unable to index only some files

Hi All!
I've got problem with my TREX (6.1 SP14 running on portal maschine SAP EP 6.0 SP14).
I've created some repositories, physically residing on that server's filesystem. It's an WebDAV repository and two CM (FSDB and DBFS).
Created an Index.
It indexes those repositories, and after that I see, that it can't index content of some files, while normally indexes others. It can't index *.doc, *.xls, *.pdf, *.ppt. It normally indexes *.txt, *.zip and folders.
In application log (in portal) I can see, that error code is 401 (6401), 'not authorized'.
If I open (for example) some *.doc file properties and try to access 'Settings'>'Classification', I recieve an error:
"An error occurred during classificationError while classifying resource /FSDB_local/testdocFSDB.doc for taxonomy localfiles_tax.com.sapportals.wcm.WcmException: HTTP Status Code 401: Unauthorized (Errorcode 6401)".
In IIS log there is:
"2006-01-26 17:51:01 W3SVC1 10.2.1.67 PROPFIND /localfiles/EPtest/Logging.doc - 80 GMCS\MYUSER 10.x.x.x SAPCMWebDAVRepository1.1 $Version=0;+MYSAPSSO2=AjExMDAgABJwb3J0YWw6 207 0 0"
In security log of windows system I can only see 'successful' events like :
"Event Type: Success Audit
Event Source: Security
Event Category: Object Access
Event ID: 560
Date: 26.01.2006
Time: 20:41:13
User: HOSTNAME\SAPServiceSID
Computer: HOSTNAME
Description:
Object Open:
 Object Server: Security
 Object Type: File
 Object Name: D:\repositories\FSDB
 Handle ID: 13960
 Operation ID: {0,1066813}
 Process ID: 924
 Image File Name: D:\usr\sap\G03\JC00\j2ee\os_libs\jlaunch.exe
 Primary User Name: SAPServiceSID
 Primary Domain: HOSTNAME
 Primary Logon ID: (0x0,0xEFAE)
 Client User Name: -
 Client Domain: -
 Client Logon ID: -
 Accesses: SYNCHRONIZE
 ReadAttributes
 Privileges: -
 Restricted Sid Count: 0
 Access Mask: 0x100080
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
What could it be?
All permissions (on portal side and on filesystem) are the same for all files.
Thanks in advance for help and support!
Regards,
DK

I have a similar issue with a web repository.
I have an alternative URL set in the URL generator and I also do not have a locked index_service user (password is also reset) but I am getting the same 401 (6401 TREX error) problems as others.
Anybody know how to solve this problem?
How does TREX authenticate with the portal using the index_service user? How does TREX know what credentials to use? If it is ticket based authentication, how is this ticket set in the TREX system?
Thanks,
Tom
http://tomparle.com/
http://deadlytech.co.uk/

TREX - Error importing index

hi,
we upgraded our TREX 6.1 to 7.0 on a new server. The index export worked fine but when we want to import the index files with the import61-70 python script there is an error showing:
[2009-02-04 13:35:31] : Starting import on 7.0 system
[2009-02-04 13:35:31] : Unzipping archive file(s).
[2009-02-04 13:35:31] : Working on file Y:\Indextransfer\isw25.zip
[2009-02-04 13:35:57] : Closing zip file
[2009-02-04 13:35:57] : Searching for following zip file Y:\Indextransfer\isw25_1.zip
[2009-02-04 13:35:57] : No follow zip archiv found
[2009-02-04 13:35:57] : Finished with zip files
[2009-02-04 13:35:57] : Importing index 4744464b226e4c5de10000000a35e046ccm110
[2009-02-04 13:36:07] : Error importing index4744464b226e4c5de10000000a35e046ccm110
I didnu00B4t find any logs i.e. a better description of the error than this one.
I also dinu00B4t find a sapnote relating to this.
Are there any more logs for the import?
Edit:
I found this in TrexQueueServerAlter.trc
[3284] 2009-02-05 10:13:46.953 e TrexSlice SnapshotFileManager.cpp(00671) : SnapshotFileManager: copy <D:\tmp\trex_import_tmp_20090205-101313\queue\4744464b226e4c5de10000000a35e046ccm110/TREX4744464b226e4c5de10000000a35e046ccm110.ini>-><D:\usr\sap\TRX\TRX04\queue\4744464b226e4c5de10000000a35e046ccm110/TREX4744464b226e4c5de10000000a35e046ccm110.ini> (syncpoint=1) failed, rc=5(Access is denied)
[3284] 2009-02-05 10:13:46.953 e TrexSlice SnapshotFileManager.cpp(00501) : SnapshotFileManager: failed to update <D:\tmp\trex_import_tmp_20090205-101313\queue\4744464b226e4c5de10000000a35e046ccm110> rc=34
[3284] 2009-02-05 10:13:46.953 e Q4744464b2 Queue.cpp(02095) : Queue::restore: : error: file could not be written
[4380] 2009-02-05 10:23:49.609 e TrexSlice SnapshotFileManager.cpp(00671) : SnapshotFileManager: copy <D:\tmp\trex_import_tmp_20090205-102313\queue\4744464b226e4c5de10000000a35e046ccm110/TREX4744464b226e4c5de10000000a35e046ccm110.ini>-><D:\usr\sap\TRX\TRX04\queue\4744464b226e4c5de10000000a35e046ccm110/TREX4744464b226e4c5de10000000a35e046ccm110.ini> (syncpoint=1) failed, rc=5(Access is denied)
[4380] 2009-02-05 10:23:49.609 e TrexSlice SnapshotFileManager.cpp(00501) : SnapshotFileManager: failed to update <D:\tmp\trex_import_tmp_20090205-102313\queue\4744464b226e4c5de10000000a35e046ccm110> rc=34
[4380] 2009-02-05 10:23:49.609 e Q4744464b2 Queue.cpp(02095) : Queue::restore: : error: file could not be written
Edited by: Tobias Nagel on Feb 5, 2009 10:27 AM

I solved the problem myself.
I granted everyone full rights to the temp directory while importing the indexes.
It finished without any problems.

Trex failing to index word docs in FS repository

Hi,
I am having errors while indexing a FS repository.
The errors in TREX monitor are
return message:Content-Length -vs- Actual Read mismatch
return code:8030
Document Status: Preparation Failed
I tried reindexing these failed entries, but did not work out.
All of these are word docs. Moreover Crawler errors for
folders are also visible in the errors list.
Looking into the TREX trace , was able to get the follwing.
HTTP-GET failed for URL <............>with Errorcode -30 , but HTTP-HEAD worked, trying again,
Mimetype application/msword is not based on TEXT, but was detected as text type; content might be corrupted and will be ignored
When I tried opening some of these docs from Windows,
I did not have access to the same itself and got an error. Would this also be the case for the index_service user?
Also not all docs which are visible on the Windows side are visible from the portal in the KM nav iview.
Platform :EP 7.0 SP13, TREX 7.0
Any help would be appreciated
Rgds

Hello,
A problem related to the search for this FS repository is that search takes a very long time to display results.
The datasource is quite big with nearly 90,000 docs and the index is supposed to index external links too with
indexContentOfExternalLink, indexContentOfExternalLink properties set also.The search scope is based on Indexes in the search iview .
When a normal user who has the relevant role for the searh iview runs a search it takes a very long time, nearly 30 min!!
But if a super admin runs the same , it comes up with results immediately.
Is this some kind of authorisation issue.The index is having everyone full control and I was not able to see any thing much in the default trace too.
Is there any particular trace/log file to be checked for this?Has something been missed out in the index creation process?
Hope someone can comment on this
Rgds

TREX not updating index of UME

We have created an index of the UME users for the Who's Who search functionality. Our UME is connected to an Active Directory LDAP. Everything is working except that changes made to AD are not being updated in the index. The index and its data source are scheduled to run its crawler every night. In particular, it is the telephone property that we noticed is not updating.
What am I missing?
Maximum points awarded to the first correct solution.

Here you go. You can see where PRINCIPAL_MODIFY_DATE has been mapped. All the other mappings are pretty standard for AD.
<?xml version="1.0" encoding="UTF-8"?>

<!DOCTYPE dataSources SYSTEM "dataSourceConfiguration.dtd">
<dataSources>
 <dataSource id="PRIVATE_DATASOURCE" className="com.sap.security.core.persistence.datasource.imp.DataBasePersistence" isReadonly="false" isPrimary="true">
 <homeFor>
 <principals>
 <principal type="group"/>
 <principal type="user"/>
 <principal type="account"/>
 <principal type="team"/>
 <principal type="ROOT"/>
 <principal type="OOOO"/>
 </principals>
 </homeFor>
 <notHomeFor/>
 <responsibleFor>
 <principals>
 <principal type="group"/>
 <principal type="user"/>
 <principal type="account"/>
 <principal type="team"/>
 <principal type="ROOT"/>
 <principal type="OOOO"/>
 </principals>
 </responsibleFor>
 <privateSection/>
 </dataSource>
 <dataSource id="XXXXXXXXX" className="com.sap.security.core.persistence.datasource.imp.LDAPPersistence" isReadonly="true" isPrimary="true">
 <homeFor/>
 <responsibleFor>
 <principal type="account">
 <nameSpace name="com.sap.security.core.usermanagement">
 <attributes>
 <attribute name="j_user"/>
 <attribute name="logonalias"/>
 <attribute name="j_password"/>
 <attribute name="userid"/>
 </attributes>
 </nameSpace>
 </principal>
 <principal type="user">
 <nameSpaces>
 <nameSpace name="com.sap.security.core.usermanagement">
 <attributes>
 <attribute name="firstname" populateInitially="true"/>
 <attribute name="displayname" populateInitially="true"/>
 <attribute name="lastname" populateInitially="true"/>
 <attribute name="fax"/>
 <attribute name="email"/>
 <attribute name="title"/>
 <attribute name="department"/>
 <attribute name="description"/>
 <attribute name="mobile"/>
 <attribute name="telephone"/>
 <attribute name="streetaddress"/>
 <attribute name="city"/>
 <attribute name="company"/>
 <attribute name="manager"/>
 <attribute name="uniquename" populateInitially="true"/>
 <attribute name="kpnprefix"/>
 <attribute name="krb5principalname"/>
 <attribute name="dn"/>
 <attribute name="country"/>
 <attribute name="jobtitle"/>
 <attribute name="zip"/>
 <attribute name="state"/>
 <attribute name="pobox"/>
 <attribute name="PRINCIPAL_MODIFY_DATE"/>
 </attributes>
 </nameSpace>
 <nameSpace name="com.sap.security.core.usermanagement.relation">
 <attributes>
 <attribute name="PRINCIPAL_RELATION_PARENT_ATTRIBUTE"/>
 </attributes>
 </nameSpace>
 <nameSpace name="$usermapping$">
 <attributes>
 <attribute name="REFERENCE_SYSTEM_USER"/>
 </attributes>
 </nameSpace>
 </nameSpaces>
 </principal>
 <principal type="group">
 <nameSpaces>
 <nameSpace name="com.sap.security.core.usermanagement">
 <attributes>
 <attribute name="displayname" populateInitially="true"/>
 <attribute name="description" populateInitially="true"/>
 <attribute name="uniquename"/>
 </attributes>
 </nameSpace>
 <nameSpace name="com.sap.security.core.usermanagement.relation">
 <attributes>
 <attribute name="PRINCIPAL_RELATION_MEMBER_ATTRIBUTE"/>
 <attribute name="PRINCIPAL_RELATION_PARENT_ATTRIBUTE"/>
 </attributes>
 </nameSpace>
 <nameSpace name="com.sap.security.core.bridge">
 <attributes>
 <attribute name="dn"/>
 </attributes>
 </nameSpace>
 </nameSpaces>
 </principal>
 </responsibleFor>
 <attributeMapping>
 <principals>
 <principal type="account">
 <nameSpaces>
 <nameSpace name="com.sap.security.core.usermanagement">
 <attributes>
 <attribute name="j_user">
 <physicalAttribute name="samaccountname"/>
 </attribute>
 <attribute name="logonalias">
 <physicalAttribute name="samaccountname"/>
 </attribute>
 <attribute name="j_password">
 <physicalAttribute name="unicodepwd"/>
 </attribute>
 <attribute name="userid">
 <physicalAttribute name="*null*"/>
 </attribute>
 </attributes>
 </nameSpace>
 </nameSpaces>
 </principal>
 <principal type="user">
 <nameSpaces>
 <nameSpace name="com.sap.security.core.usermanagement">
 <attributes>
 <attribute name="firstname">
 <physicalAttribute name="givenname"/>
 </attribute>
 <attribute name="displayname">
 <physicalAttribute name="displayname"/>
 </attribute>
 <attribute name="lastname">
 <physicalAttribute name="sn"/>
 </attribute>
 <attribute name="fax">
 <physicalAttribute name="facsimiletelephonenumber"/>
 </attribute>
 <attribute name="uniquename">
 <physicalAttribute name="samaccountname"/>
 </attribute>
 <attribute name="loginid">
 <physicalAttribute name="*null*"/>
 </attribute>
 <attribute name="email">
 <physicalAttribute name="mail"/>
 </attribute>
 <attribute name="mobile">
 <physicalAttribute name="mobile"/>
 </attribute>
 <attribute name="telephone">
 <physicalAttribute name="telephonenumber"/>
 </attribute>
 <attribute name="department">
 <physicalAttribute name="department"/>
 </attribute>
 <attribute name="description">
 <physicalAttribute name="description"/>
 </attribute>
 <attribute name="streetaddress">
 <physicalAttribute name="streetaddress"/>
 </attribute>
 <attribute name="city">
 <physicalAttribute name="l"/>
 </attribute>
 <attribute name="company">
 <physicalAttribute name="company"/>
 </attribute>
 <attribute name="manager">
 <physicalAttribute name="manager"/>
 </attribute>
 <attribute name="kpnprefix">
 <physicalAttribute name="samaccountname"/>
 </attribute>
 <attribute name="krb5principalname">
 <physicalAttribute name="userprincipalname"/>
 </attribute>
 <attribute name="dn">
 <physicalAttribute name="distinguishedname"/>
 </attribute>
 <attribute name="country">
 <physicalAttribute name="country"/>
 </attribute>
 <attribute name="jobtitle">
 <physicalAttribute name="title"/>
 </attribute>
 <attribute name="zip">
 <physicalAttribute name="postalCode"/>
 </attribute>
 <attribute name="state">
 <physicalAttribute name="st"/>
 </attribute>
 <attribute name="pobox">
 <physicalAttribute name="postOfficeBox"/>
 </attribute>
 <attribute name="PRINCIPAL_MODIFY_DATE">
 <physicalAttribute name="modifyTimeStamp"/>
 </attribute>
 </attributes>
 </nameSpace>
 <nameSpace name="com.sap.security.core.usermanagement.relation">
 <attributes>
 <attribute name="PRINCIPAL_RELATION_PARENT_ATTRIBUTE">
 <physicalAttribute name="memberof"/>
 </attribute>
 </attributes>
 </nameSpace>
 <nameSpace name="$usermapping$">
 <attributes>
 <attribute name="REFERENCE_SYSTEM_USER">
 <physicalAttribute name="sapusername"/>
 </attribute>
 </attributes>
 </nameSpace>
 </nameSpaces>
 </principal>
 <principal type="group">
 <nameSpaces>
 <nameSpace name="com.sap.security.core.usermanagement">
 <attributes>
 <attribute name="displayname">
 <physicalAttribute name="displayname"/>
 </attribute>
 <attribute name="description">
 <physicalAttribute name="description"/>
 </attribute>
 <attribute name="uniquename" populateInitially="true">
 <physicalAttribute name="cn"/>
 </attribute>
 </attributes>
 </nameSpace>
 <nameSpace name="com.sap.security.core.usermanagement.relation">
 <attributes>
 <attribute name="PRINCIPAL_RELATION_MEMBER_ATTRIBUTE">
 <physicalAttribute name="member"/>
 </attribute>
 <attribute name="PRINCIPAL_RELATION_PARENT_ATTRIBUTE">
 <physicalAttribute name="memberof"/>
 </attribute>
 </attributes>
 </nameSpace>
 <nameSpace name="com.sap.security.core.bridge">
 <attributes>
 <attribute name="dn">
 <physicalAttribute name="*null*"/>
 </attribute>
 </attributes>
 </nameSpace>
 </nameSpaces>
 </principal>
 </principals>
 </attributeMapping>
 <privateSection>
 <ume.ldap.access.server_type>MSADS</ume.ldap.access.server_type>
 <ume.ldap.access.context_factory>com.sun.jndi.ldap.LdapCtxFactory</ume.ldap.access.context_factory>
 <ume.ldap.access.authentication>simple</ume.ldap.access.authentication>
 <ume.ldap.access.flat_group_hierachy>true</ume.ldap.access.flat_group_hierachy>
 <ume.ldap.access.user_as_account>true</ume.ldap.access.user_as_account>
 <ume.ldap.access.dynamic_groups>false</ume.ldap.access.dynamic_groups>
 <ume.ldap.access.ssl_socket_factory>com.sap.security.core.server.https.SecureConnectionFactory</ume.ldap.access.ssl_socket_factory>
 <ume.ldap.access.objectclass.user>User</ume.ldap.access.objectclass.user>
 <ume.ldap.access.objectclass.uacc>User</ume.ldap.access.objectclass.uacc>
 <ume.ldap.access.objectclass.grup>Group</ume.ldap.access.objectclass.grup>
 <ume.ldap.access.naming_attribute.user>cn</ume.ldap.access.naming_attribute.user>
 <ume.ldap.access.auxiliary_naming_attribute.user>samaccountname</ume.ldap.access.auxiliary_naming_attribute.user>
 <ume.ldap.access.naming_attribute.uacc>cn</ume.ldap.access.naming_attribute.uacc>
 <ume.ldap.access.auxiliary_naming_attribute.uacc>samaccountname</ume.ldap.access.auxiliary_naming_attribute.uacc>
 <ume.ldap.access.naming_attribute.grup>cn</ume.ldap.access.naming_attribute.grup>
 <ume.ldap.access.extended_search_size>200</ume.ldap.access.extended_search_size>
 <ume.ldap.access.server_name>XXXXXXXXX</ume.ldap.access.server_name>
 <ume.ldap.access.server_port>XXXXX</ume.ldap.access.server_port>
 <ume.ldap.access.user>XXXXXXXXX</ume.ldap.access.user>
 <ume.ldap.access.password>XXXXXXXX</ume.ldap.access.password>
 <ume.ldap.access.base_path.user>XXXXXX</ume.ldap.access.base_path.user>
 <ume.ldap.access.base_path.grup>XXXXXX</ume.ldap.access.base_path.grup>
 <ume.ldap.negative_user_filter></ume.ldap.negative_user_filter>
 </privateSection>
 </dataSource>
</dataSources>

CCM TREX indexing error

To CCM gurus,
Once in a while, I'd get indexing errors while trying to publish a procurement catalog. The errors would say something like:
1. Error when deleting TREX metadata for catalog ABC...
2. Error when creating the index for catalog XYZ...
3. Error in search index update; discarding existing changes
And then the catalog update is terminated. What we normally do is restarting the TREX server and then we can publish again.
My question is...can we resolve this without having to restart TREX each time? Is there a way to re-index TREX without restarting it?
Regards,
SN

Hi SN,
You can check the 'health' of the TREX indexes specific to CCM by use of report /CCM/CHECK_TREX (you need at least CCM 2.0 SP4 for this). In this report, if the index is either orange or red, it is not usable, if it is green it is fine. If the index is coloured red or orange, drill into this index and there will be some short text indicating what the problem with the index is. Once inside this index it can be deleted using the delete (trashcan) icon - in this case, a full publication is required to regenerate the index from fresh.
It may also be possible to use report /CCM/RECREATE_INDEX providing the index is still valid on the trex server.
Regards,
Jason

Index of EXIF-metadata from jpeg files by TREX

Hello,
I have the following scenario:
We have a central fileserver with a lot of marketing pictures. Our marketing people are looking for a solution to search pictures by data stored in the EXIF-metadata of the jpeg-files.
So I like to integrate this fileserver as a repository in KM, set up an index and let TREX do the search (as of note 663630 TREX can search the EXIF-Data of JPEG-Files).
As goodie I want to give the marketing people the possibility to browse through the pictures in an image gallery. This gallery should be consisting of a query-based taxonomy where all the pictures are sorted by special EXIF-data (e.g. name of the photographer).
Until now I have integrated the fileserver (as a FS-Repository) and create an index.
Before index creation I added the mime-type image/jpeg to the TREXValidMimeTypes.ini and restarted TREX.
After indexing the pictures could be found by its name, but the EXIF-data is not indexed.
Now my question:
Why TREX doesnt index the EXIF-metadata?
And how can I use the EXIF-data in an taxonomy?
System:
EP6.0 on WebAS 6.40 SPS16
TREX SPS16 Patch 2
KMC SPS16 Patch 2
Greetings from Berlin, Germany
Jens

Greetings to Berlin,
when triggered by KM, TREX will only index metadata that is known to KM as KM propertis.
I do not know in detail and am not at all sure, but you could try to create custom properties in KM that are called exactly like your EXIF-metadata, set them to "indexable", not fill them with values on KM side and then try again.
You may want to try this for just one of the EXIF-metadata as a test.
Even if that works somehow, the maximum result is:
- Property name existent in KM
- Property thus searchable an classifiable
- BUT property values will not show up in KM, as they will remain known only to TREX
Regards, Karsten

TREX: on SKPR07 "index possible" is red

Similar Messages

Maybe you are looking for