Support 2

[Support 2]

Hi Eric,

Thanks for the confirmation. As mentioned via direct email today, the engineering team has been able to replicate the error, which occurs when the selected secondary archive path is invalid. We are improving the error handling for this condition in Archive To Go 3.0, which is in the final coding stage.

Now we need to identify why Archive To Go thinks your secondary archive path selection is invalid.

Kind Regards,

Advansys Support

[Support 2]

Hi Eric, we will write to you directly to help isolate the issue.

Kind Regards,

Advansys Support

[Support 2]

Hi Eric,

Thank you for your post. As you’ve been using Archive To Go successfully for a long time, it is likely that something has changed within the environment in which Archive To Go is executing. Do you know what may have changed recently which could coincide with this outcome?

You could try to upgrade from Archive To Go 2.0.0.4 to the current release of 2.0.0.7, which introduces another variable, although this should not matter. Ultimately something within your workstation or GroupWise environment has changed, most probably the workstation. Can you try installing 2.0.0.7 and running it on another workstation?

Could you please send the detailed log file from an archive export which fails? The detailed log file is in the exported archive’s main folder, for example, a folder named bsmith archive. Please send it to supportATadvansyscorp.com, where AT should be replaced with @.

Kind Regards,

Advansys Support

[Support 2]

Thanks for the question and including the reason you needed this feature. It’s great that you found the work-around, which is the way it needs to be done currently. We have noted the use-case and will consider adding a feature which would enable deletion of messages from the Archive To Go Viewer application.

Kind Regards,

Advansys Support

[Support 2]

Just for records purposes, the reason why the license file did not work is that for some unknown reason the license file had become corrupted when forwarded from a partner’s smartphone.

A resend of the original license file solved Jan’s problem.

Kind Regards,

Advansys Support

[Support 2]

Hi Jan,

Sorry for any inconvenience and we’ll look into it and respond to your direct email. This is a very unusual issue and should hopefully be able to be resolved quickly.

Kind Regards,

Advansys Support

[Support 2]

Hi Jonathan,

Thank you for your post and your feedback, which is much appreciated. As we don’t have access to an Exchange server environment, we cannot reproduce the problem in-house. Are you able to send us a screen cast (perhaps using Jing, which is free from TechSmith at http://www.techsmith.com/jing.html) or screen shots of what the Exchange contacts look like in Outlook and the equivalent converted GroupWise contacts?

Are you able to send some example Outlook Contacts & emails to supportATadvansyscorp.com (please substitute AT with @)?

For the messages which do not convert correctly, is there any other field in the original Outlook message which contains an SMTP style address?

Kind Regards,

Advansys Support

[Support 2]

Yes, that is correct, all help information is in the user manual.

Kind Regards,

Advansys Support

[Support 2]

Thanks for the additional background. Sorry, in that case we do not have any solution for your needs.

Kind Regards,

Advansys Support

[Support 2]

In what form do you have the GroupWise data? A remote or caching user’s mailbox files and/or GroupWise personal archives? Do you have the user passwords?

We have previously offered data conversions where customers provide the GroupWise personal archive data and we convert it into portable Archive To Go archive format and Outlook PST file format. In addition to the use of Advansys Archive To Go Creator and Advansys PST Creator, this process uses a working GroupWise system and knowledge of how to graft existing data into the system.

Kind Regards,

Advansys Support

[Support 2]

The Advansys Message Viewer works for GroupWise messages which are already exported by the Advansys Message Saver software, which saves the GroupWise messages in the Advansys FML file format.

Are you attempting to view Advansys FML files?

[Support 2]

Hi, the help files or user documentation is installed with the software. What are you trying to achieve with the software you’ve installed?

Kind Regards,

Advansys Support

[Support 2]

Hi L.P.,

Indeed it is strange that the applets work on another server. Unfortunately these type of access violations are very difficult to isolate, particularly on a Windows 2003 server which we do not officially support. We cannot find any information on hand which could help you isolate the cause.

Very sorry we cannot be of more assistance in this case.

Kind Regards,

Advansys Support

[Support 2]

quote:

System.Windows.Forms.ImageList.ImageCollection.get_Item(Int32 index)

Hi Mike, thanks for your report. Researching our records suggests this specific error has not been reported previously, which may indicate a GroupWise archive data corruption. Which of the following steps have you tried from the suggestions in the forum post below:

http://www.advansyscorp.com/forums/topic/2021043902/ ?

We will write to you via email to request the full log files.

Kind regards,

Advansys Support

[Support 2]

Unfortunately the full path is not accessible via the search results. There is a way to check, which is outlined below. Although it’s cumbersome, it may be of some use to you.

• In the search results, open the message of interest.
• Switch to the Properties tab in the message view.
• Find the message file path, which will look like: N:engSupport Archivemedia-01data000001d739F59406.GWHQ.MOSMAN.100.0.1.E64A6FE8.1.fml.
• Copy the Archive To Go archive folder location name for this message, in the example above, 000001d7.
• Open the mailbox.xml file in an editor, such as Notepad or Notepad++ (recommended); the file will be located in the medtadata folder, such as N:engSupport Archivemedia-01_metadatamailbox.xml.
• Search for the folder name, 000001d7 within the mailbox.xml file. Once the location is found in the XML, you will see the target folder’s context within the mailbox folder hierarchy.

I realize this not efficient but I hope it helps achieve what you need.

Kind Regards,

Advansys Support

[Author]

Replies