• Creator
    Topic
  • #5047
    George
    Participant

    Trying to complete an indexing of an archive, and I receive the following message:

    2009-11-02 10:26:37.421-05:00 ______________________________________________________________________
    2009-11-02 10:26:40.718-05:00 [E] General Indexer exception:

    System.ArgumentNullException: Value cannot be null.
    Parameter name: path2
    at System.IO.Path.Combine(String path1, String path2)
    at Advansys.Arctic.Indexer.IndexSizeEstimator.x16393c78e0562e3f()
    at Advansys.Arctic.Indexer.IndexSizeEstimator..ctor(String xb366e21af75d35f0, DirectoryInfo x8bd2ea1eff5a0f7f)
    at Advansys.Arctic.Indexer.ArchiveIndexer.xc1d461672e5161e1()
    at Advansys.Arctic.Indexer.ArchiveIndexer.x1d33084d33a679dc()
    2009-11-02 10:26:40.718-05:00
    ________________________________

  • Author
    Replies
  • #9669
    Support 1
    Participant

    Thanks for reporting this problem, which I think has not been reported previously.

    Which version of Indexer are you using? You can find out by clicking About… on the Indexer dialog. This featured topic has details about obtaining the latest update.

    Please send the contents of the _metadata folder (zipped) to support@advansyscorp.com. The exported metadata contains only Sender, Recipients, Subject and Date for each message; it contains only Display Name and Email Address for each contact. If the Indexer log contains more information than that quoted in your post, please attach the log file to your email.

    Regards,
    Advansys Support

    #9667
    Support 1
    Participant

    It seems that this error will occur when attempting to index an archive that is incomplete. That is, when the archive was created the process was cancelled manually or stopped due to an error. You can review the archive log summary (at the end of the log, beginning with a marker line) to check whether the process completed. If the summary is missing then the process did not complete.

    We plan to update Indexer for the forthcoming release of version 2.0, so that it is not affected in this way by an incomplete archive.

    Regards,
    Advansys Support

    #9670
    George
    Participant

    The archive process was not completing due to excessive emails in a given folder, in the case the Mailbox/Inbox. The user had approximately 80,000 messages in there. I broke them out by year and ran the Archive to Go process. I did go back through the XML to put the folders all under the Mailbox, even though it wasn’t necessary.

    I was then was able to index it properly.

    #9668
    Support 1
    Participant

    Thanks for the additional information. 80,000 is an extraordinary number of messages for a single folder.

    Is it common for your GroupWise users to have more than 5,000 messages in a single folder (not necessarily Mailbox)?

    Which version of GroupWise were you using with Archive To Go when it failed to process all 80,000 messages? We know that older versions of GroupWise did not report the correct number of messages to third-party applications when the number exceeded 4,960. It is not clear whether later versions of GroupWise are more robust when processing larger numbers per folder.

    I will ensure that our engineers review this scenario. Archive To Go should (for example) display a warning about unprocessed folders when an attempt is made to index the archive.

    I look forward to your reply.

    Regards,
    Advansys Support

Viewing 4 replies - 1 through 4 (of 4 total)
  • You must be logged in to reply to this topic.