Support 1

[Support 1]

Thanks for reporting this problem.

I think one or more XML files used by A2Go have become corrupted, perhaps because of a forced reset of the machine. I suggest that you follow the directions below:

• Delete the file settings.xml in the following folder:

  C:Documents and Settings[Windows Username]Application DataAdvansysArchive To Go

  Note that the next time you run Archive To Go Creator, the settings from previous usage will have been lost, but they are easily set again.

• If you get a similar error, try also deleting the file systems.xml in the same folder, before running Creator.

  Note that the next time you run Archive To Go Creator, the GroupWise systems defined from previous usage (Enterprise mode) will have been lost. You will need to redefine all systems if Enterprise mode is required.

Please let us know how you go.

Regards,
Advansys Support

[This message was edited by Support 1 on September 08, 2009 at 06:06 AM.]

[Support 1]

You wrote:

>cannot view the forwarded embedded messages.

Please describe what happens when you try this, eg. do you see an error or some other unexpected behavior?

I wonder if the problem is that the PC with GroupWise build 976 does not have Advansys Message Viewer installed? This free application is required for viewing .FML files that are outside of an Archive To Go archive. It is not the same as the Archive To Go Viewer.

Note: By default, Archive To Go Viewer will add the following advisory text to a forwarded message that includes an FML attachment:

quote:

---

Download a viewer for the attached FML file from
http://www.advansys.info/advansys-message-viewer.htm

---

You can find more information on this in the Viewer guide page 16, Forward and Reply.

I look forward to your reply.

Advansys Support

[Support 1]

Thanks for reporting this problem.

You wrote:

>One pc with GroupWise client ver. 7.0.3 build 1068 dated 09/06/2008
>can successfully view the forwarded embedded messages.
>Other pc with GroupWise client ver. 7.0.3 build 976 dated 08/03/2008
>cannot view the forwarded embedded messages.

Are these forwarded embedded messages in the same or different GroupWise accounts? When you forwarded the messages (using A2Go Viewer), was GroupWise logged in to the same account from which the messages were originally archived? If so, had the original messages been deleted from the GroupWise mailbox?

It may help us to understand the problem if you send sample messages (forward as attachments please, to support@advansyscorp.com): one from build 976 (cannot view), one from build 1068 (can view).

I look forward to your reply.

Regards,
Advansys Support

[Support 1]

Thanks for your enquiry.

Could you describe how the enumerated emails might be used, please? We are not sure of the best answer to your question; it may help if we know how you intend to use the enumeration in practice. In addition, how might a watermark/stamp function as a kind of enumeration?

Each message has an ID that look like this: 7B20450A.Acme.AcmePO.100.3136169.1.16F3F.1

This value is stored as the name of each archived message file (in the data subfolder of the archive folder) and in its referencing index file.

An index file (eg. 00000001.xml) represents the items archived from a specific GroupWise folder. Index files are stored in the _metadata subfolder of the archive folder, and are referenced in mailbox.xml, which is an index of the GroupWise folders included in the archive.

Regards,
Advansys Support

[Support 1]

Thanks for your enquiry, and sorry for the delay.

Archive encryption (in addition to password protection) and incremental archiving (appending to an existing archive) are features that we do plan to add to Archive To Go. At this stage we anticipate that these features may be available by Q1 2010.

In the meantime, we strongly recommend that you protect archives which contain sensitive information by using generic disk encryption software, eg. TrueCrypt.

On the issue of appending, it may suit your organization to archive periodically, by date range. For example, you could create distinct archives for 2008, 2007, etc. instead of a single archive that is potentially huge and time-consuming to create. While it is not possible to search across multiple distinct archives at present, this is a feature that may be added to the Finder tool. And it’s likely that the incremental archiving feature will be capable of merging several distinct archives into a single archive.

Note: As a rough estimate, it takes around 1 hour to archive 3,500 messages. This rate can vary dramatically, depending on network latency and throughput, disk latency, available RAM and virtual memory, among other factors. We expect that version 2.0 will be substantially faster; at this stage it is likely to be available in Q4 2009.

Regards,
Advansys Support

[Support 1]

Thanks for trying the language change. Did you restart the machine before trying again with Creator?

It seems the error “The application failed to initialize properly” can occur for a range of reasons. It may help if you review the discussions there for a possible solution, since no other Archive To Go user has reported this as a persistent problem.

In addition, please provide the following information:

• The specific error number (eg. cchimera above noted the number “0x0000142”).
• Your product and version of Windows: to find out with File Explorer, right-click “My Computer” and select Properties.
• The full name of each installed product starting with “Microsoft .NET Framework”, as listed in Add or Remove Programs, in the Windows Control Panel.
• The version of Archive To Go. To find out, navigate to the installation folder using File Explorer; this is usually:

  C:Program FilesAdvansysArchive To Go

  Right-click the file “a2goengine.exe” and select Properties, then go to the Version tab.

• Items listed in the Windows Event Log associated with “CSC.exe” or “a2goengine.exe”. View the log immediately after starting Creator and after seeing the error, as follows: in the Windows Control Panel, double-click Administrative Tools, then Event Viewer. In Event Viewer, select Application to display a list of events. Double-click an event to see a detailed description about the event.

I look forward to your reply.

Regards,
Advansys Support

[Support 1]

Which language is selected for non-Unicode programs on your machine? You can find out by opening Regional and Language Options in the Windows Control Panel. Go to the Advanced tab, where you’ll see the selected language in the upper area.

If the language is other than English (United States) try changing it temporarily to see if it makes a difference.

I look forward to your reply.

Regards,
Advansys Support

[Support 1]

ghitelj,

Thanks for letting us know. Other users of Archive To Go have confirmed that the FTF prevents the ‘Setup Error’.

Regards,
Advansys Support

[Support 1]

This message has been replied to by direct email.

Regards,
Advansys Support

[Support 1]

Novell has confirmed there is a defect in GroupWise 7.0.3 which causes a crash upon accessing phone messages. Novell has indicated that 7.0.4 will fix the defect. In the interim, Novell has released a public FTF (field test file) that is intended to fix the defect with phone messages. You can download it from:

http://download.novell.com/Download?buildid=1zy1s7M1Vwc~

Note that, if you have not already done so, you will need to install the 7.0.3 HP3 patch before applying the FTF. You will find a link to the 7.0.3 HP3 patch here:

http://download.novell.com/index.jsp?tab=patches&page_num=1&families=2650&keywords=&search_type=&search=Search

Please try archiving again with the FTF installed. I look forward to your reply.

Regards,
Advansys Support

[This message was edited by Support 2 on August 24, 2009 at 05:16 AM.]

[Support 1]

Thanks for sending the log file details.

As far as we can tell, this Setup Error is an obscure behavior of the .NET Framework, that can occur in various circumstances.

Our engineers are investigating this problem, and we will post here when we have any new information. We may need to set up a remote debugging session on your system; if so, we will contact you by direct email.

Regards,
Advansys Support

[Support 1]

Thanks for the additional information.

The current release build of Archive To Go is 1.5.0.3. Its Readme and user guide state that it requires version 1.1 or above of the Microsoft Framework for .NET. I suggest installing 1.1 before trying again.

>I believe I started having problems with this when I trialed and
>Advansys email merge and then uninstalled after the trial period.

Are you referring to the Personalized Emailer solution for Advansys Formativ?

I look forward to your reply.

Regards,
Advansys Support

[Support 1]

Thanks for reporting this problem. Unfortunately there is no fix available yet.

Would you consider trying out a special diagnostic version of the Viewer? This will assist our engineers in fixing the problem.

Out of interest, for approximately how long (days or weeks) had the machine been running when this error came up?

Regards,
Advansys Support

[Support 1]

Thanks for reporting this behavior.

We have archived a number of our mailboxes that contain phone messages; none of these failed or logged any problem to do with phone messages. We know that other customers also have successfully archived mailboxes that contain phone messages.

What are the reasons why you believe that phone messages are causing the failure to archive?

Do you see an error displayed? If so, please send a screen shot to support@advansyscorp.com.

I look forward to your reply.

Regards,
Advansys Support

[Support 1]

Thanks for your enquiry.

For GroupWise 8 you will need to update Formativ to the current beta release (2.0.2). Details on how to obtain this update are available on this forum in the featured topic Formativ 2.0.2 (Beta) available now.

Regards,
Advansys Support

[Author]

Replies