Errors in index log

[clement]

Hi,

We have had reports that a few of our clients are having errors reported in the index log which reference an .xls file being in use. The file name is always different but the location is always the same. For example, this is the latest report:
System.IO.IOException: The process cannot access the file ‘C:Documents and SettingsUNHCRUserLocal SettingsTempadvfmlindexerDarfur_ CDF_ Strenghening well being of children (PS1).xls’ because it is being used by another process.
at System.IO.__Error.WinIOError(Int32 errorCode, String maybeFullPath)
at System.IO.FileInfo.Delete()
at Advansys.Arctic.Indexer.ArchiveIndexer.x615859b779dfa6c8(FolderAttributesHelper x8b5b49efcd08ae0a, ItemHelper xccb63ca5f63dc470, GWMessage x1f25abf5fb75e795, String x1a37a0209eb19332, Int32 xaa9f0e52733fc080, Boolean x7a77671c06dfd253, String xb7e6749facb89de8)

On another users computer, I deleted the file that was being referenced but the next time I ran the index process, the file reappeared. The user had not used this file in more than 6 months and nobody had it opened at the time of archiving/indexing.

Can you shed some light into this matter?

Thanks,
Sue

Topic

[Support 1]

Thanks for reporting this problem. Unfortunately we do not know the cause of this error, which seems to affect only .xls (Excel spreadsheet) files.

Please send samples of the .xls files (zipped) to support@advansyscorp.com. Note that Advansys treats all customer-supplied sample data as strictly confidential. Alternatively, please answer the following questions:

• Do the affected .xls files contain links to other documents (eg. Web addresses)?
• Do the affected .xls files contain plain text (eg. tabular data formatted as comma-separated values, ie. CSV)? You can see this by using a plain-text editor (eg. WordPad) to open the .xls file.

Was anti-virus software active during the indexing process? We recommend disabling any such software temporary while indexing takes place.

Which version of Indexer are your clients using? The error format looks like 1.5.0.3 or below. We recommend version 1.5.0.4, which minimizes the incidence of this problem. Anyone can obtain this version by following the directions in 1.5.0.4 updates for Indexer and Viewer.

Do you see these errors with Indexer 1.5.0.4? If so, is there a different pattern to it, eg. fewer errors per log file? Detailed information about your results will help our engineers to understand and fix this behavior. Please send sample log files (zipped) to support@advansyscorp.com. For all the machines where these errors come up:

• Which version (and service pack) of Microsoft Windows is installed?
• Which version of Microsoft Office is installed?
• Which version of Microsoft Excel is installed?

I look forward to your reply.

Regards,
Advansys Support

[This message was edited by Support 1 on April 08, 2010 at 07:33 PM.]

[Author]

Replies