Hello,
I do not know if the following will help or not but just in case it might here is a doc I located that might apply. I know you have done some of the actions referenced in the doc however perhaps it might shed more light on the problem.
Also, sometimes turning on debug can give some clues to these document search issues. I'll put those instructions below too. If any of this is redundant, I apologize!
The Change and Impact Guide also might be helpful.
~dana
1st doc:
Filestore and Search Index location changes in Clarity v13
Summary:
There are two significant changes to the Clarity V13 upgrade process that directly affect the file store feature. These changes require action during the upgrade process to ensure that this feature operates correctly after the upgrade. These changes are necessary if the files are not stored in the database. If files are stored in the database then no action is required. Determining if files are stored in the database can be done by using the Clarity System Administration application. Login to the application and navigate to the Documents and Search link under the Properties tab. Review the Store Files in Database property.
If the database has not been used as the filestore repository , action must be taken. Failure to follow these steps can potentially lead to permanent loss of the file store contents. The changes are as follows:
1.
The upgrade process in Clarity V13 always installs to an empty destination folder. During upgrade, any files and folders that exist in the target install folder are moved to a new location before the new files are installed. If the file store folder is located in the Clarity runtime folder it will be moved along with the other Clarity content. If the file store is located anywhere outside the Clarity runtime folder (which is the recommended configuration), then the filestore location will not need to be moved or copied from the backup location.
2.
The file store and search index folder structures have been altered slightly to accommodate architectural changes in Clarity V13. This change requires action for all Clarity V13 upgrades, regardless of whether the filestore was located in the Clarity installation folder or not.
The course of action depends on two factors: where the file store was prior to upgrade, and the target install folder selected during the upgrade. The correction must be made immediately after the upgrade completes, prior to any files being added to the file store. Any files added to the file store before this correction is made must be manually preserved using the following steps:
1.
Use Clarity to retrieve the newly checked-in documents and save them to a temporary location on the file system.
2.
Perform the steps indicated by case 1, 2, or 3 below.
3.
Use Clarity to check the saved documents back into the Clarity file store.
4.
Execute the following commands from the <runtime>/bin folder:
‘admin search recreate-index-files’
‘admin search recreate-index-data’
Filestore and Search Index Correction Procedure
Before you start, ensure that a backup has been created of the filestore so that recovery is possible in the event of an unexpected problem. As noted in the previous section, if your document store has been used before completing this procedure, the newly added documents must be added back to the filestore after completing the following procedure.
The following scenarios illustrate the actions to be taken because of the changes cited above. Use the "File store location" and "Target install folder" to determine the correct course of action.
1)
File store location: The file store was located in the Clarity runtime folder prior to upgrade.
Target install folder: The existing (pre-upgrade) Clarity runtime folder was selected as the target install folder.
Prior to the upgrade process running, the file or index folder is in the <runtime> folder and the upgrade process has moved it to a folder called <runtime>
prev based on the chosen upgrade install option. The move has resulted in the file or index folder being located in the <runtime>prev folder. The file or index folder MUST be moved from the <runtime>_prev folder to another location because any subsequent upgrade attempt will delete this folder. Here are the steps to perform for this use case:
a.
If prior to the upgrade the file store location was <runtime>/filestore, copy or move the folders under <runtime>_prev/filestore to a new path:
<new directory>/filestore/clarity
where <new directory> is located outside of the upgrade resulting <runtime> directory (having the location outside of the runtime folder follows best practices) . Ensuring the folder is outside of the Clarity installation directory will also ensure that this process will not have to be repeated in the future when Clarity is upgraded again. Login to the Clarity System Administration application and navigate to the Documents and Search link under the Properties tab and change the Filestore Directory location to the new location. For example if the file store path is <old clarity install directory>/filestore then it needs to be modified to <new directory>/filestore. Note: ‘clarity’ should not be appended to the path in the CSA. This is added internally by the Clarity architecture.
b.
If prior to the upgrade the search index directory location was <runtime>/searchindex , copy or move the folders under <runtime>_prev/searchindex to a new path:
<new directory>/ searchindex /clarity
where <new directory> is located outside of the upgrade resulting <runtime> directory (having the location outside of the runtime folder follows best practices) . Login to the Clarity System Administration application and navigate to the Documents and Search link under the Properties tab and change the Index Directory location to the new location. For example if the file store path is <old clarity install directory>/searchindex then it needs to be modified to <new directory>/searchindex. Note: ‘clarity’ should not be appended to the path in the CSA. This is added internally by the Clarity architecture.
c.
Execute the following command from the <runtime>/bin folder:
‘admin search recreate-index-files’
‘admin search recreate-index-data’
2)
File store location: The file store was located in the Clarity runtime folder prior to upgrade.
Target install folder: A new, empty folder was selected as the target install folder.
Prior to the upgrade process running, the file or index folder is located in the <runtime> folder and the upgrade process produced a different folder called <new runtime> based on the upgrade install option to choose a different folder for the upgrade result than the current one. This has resulted in the file or index folder being located in the <runtime> folder. Here are the steps to perform for this use case:
a.
If prior to the upgrade the file store location was <runtime>/filestore, copy or move the folders under <runtime>/filestore to a new path:
<new directory>/filestore/clarity
where <new directory> is located outside of the upgrade resulting <runtime> directory (having the location outside of the runtime folder follows best practices) . Ensuring the folder is outside of the Clarity installation directory will also ensure that this process will not have to be repeated in the future when Clarity is upgraded again. Login to the Clarity System Administration application and navigate to the Documents and Search link under the Properties tab and change the Filestore Directory location to the new location. For example if the file store path is <old clarity install directory>/filestore then it needs to be modified to <new directory>/filestore. Note: ‘clarity’ should not be appended to the path in the CSA. This is added internally by the Clarity architecture.
b.
If prior to the upgrade the search index directory location was <runtime>/searchindex , copy or move the folders under <runtime>/searchindex to a new path:
<new directory>/ searchindex /clarity
where <new directory> is located outside of the upgrade resulting <runtime> directory (having the location outside of the runtime folder follows best practices) . Login to the Clarity System Administration application and navigate to the Documents and Search link under the Properties tab and change the Index Directory location to the new location. For example if the file store path is <old clarity install directory>/searchindex then it needs to be modified to <new directory>/searchindex. Note: ‘clarity’ should not be added to the path. This is added internally by the Clarity architecture.
c.
Execute the following command from the <runtime>/bin folder:
‘admin search recreate-index-files’
‘admin search recreate-index-data’
3)
File store location: The file store was located outside Clarity runtime folder prior to upgrade.
Target install folder: The target install folder is not relevant to this scenario. These steps must be performed for all upgrades with an external file store.
The file or index folder is not located in the <runtime> folder. Here are the steps to perform for this use case:
a.
If the previous file store folder path is now located at <some folder>/filestore, copy or move the folders under <some folder>/filestore to a new path:
<some folder>/filestore/clarity
b.
If the previous search index folder path is now located at <some folder>/searchindex, copy or move the folders under <some folder>/seachindex to a new path:
<some folder>/seachindex/clarity
c.
Execute the following command from the <runtime>/bin folder:
‘admin search recreate-index-files’
‘admin search recreate-index-data’
d.
No modification to the Filestore Directory or Index Directory properties is needed. These properties can be viewed from the Properties tab, Documents and Search subtab in the Clarity System Administration application Note: ‘clarity’ should not be added to the path in the CSA. This is added internally by the Clarity architecture.
Doc 2
Turn on debugging in the CSA for DMS
1. In the CSA click on the icons for Logs.
2. Next screen up near the top but under the word Services
click on Edit Configuration
3. Next screen scroll down to the Categories section and
click on Add Category
4. Next you will see at the bottom now, com.niku. Click on the
little arrow and choose com.niku.dms
5. Now in the column that says 'Appender' it should default to 'STDOUT'
and in the next column' Priority' click the arrow and choose 'Debug'.
6. Scroll down and click Save.