This is a somewhat unusual configuration, and not one we have tested.
How are the Windows messaging services configured? Do you run the GroupWise and Outlook clients at the same time? Is the Outlook client drawing data from the GroupWise back-end?
Does Archive to Go work if you shut down the Outlook client? If so, is it necessary to have the Outlook client running while creating an archive?
I must clarify, Outlook is not running at the time. I received an outlook error at the time of the crash. The Groupwise Client was OK, but this same issue would occur when we clicked on the Import Outlook button in Groupwise. We then had the same issue on a separate PC with the same configuration. We merely want to import the PFT file directly, and would not want to use outlook at all. Thanks, -Nick
Thank you for the additional information. I assume you are refering to the Personal Outlook Migration Pack solution when you mention the ‘Import Outlook button’ in GroupWise?
This is not an issue with Archive To Go or the Outlook migration utility, rather it most likely relates to the way you have setup the Windows Messenging Services as they relate to GroupWise and Outlook. It sounds like you may have Outlook using GroupWise services, or GroupWise using GroupWise services.
Running GroupWise and Outlook on the same machine can be somewhat of a black art. When developing the Outlook migration pack, we had the most success by creating two messaging profiles – one that contained only GroupWise services, the other using only Outlook services. We also ensured the ‘prompt for which service to use’ option was always selected. You’ll find more information about setting this up in the Outlook Migration Pack users guide.
