Support 2

[Support 2]

Hi,

This is not a usual error and does not have an obvious cause. We need to gather more information.

Has it been working on any other workstations or on the same workstation prior to reinstallation of A2G?

If it has worked previously, we need to understand what else may be different between the successful operating and the new installation environment.

Some variables may be related to the GroupWise Client installation (such as Admin API used by A2G for accessing the primary domain) and perhaps even the NetWare Client.

Have you tried reinstalling the GroupWise Client?

Do you have multiple eDirectory Trees in your system?

Regards,

Advansys Support

[Support 2]

Sorry, Archive To Go is not a mobile device synchronization product.

For other Novell Partner Products, see http://www.novell.com/partnerguide/section/468.html.

Regards,

Advansys Support

[Support 2]

No, sorry at this stage you cannot export just the GroupWise native archive. This is certainly on our enhancement list for a future version.

Regards,

Advansys Support

[Support 2]

Sorry we missed it in your post the first time round but our minimum specification for the GroupWise Windows Client is 6.5.3. Before any further troubleshooting can proceed, please upgrade the client to 6.5.3 or higher (the latest being 6.5.6).

We hope the upgrade will solve the problem.

Regards,

Advansys Support

[Support 2]

As you would be aware from past correspondence, we cannot reproduce this problem in-house nor do we yet know of another customer with the same issue.

As correspondence has started via direct email, we will continue to deal with this issue via email. If a resolution is found which may be beneficial to other Stationery users, we will post an update to this thread.

Regards,

Advansys Support

[Support 2]

In short, we don’t know because we’ve never tested Archive To Go with this configuration. Technically the GroupWise APIs we use do not provide the capability to distinguish between a live and restored PO area, it just exports from what A2G believes is the currently selected and authenticated user’s account.

If possible, you need to find an external method to isolate the live mailbox access from Archive To Go while allowing access to the restored account.

Would a date filtering option be of assistance in this case?

We will log your requirement for review in future research & development.

If you find a practical approach, it would be most appreciated if you could let us know.

Regards,

Advansys Support

[Support 2]

As this is a low-level error message which can have multiple causes, such as GroupWise data store corruption issues, there is no universal solution.

Data related issues can sometimes be resolved through a thorough GWCheck process. Difficult ones may need to be isolated or bypassed using the start folder troubleshooting facility mentioned in the Archive To Go Creator guide.

More information may be available in the Details of the exception dialog which displays when the error occurs. Could you please copy these details and send them to support@advansyscorp.com for analysis.

Regards,

Advansys Support

[Support 2]

We’ve seen this error on one machine, which happened to be an in-house system. While we did not discover the exact reason why this workstation installation varied from others, the problem was tracked down to the current directory changing from the program directory during the archiving process. This meant that Creator could not locate the Indexer at the end of the export and resulted in the error you describe.

This has been resolved in Archive To Go 1.1, which is scheduled to be available within the next few weeks.

Regards,

Advansys Support

[Support 2]

Thanks for your question. While the archives are displayed separately, using Finder you can search across all exported archives and the main mailbox.

We will log the unified view option as an enhancement request for consideration in a future version. There are some data management issues, such as how data is distributed and accessed across multiple volumes, which may influence how much work is required for implementation.

Can you advise us of the benefits you feel a unified view would offer your users?

Regards,

Advansys Support

[Support 2]

Sorry, no, not at this stage. However, it is listed in our enhancement requests. At this stage we do not know if/when this feature may be implemented.

Regards,

Advansys Support

[Support 2]

An email regarding test application availability has been sent directly to your registered email address.

Regards,

Advansys Support

[Support 2]

Great news, thanks for the feedback.

Regards,

Advansys Support

[Support 2]

We have made progress with the caching capabilities but this feature is still under final development. While caching will improve a number of usability aspects for large system navigation and discovery, it is not likely to address the problems you are describing with the variation in system object visibility.

There appears to be a problem with system discovery, although the variable results you mention are unusual. The deletion and recreation of the trusted application should not alter system object visibility because it should affect only the ability for Archive To Go to login to accounts in Enterprise mode. However, if you mean by “delete and regenerate the trusted app key” that you are recreating a new system definition, then it is the system discovery process which is failing to traverse your full GroupWise system.

We are finalizing a test application which may help identify where the process is failing within the system discovery and will let you know when it is available.

Regards,

Advansys Support

[Support 2]

Great, thanks for the feedback!

Regards,

Advansys Support

[Support 2]

Are using Formativ 2.0.1?

Regards,

Advansys Support

[Author]

Replies