Errorcode 2030 while creating Index

Question

Hi,
I am try to create an index for the first time and am not able to, because of the following error:
Index could not be created; creating index failed: general configuration error (Errorcode 2030)
Can you tell me if there is any place where I can lookup errorcodes and their descriptions?
Thanks
Raj Balakrishnan

Answer 1

Error codes and messages of TREX 6.0
OSS Note 649574 you can find a attach file in which explain you these message error.
Patricio.
List of TREX 6.0 Error Codes and Messages
(including hints for solving some common problems)
0000 no error No errors occurred. The process was completed successfully
0001 multiple operations failed detail provided in a list This problem is mostly caused by HTTP problems when indexing or synchronizing. You must check whether the documents processed are actually available
0004 Document to delete/update was not found The document that was prepared for deindexing or an incorrect document ID or document name. You must check whether there is a document in the index or on the harddisk (as URL) with the corresponding ID. For non Portal scenarios this error means: "document can not be found". If you use Content Server please check this document for consistency.
0008 index is corrupted. Must be deleted/repaired by hand An error occurred when the system tried to delete the index. The corresponding entry was deleted from bartho.ini, but the index still exists. Solution: 1. Stop the TREXServices. 2. Delete the index directory and the entries in bartho.ini, TREXIndexServer.ini and TREXTcpipClient.ini manually. 3. Start the TREXServices 4. if necessary delete index in R/3 system (for non Portal scenarios) and clean tables. 
0010 not enough space available for index creation There is no disk space available for creating a new index. You must chose another disk for the index. (The trace files might be occupying to much diskspace. If so, they have to be deleted.) 
0011 specified language is unknown or not supported You must check whether the chosen language is supported by TREX and whether the language ID has been entered correctly. You must check also if these languages have been chosen correctly during the TREX installation. 
0012 directory creation failed An index with the same name has already been created, and an error occurred when the index with the same ID was created again. The old index was not correct deleted :empty index directory still exists. Solution: 1. Stop the TREX Services. 2. Delete the index directory manually. 3. Start TREX Services again. 
0013 directory removal failed The index directory could not be deleted correctly. This may be because there is a file missing from the index directory, or the index might be locked by another process. Solution: 1. Stop the TREX Services. 2. Delete the index directory and the entry in bartho.ini, in TREXIndexServer.ini and in TREXTcpipClient.ini manually. 3. Start the TREX Services 4. if necessary delete index in R/3 system (for non Portal scenarios) and clean tables. 
0014 unknown or unsupported data type This may be because the document contains a data type that is not supported.
0016 an operation has failed on a file (create, delete, copy, move...) This error occurs when the system tries to delete an index that is locked by another process. Solution: 1. Stop the TREX Services. 2. Delete the index directory and the entry in bartho.ini,TREXIndexServer.ini and in TREXTcpipClient.ini manually. 3. Start the TREX Services 
0018 a received argument has an invalid value This problem can be occurred for example if Search Request is not correct.
0020 unspecified win32/unix system error The error occurs when the system tries to index an index that has already been partially deleted. Solution: 1. Stop the TREX Services. 2. Delete the index directory and the entry in bartho.ini,TREXIndexServer.ini and in TREXTcpipClient.ini manually. 3. Start the TREX Services 
0022 automatic index optimization failed This error can occur when another document is indexed by a URL in an index for an existing document. Afterwards the index is no longer available. Solution: 1. Stop the TREX Services. 2. Delete the index directory and the entry in bartho.ini,TREXIndexServer.ini and in TREXTcpipClient.ini manually. 3. Start the TREX Services 
2001 Multiple operation failed, detail is provided in a list This problem is mostly caused by HTTP problems when indexing or synchronizing. You must check whether the documents processed are actually available. 
2003  The error normally occurs when you try to create a new index with the same index ID as that of an existing index. If the index is not available in SAP_RETRIEVAL_PATH \Index, you must check whether there is an entry for a corresponding index in bartho.ini, TREXIndexServer.ini 
2004 Document to delete/update was not found The document that was prepared for deindexing or an incorrect document ID or document name. You must check whether there is a document in the index or on the harddisk (as URL) with the corresponding ID. For non Portal scenarios this error means: "document can not be found". If you use Content Server please check this document for consistency.
2007 index does not exist This error occurs when you try to delete an index that does not exist (or (de-) index some document in this index). The following points must be checked: Is the name of the index correct? Is there a subdirectory with the same name in SAP_RETRIEVAL_PATH\Index? Is there a matching entry in bartho.ini, TREXIndexserver.ini and in TREXTcpipClient.ini? 
2011 Document language is unknown or not specified Check whether the chosen language is supported by TREX and whether the language ID has been entered correctly. (You also need to check that the language in question was selected when TREX was installed). 
2503 Direct load, no queue server existing It should be checked , if the TREXIndexServer.ini has the proper entry for the Index Server, Queue Server and the IndexId. If it is necessary, this entries have to be added manually or from the backup version. 
2960 The index server (for the specified indexes) cannot be determined check if TREXNameServer should be used, properly configured and run.
2982 A communication error occured, with the TREX TcpIp Server Check if TREXIndexServer is running.
2988 Missing argument Possible reason: search query is not correct
2990 codepage error Possible reason: Codepage is not supported. 
2998 dll can not be loaded Possible reason: in R/3 system check if in Transaction SRMO during the creation of SSR was selected DRFUZZY as searchengine. 
6001 QS error: index not found Possible reasons: Index was deleted not complete (queue is still exist), or queue was created from TREXQueueClient. Solution: delete Queue through TREXQueueClient 
6002 QS error: queue not found The queue has been deleted manually or was never created.
6009 QS error: no connection to QueueServer The queue server did not start. Also check whether the TREXIndexServer.ini file has appropriate entries for the index server, queue server, and index id. If necessary, enhanced these entries manually or using the back-up version. 
6017 QS error: queue not deleted The queue can not be deleted. The TREX index server, preprocessor, and queue server must be stopped and the queue index must then be deleted manually. 
6021 QS error: queue exists The queue wasn't deleted when you deleted the index. This error occurred when you tried to create an index with the same ID. You have to delete the entries from this index from TREXTcpipClient.ini. 
6401 HTTP Status Code 401 : Unauthorized Possible reason: TREX-user has no permissions for this document
6403 HTTP Status Code 403 : Forbidden Possible reason: TREX-user has no permissions for this document
6404 HTTP Status Code 404 : Not Found Possible reason: the document is not available
6806 Preprocessor: filter error check if the document has correct mime-type and if necessary test with the filter.exe
6906 Attribute engine index not found Subfolder attribute for index was not created with the index. Solution: 1. Stop the TREXServices. 2. Delete the index directory and the entries in bartho.ini, TREXIndexServer.ini and TREXTcpipClient.ini manually. 3. Start the TREXServices 4. if necessary delete index in R/3 system (for non Portal scenarios) and clean tables. 
6915 UNKNOWN_ATTRIBUTE (AttributeEngine) check the search query. Requested attribute is not available in the index.
Message was edited by: Patricio Garcia