Grant Botes

[Grant Botes]

Hi – thanks for this detailed reply. For now, I will keep using Full Sync.

Kind regards,
Grant

[Grant Botes]

Hi – sorry for my slow reply on this issue. Work pressure! I’m sending an email with the logs, as requested.

Because of the severe size restriction my employer has recently imposed on GroupWise mailboxes, I want to do a partial sync every day. I want to delete emails that are not essential or have been resolved from GroupWise but use partial sync to make sure they still appear in my archive. I was only able to create one archive using partial sync; subsequently any attempt to run a partial sync against that archive failed. I was able to run a full sync when I tried that instead.

I was hoping to use partial sync rather than full sync so that I wouldn’t have to resort to using GroupWise’s archive facility – in other words, I would like to maintain only an A2Go archive, using partial sync to archive all my emails, and I want to keep my GroupWise mailbox small by deleting emails once I’ve dealt with them. I hope that makes sense.

Up until now, I have been using full sync only. But that I understand that means I need to maintain a GroupWise archive, too, rather than just delete emails otherwise delete emails will also be deleted from my A2Go archive (yes?)

Yes, the “Archive To Go has stopped working” message appears every time I attempt a partial sync update, no matter how many times I attempt it. Full sync continues to work perfectly.

Kind Regards,
Grant

[Grant Botes]

Hi

I’m happy to provide positive feedback – Archive to Go 4.0 exported my GroupWise emails successfully. It did display warning messages, too, and said one message was not indexed but my archive is searchable and my emails are viewable.

Thanks, and kind regards,
Grant

[Grant Botes]

Awesome! Thanks very much for this helpful answer.

Kind regards,
Grant

[Grant Botes]

Awesome! Thank you for this helpful answer.

Kind regards,
Grant

[Grant Botes]

Hi Advansys Support

Many thanks for your very prompt response. Your answer has helped me to some extent. I think one of the issues is that my organisation uses McAfee protection, and I see from the logs McAfee has complained about the Advansys autorun.inf file and blocked it.

I’ve downloaded the Archive to Go 4.0 beta, and am busy running a few tests with that. I’ll know more after that, I think, as it installs from a .msi file which McAfee will feel safer about.

There were messages on the Wizard page when it completed, but I don’t feel that in itself ought to be a reason why a multi-gigabyte GroupWise archive should fail to index. The archive was built well enough even though the log shows some errors and warnings – I would expect the index engine to index what it can under those circumstances.

Anyhow, I’ll post an update here after 4.0 completes. It’s a big archive, and took about 8 hours using 3.1

Kind regards,
Grant

[Author]

Replies