log file – errors listed

[Brandon]

“Archive is ready to go” which archived 53864 and found 53865. I’ve checked the log and see a number of errors, one in particular “21,417 contain one attachement which is not available”. So when the user calls up any one of those attachements, they will not be available? There are other errors but not sure what i’m looking at or what could be wrong in the archive to produce this. Any info would be helpful.

I copy the users archive (ofxxxarc folder) to c:temp and run from there. Here is the log:

Product: Advansys Archive To Go, Version: 2.0.0.3, Date: 2010-05-26T16:50:04
Operating system: Windows XP, Version: 5.1.2600.196608
Runtime: Microsoft Framework for .NET, Version: 2.0.50727.3082
Client: GroupWise, Version: 8.0.1, Date: 2009-08-28T05:53:58
Account access mode: Local
Account type: User
Account: xxxxxxx, Mailbox: Online
Include main account: Yes
Include personal address books: No
Include Trash folder: No
Include incoming shared folders: Yes
Include newsgroup folders: No
Include RSS folders: No
Exclude empty folders: No
Include message properties: No
Include items marked Private: Yes
Include hidden items: Yes
Home folder alias:
Include primary native archive: No
Include secondary native archive: C:Temp
Media optimization: Single Layer DVD (4,403 MB)
Output folder:
Build index: No
______________________________________________________________________
Account name:
GroupWise personal archive: No
[Warning] Cannot load file “TEXT.htm”: 231 Byte(s)

Folder: , Messages archived: 7 (7 found)
______________________________________________________________________
Folders archived: 154 (160 found, 6 excluded, 46 empty)

Archive failure summary:
Main Account, Folder: ” “, Messages archived: 2 (3 found)

Messages archived: 53,864 (53,865 found)
Contacts archived: 0 (0 found)

53,865 message(s) were archive candidates, but only 53,864 were archived.
Please check the log for details of messages that could not be archived.
4 message(s) contain at least one key property which is not available.
21,417 message(s) contain at least one attachment which is not available.
1,165 message(s) contain at least one attachment which could not be saved.
74 message(s) contain an invalid Mime.822 attachment.

Completion: Warnings (check log entries marked as exception [E] or warning [W], [Warning])

Topic

[Support 1]

Thanks for reporting these errors.

> “21,417 contain one attachement which is not available”.
> …
> So when the user calls up any one of those attachements, they will not be available?

Yes. Note that the log entry states ‘at least one attachment… is not available’. Other attachments in a single message may be available. It is possible that for some of these 21,417 messages, the unavailable attachments are not important, eg. Mime.822 or some other ‘system’ attachment.

An attachment may be unavailable because it is very large and cannot be loaded into the machine’s available memory, or for some other reason.

[I] [Warning] Cannot load file “TEXT.htm”: 231 Byte(s)

The next log entry should show the related error. This attachment is very small, so it is probably not a machine memory error.

Unfortunately, without looking at the complete log, it is difficult to say what has caused this problem. You may wish to send the log (zipped) to support@advansyscorp.com for us to analyze.

> [I] 1,165 message(s) contain at least one attachment which could not be saved.

This means that Archive To Go requested GroupWise to save these attachments but GroupWise was unable to do so. It could be due to some data corruption in the GroupWise message database, or due to some other reason.

We tend to see more problem reports with GroupWise personal archives.

In general we recommend running a thorough GWCheck (Fix Structure and Contents) on the GroupWise mailbox and personal archives prior to commencing an export. Also, we recommend updating your GroupWise client to the latest patch; for 8.0.1 I believe the release date is 8 January 2010.

I hope this helps.

Regards,
Advansys Support

[Author]

Replies