Changes to mail system not reflected in Archive2Go

Creator

Topic
July 29, 2011 at 2:02 pm #5102
tseabourn
Participant
It’s been a number of months since I’ve used Archive2Go. I am trying to use it again to archive some old email accounts, and when I attempt to use the software, it fails. Enterprise Mode appears to not to reflect changes made to the system since the last time it was used. For example, there is a new Groupwise post office that doesn’t appear, and the user I’m trying to archive has been moved to that post office. The Archive2Go system still shows this user to be part of the original post office. I presume this is why the archive is failing. What can I do to force Archive2Go to detect my Groupwise system the way it exists today?
Creator

Topic

Author

Replies
July 31, 2011 at 5:27 pm #9800
Support 1
Participant
Thanks for reporting this problem, which is a known issue.

When changes are made to the GroupWise eDirectory system you will need to refresh the view of the system that Archive To Go Creator shows. This is because Creator stores a copy of the system information in a local cache, to avoid a lengthy delay every time you view the system.

To refresh Creator’s System view, select a System, Domain or Post Office and press F5. You can also use the mouse to right-click, then select Refresh from the pop-up menu. Depending on your network topology, throughput and other physical factors, you may find it much faster to refresh selected Post Office objects instead of an entire Domain (or System).

The Refresh function should be more visible on the Creator dialog; we have recorded this issue in the enhancements list for the product.

Note: The pop-up menu includes an option to show the discovery log. You may find it useful to review the log before/after refreshing, to find out which, if any, system objects were inaccessible. This can happen for various reasons, eg. if there are multiple eDirectory Trees in your GroupWise system and you have not logged in to the Tree that hosts a particular Post Office.

I hope this helps.

Kind regards,
Advansys Support
August 1, 2011 at 2:09 pm #9798
tseabourn
Participant
Now that I’m able to see the new accounts, I am still unable to create an archive.

When I start the process, it displays PREPARING for just a moment, then displays FAILED. The summary log shows:

quote:

Creator general exception:

Advansys.Arctic.Auditing.LogException
at Advansys.Arctic.Auditing.AuditManager.x16eb53e98c3cc83b(AuditWriter xbdfb620b7167944b)
at Advansys.Arctic.Auditing.AuditManager.xbfc2f8d646f671db(AuditWriter xbdfb620b7167944b, Int32 xc0c4c459c6ccbd00)
at Advansys.Arctic.Auditing.AuditManager.x7b437f3c0ae7c2a0()
at Advansys.Arctic.Archiver.xedb094324a864cc0()
at Advansys.Arctic.Archiver.x378a375f240466f5(Int32 x8ff1a8790e426913, Int32 xb3e0cf0d6968c1c7, Boolean& x954deb06c639cd05)
at Advansys.Arctic.Archiver.x18dfca7c5fd2402f()

Any thoughts?
August 2, 2011 at 5:42 pm #9797
Support 1
Participant
Thanks for your detailed description of this new problem. It’s possible that this is the same problem discussed in Failed – Consult the documentation for more information. If you don’t find the resolution there, please send the summary and detail logs (zipped) to support@advansyscorp.com.

Kind regards,
Advansys Support
August 4, 2011 at 2:08 pm #9799
tseabourn
Participant
You’re a genius. That was it. Thanks!
August 4, 2011 at 4:33 pm #9801
Support 1
Participant
That’s great to hear, thanks for letting me know.

Kind regards,
Advansys Support
Author

Replies

Viewing 5 replies - 1 through 5 (of 5 total)

You must be logged in to reply to this topic.