Support 2

[Support 2]

Perhaps another approach may be to implement the user’s signature via an applet rather than using the native GroupWise signature feature.

The main challenge with this approach is to ensure the signature is located in the right place under varied conditions, such as Reply, Forward etc.. and when the Spell Checker operates it may shift the current cursor position. It is achievable and our Multiple Signatures solution already caters for the Forward Reply cases.

Regards,

Advansys Support

[Support 2]

Novell has confirmed that the GroupWise Message.Forward API is broken in GroupWise 6.5.x (defect #
357086), upon which the Message Monitor solution is dependent. It does work in 6.0.x, for which the solution was designed originally.

Hopefully Novell will be able to fix this API command and include it in the official 6.5.2 release.

Regards,

Advansys Support

[Support 2]

Unfortunately we are not aware of a work-around. We have reported the issue to Novell and hopefully that will result in a fix being available in the next service pack.

Regards,

Advansys Support

[Support 2]

Thanks for your post. I have replicated the problem in-house. Testing indicates that the problem occurs when using client Caching mode. Setting the DelayedDeliveryDate works correctly when using client Online mode.

There is also a recent posting on the Novell Developer newsgroup from someone experiencing the same problem [click here].

This is an issue with the Object API and not related to Formativ. We will report the problem to Novell.

Seasons Greetings,

Advansys Support

[Support 2]

Thank you, this additional information does help. I was able to replicate the problem on my machine, which is running the 6.5.1 client, by moving the folder context toolbar to another position.

The additional information makes it easier to replicate the problem and to report it to Novell.

Regards,

Advansys Support

[Support 2]

Thank you very much for your feedback. We can’t say yet if these features could be included in the first release, but your worthwhile suggestions have been submitted to the engineering team for review.

If you have any further suggestions, please don’t hesitate to communicate them to us.

Regards,

Advansys Support

[Support 2]

Thanks for your feedback. We have had a couple of similar reports but we have not yet been able to track the environmental conditions which precipitate the problem. We cannot yet reproduce the issue in-house.

To help us gather further information, if you press and hold the SHIFT key when you initiate the migration solution, it should provide a more detailed log of the startup sequence. The log is saved in the default Formativ Data folder, which can be determined by looking at the configuration information, in the GroupWise Help | About Formativ dialog.

Are you running GroupWise in online, caching or remote mode?

Are you trying to migrate from a PST file or live from an Exchange account?

Is your Outlook configured for Internet Mail only or for Workgroup?

What MAPI mail services and profiles do you have configured?

Do you have Outlook configured to prompt you for the profile to be used so that it does not by default use the GroupWise profile? You can configure Outlook to prompt for the profile by choosing Tools | Options | Mail Services and select the option Prompt for a profile to be used.

You can post the answers and log file to the forum or send it direct to support@advansyscorp.com.

Thanks for your assistance.

Regards,

Advansys Support

[Support 2]

Sure, they have been resent to both addresses.

Regards,

Advansys Support

[Support 2]

Hi Roger,

I’ve checked our records and you were emailed twice about BSP source code to the address you have indicated, once on the 27 Oct and again on the 31 Oct as a follow-up to your follow-up.

We have no idea why you are not receiving our messages. Do you?

Regards,

Advansys Support

[Support 2]

Further experimentation revealed that GroupWise 6.5.2 beta4 does not solve the problem. However it appears that if you play around with the custom settings of the Item Context toolbar, and move it into another position and then back again, the problem appears to ‘go away’. Changing the settings of the toolbars back to the settings which caused the problem to appear originally, did not seem to make it come back again.

By moving the toolbars and changing the custom settings (don’t know which is the key factor at present), something must be eventually written to the mailbox account which prevents the problem from recurring. This is why the problem appears to happen on new accounts or GroupWise client installations, and can disappear without apparent reason.

We need to pin this one down in order to help Novell reproduce the problem and fix the underlying cause.

Regards,

Advansys Support

[Support 2]

Hi Phil,

Yes, Formativ disables VBScript as a general security measure. You can restore VBScript operation by using the Formativ Control Panel Applet in the Windows Control Panel. Run the Formativ Control Panel Applet and on the General tab, uncheck the option:

[ ] Disable the VBS/VBE association everytime I start GroupWise

You can then click the Restore Association button to restore your original VBScript registry association.

I hope this helps.

Regards,

Advansys Support

[Support 2]

This post was answered by direct email.

Regards,

Advansys Support

[Support 2]

As a follow-up, we don’t have any outstanding issues with the OnSend event and we cannot duplicate the problem you describe.

Are you able to send your applet to us for analysis? As you may appreciate, we cannot support custom solutions and we need to be able to replicate the problem to understand the cause.

You can send the applet to: support@advansyscorp.com

Regards,

Advansys Support

[Support 2]

A pleasure and thanks for the feedback. We would still like to identify why your Registration Utility is not working and I will be following this up with the engineering team.

Regards,

Advansys Support

[Support 2]

Thank you for your post and your purchase. At this stage we don’t know why this would happen and we will research the issue.

In the mean time, you should be able to register the software using the Windows installer, formativdeveloper.exe, by using the Windows RUN command and passing the following registration only command line option:

formativdeveloper /ro-&ltRegistration Code&gt

Register Only Mode

The /ro switch is used to register Formativ. It does not install any files, so Formativ must have already been installed on the PC in order to use this parameter. You must provide the registration code exactly as supplied by Advansys, or your reseller, for the registration to be successful.

We will get back to you once we have an idea how to research the registration utility issue.

Regards,

Advansys Support

[Author]

Replies