Search Index not working after archive is copied to another drive

[jneureut]

I have an archive on a network drive that was indexed and searchable. I zip it and copy it to another drive (PC, thumb drive ect) then extract the files there. I proceed to try and run a search from the new location and it says ” A text search index for this archive cannot be found. Would you like to create one now?” This search was working before I moved the archive to another pc. I don’t know why it is asking me to rerun the index which can be a long process.

Topic

[Support 1]

Thanks for reporting this behavior.

It’s possible that some file or folder names in the archive are too long for the target media where the archive was copied. Can you confirm that the archive sub-folder _index and contents in the copy match the original?

I look forward to your reply.

Regards,
Advansys Support

[jneureut]

I do not see an _index sub folder. The only folders I see under the archive are the media folders ie media-XX (where the X is a number of the media disks). Under the media-xx folders there are 3 folders _metadata, _viewer, data and a DiskX.info.xlm file. Under the data folder there are numbered folders that conatin the emails with fml extensions. That is all I have.

[Support 1]

Thanks for the detailed description of the archive sub-folders.

If the sub-folder _index is not in the copied archive, this explains why you get the message ‘A text search index for this archive cannot be found…’

If you look at the the original archive folder on the network drive, can you see this sub-folder? If so, it appears to have been excluded from the zipfile you created, or it could not be copied to the other drive.

I look forward to your reply.

Regards,
Advansys Support

[jneureut]

I see that in other archives that the _index folder is found under the last media-xx folder of the group. The archive I currently have on the network drive is missing this _index folder but I am still able to search the archive. How is this possible?

[Support 1]

Thanks for the clarification.

When the index is too large to be placed in the archive folder group, Indexer may move it to the ‘standard index location’ on the machine used to create the index. Since you have been able to search the network-based archive, I think your machine stores the index locally.

Have you tried to use the same machine to search the new copy of the archive? I would expect it to use the local index also for the copy.

To see whether the index for this archive is stored locally, please follow these steps:

• Open the file DiskX.info.xml using a plain text editor or a Web browser. The third line should look like this:

    <volume vol="1" archive-id="a37eb297-08e8-49a7-ba32-7caa6a31ce88" />

• Note the value at archive-id (‘a37eb297-08e8-49a7-ba32-7caa6a31ce88’ in the above sample).
• Use File Explorer to navigate to the following folder:

  C:Documents and Settings[Windows User Name]Local SettingsApplication DataAdvansysArchive To GoIndexes

• If this folder exists, does it contain a sub-folder matching the archive-id noted earlier? If so, you should find that it contains a sub-folder dat. In the last media-XX folder of the archive copy, create a sub-folder _index if it does not exist. Copy dat into this new sub-folder. You should be able to search the archive copy now.

I hope this helps.

Regards,
Advansys Support

[This message was edited by Support 1 on March 31, 2010 at 04:19 PM.]

[jneureut]

That was it! I created the _index folder under the last media-xx folder and then copied in both the dat and inf sub-folders found using your steps above and it works now.
Thanks again.

[Support 1]

That’s great news, thanks for letting us know.

We will ensure that the product documentation mentions this ‘standard index location’, if it doesn’t already do so.

Regards,
Advansys Support

[Author]

Replies