Support 2

[Support 2]

Thanks for the update about the email address change. It is the beta 2 location as previously provided and another email has been sent to your current email address.

The February date tends to indicate you are looking at the 1.2 released version.

Kind Regards,

Advansys Support

[Support 2]

KenD,

Please note that we are not able to send email from our support account to your email address. It keeps rejecting messages sent from support with the response that your mail system is not configured to relay messages from Advansys support to your address.

This appears to be a similar problem with notifications from the Support Forum.

Kind Regards,

Advansys Support

[Support 2]

Some good news. We’ve just uploaded an Archive To Go 1.5 beta update which includes the archive selection feature in Archive To Go Viewer. As the A2Go Viewer is a stand-alone program (a2goview.exe), you can now run it from any convenient location and select any valid Archive To Go archive.

We will also be adding a Recent Archive list for quick reselection of recently opened archives (under the File Menu) and the option for an administrator (or user with sufficient rights, say on a local drive) to create an INI file containing a preloaded list of accessible A2Go archives.

I hope this will meet your needs.

Kind Regards,

Advansys Support

[Support 2]

This enquiry has also been responded to via direct email.

Kind Regards,

Advansys Support

[Support 2]

Do you mean you manually reindexed the archive and you can no longer find the messages in that date range via Finder?

Were all the archive volumes accessible to Indexer when you reindexed?

Can you please send the indexer log file to support@advansyscorp.com.

Kind Regards,

Advansys Support

[Support 2]

Some of the updates included in beta 2 took much longer to complete than anticipated. At this stage we are still hoping to include the archive selection feature in the final release but we cannot make any guarantees.

Kind Regards,

Advansys Support

[Support 2]

Did you receive a license file with your purchase (usually sent via email from Advansys direct)? If so, you can simply rollout the license file to each workstation and the solution will register automatically upon the next GroupWise Client restart.

If you don’t have a license file or need further information, please let us know.

Kind Regards,

Advansys Support

[Support 2]

We are finalizing 1.5 and engineering will see if something can be squeezed in for this release.

Kind Regards,

Advansys Support

[Support 2]

It would be nice to offer that feature but the free Personal Outlook Migration Pack uses the Outlook Client’s COM APIs to perform the migration.

Kind Regards,

Advansys Support

[Support 2]

We have sent the work-around via email.

Kind Regards,

Advansys Support

[Support 2]

GroupWise engineering is looking into this issue. The initial response from Novell indicates that the intent is not to prevent trusted applications, like Archive To Go, from accessing Limited Accounts. Should this problem be confirmed by GroupWise engineering, it will be fixed.

In the mean time, as the problem solution is not within our control (as a third party developer), when using Archive To Go you will need to convert Limited to Full accounts. For those accounts that you convert for use only with Archive To Go (Enterprise Mode), I suggest that you keep track of the Account IDs. Once this issue is registered as an official Novell defect number, perhaps you can advise Novell of the Account IDs which were converted soley as a work-around to this problem.

Kind Regards,

Advansys Support

[Support 2]

Thanks for the additional information. We will research this issue with Novell and report back.

Kind Regards,

Advansys Support

[Support 2]

Thanks for the clarification, which helps us to understand the nature of the problem. It is correct that Archive To Go uses the GroupWise Client APIs to access a mailbox. In your testing, does Archive To Go account access fail for both Archive To Go’s Local and Enterprise Access modes?

Kind Regards,

Advansys Support

[Support 2]

Yes, you could store your applets in a shared network folder location. For Formativ Runtime users, you do need to Flexalock the open source applets, otherwise they will not operate.

With respect to LDAP, the LDAP Error 49 is LDAP_INVALID_CREDENTIALS: This indicates that during a bind operation one of the following occurred:

– The client passed either an incorrect DN or password.
– The password is incorrect because it has expired, intruder detection has locked the account, or some other similar reason.

I could not find any information in our support history which would assist you further.

Kind Regards,

Advansys Support

[Support 2]

When the default Applet path is used, no Registry entry exists. A Registry entry only gets written to the hive HKEY_CURRENT_USERSoftwareAdvansys Corporationformativ1.0Settings when the Applet path is overridden by either installer optoins or by changing the path in the Formativ Control Panel Applet’s Paths tab. The default path is generated dynamically by Formativ, in other words the current user’s My Documents folder is obtained and then the standard subfolder hive AdvansysFormativApplets is appended, i.e. C:Documents and Settings[Current Windows User]My DocumentsAdvansysFormativApplets.

I hope this helps.

Kind Regards,

Advansys Support

[Author]

Replies