Support 2

[Support 2]

Thank you for your post. The eDirectory distribution facility is designed primarily for solutions developed in-house by our customers. It was not originally intended that our commercial solutions, which require ancillary files such as manifest, license and often data files, be distributed using this feature.

The problem arises because a local installation has been performed first, which is necessary for the copying of the solution manifest, licensing mechanism and any data files. However, a local install also copies the applet files onto the workstation’s local Applets folder and this is where duplication occurs when eDirectory is also used.

The only way to rectify the duplication problem is to manually delete the applets from the user’s local Applets folder (or rename the local Applets folder etc. so Formativ cannot see them upon startup). Do not do an uninstall because this will remove the required support files. Alternatively, you could rename the registry key which identifies the local Applet path and point it to a new, empty or non-existent folder.

Regards,

Advansys Support

[Support 2]

Thank you for your post. We presume you are using the fully licensed version of Archive To Go?

If your GroupWise client is 6.5.5 or below, it is possible that a GroupWise error dialog has popped up behind the Archive To Go Creator dialog. The error text could be either Record not found or Bad parameter. This can happen only if you have opted to include message properties in the export. You can confirm this by dragging the Creator dialog to an edge of the screen. If you do see such a dialog, just click OK to allow Creator to proceed.

While the problem appears to be user data specific, trying the Archive To Go 1.2 beta is probably the first step in helping to isolate this problem.

Unfortunately from your support login information we cannot locate your company’s purchase details from our records. So we can make 1.2 available to you, could you please send them to support@advansyscorp.com?

Regards,

Advansys Support

[This message was edited by Support 1 on January 28, 2007 at 05:36 PM.]

[Support 2]

Thanks for your feedback. You do not need the registered version because the trial version is fully functional until the 30-day evaluation period expires.

Regards,

Advansys Support

[Support 2]

This is included in Archive To Go 1.2, which is scheduled to be available by mid-February. We have the latest candidate release being posted today. If no problems are discovered during field testing, this candidate will become the release version.

If you would like to test the candidate release for 1.2, please send an email to support@advansyscorp.com. If your organization does not already own the full license of Archive To Go, to test a full mailbox export with the candidate trial release, please send an email to support@advansyscorp.com requesting a full trial and nominate the User ID of the GroupWise account you would like to export.

Regards,

Advansys Support

[Support 2]

Absolutely, we encourage you to post questions to the forums to give other users the opportunity to help. The last post was simply to identify that Advansys does not provide support for this solution.

You may wish to review what recent changes have occurred within your system environment which may have precipitated the problem.

Regards,

Advansys Support

[Support 2]

Thanks for the report. We have received two reports of this issue previously and as a result it appears to be a rare occurrence. The first reporter we didn’t hear back from after a request for further information and the other stated the problem ‘went away’ after they installed the MS .NET Framework 2.0. However, as the A2Go viewer is not a .NET application, we have no idea why installing .NET 2.0 would resolve the problem. It is suspected that the install must have changed some environmental condition which resolved the problem.

Initially there are a couple of options. Firstly you could try the ‘anecdotal’ approach and install MS .NET 2.0. Secondly, you can try our candidate release for Archive To Go 1.2, which I will send you download information via direct email later today.

If these approaches don’t work, we will gather further information to see if we can reproduce the problem here.

Regards,

Advansys Support

[Support 2]

At this stage we are not aware of any other causes for a problem which is network access specific.

If we receive other suggestions from engineering, we will let you know.

Regards,

Greg Bell
Advansys Support

[Support 2]

Is IE7 installed on the workstation attempting to run Finder from the network?

If so, the cause may be related to a change in a security level introduced by IE7. We found we had to change some advanced trust settings for the local Intranet zone in the Internet settings, otherwise we couldn’t run anything from the network without getting an ‘untrusted application’ warning. We had to add the file server path to the Advanced trust settings for the Intranet zone (i.e. file://servername). Some .NET applications would not run from the network until this security setting was changed on the workstation, even though the Windows .NET security Wizard was previously used to set full trust to the Intranet zone. There may be another way to achieve this outcome but we have not investigated further.

Regards,

Advansys Support

[Support 2]

Similar to your use of the constant fgwNormal, try fgwOutOfOffice rather than egwOutOfOffice, which is the native GroupWise constant name and which will not be recognized by the Formativ Language.

The Formativ Language is scripted and not a compiled language. As a result, Formativ does not expose the native GroupWise constants automatically within the language. Instead, we support a range of constants which have the ‘fgw’ prefix and not ‘egw’. If you find the Formativ Language does not have an equivalent fgw constant for the native egw one, you can do the following:

• use the documented GroupWise API constant’s value directly within your applet code, such as 1 or TRUE etc, or
• at the beginning of your applet, define a new constant name and assign it to the desired GroupWise API constant’s value and subsequently use your constant name within your applet code.

I hope this helps.

Regards,

Advansys Support

[Support 2]

Thanks, we will provide the beta details today via direct email.

Regards,

Advansys Support

[Support 2]

Use our Personalized Emailer solution…

Regards and Happy Holidays,

Advansys Support

[Support 2]

Thank you for your understanding and best wishes also to you and your colleagues!

Regards,

Advansys Support

[Support 2]

We hope to be able to reply with a suggestion soon. Unfortunately this time of year is a little crazy.

Regards,

Advansys Support

[Support 2]

Thanks for your post, which we seemed to have missed earlier. To assist us troubleshoot the problem, can you send us the exact error message and the Formativ configuration information by selecting the GroupWise client’s Help menu, select About Formativ, select the Configuration tab and use the Copy to Clipboard button, then paste the config info into an email to suppport@advansyscorp.com.

Regards,

Advansys Support

[Support 2]

Thanks for your feedback, much appreciated.

Regards,

Advansys Support

[Author]

Replies