We haven’t had any report about this issue. Our engineers recommend you to upgrade the GroupWise client to the latest point release (i.e. 7.0.3).

– Is there any applet associated with the message forward event?
– Can you re-produce this behaviour on another machine?

If the problem persists, please send your Formativ Configuration to Support (support@advansyscorp.com). You can access this via the main GroupWise menus: Help | About Formativ. When the ‘About Box’ appears, select the ‘Configuration’ tab. Press the ‘copy to clipboard’ button, then paste the contents of the clipboard into your reply.

Regards,
Advansys Support

The “GW#C#FORWARD” registry key will be present when you remove the event association, it will not used unless you have an applet associated with the forward event.

Could you please confirm, whether you received the error, if the registry key is present and the applet is NOT associated with the forward event.

Our engineers unable to re-produce the behaviour in-house and also we haven’t had any report about this issue. It appear the issue could be environmental to the machine. As we suggest earlier, you may need to upgrade the client to the latest point release.

Regards,
Advansys Support

Can you re-produce the behaviour with another applet? May be you can create a simple applet, for example with the source below and attached it with the Forward event. Please make sure the registry key not exists prior to the association.

 
Sub Main(Client, GWEvent)
  msgbox GWEvent
End Sub

Let us know the results.

Regards,
Advansys Support

Thanks, we can re-produce the behaviour.

Our engineers will investigate this issue and we will contact Novell to get more information. We will post any update in this thread.

Regards,
Advansys Support

Hi André,

Sorry for the delay. We are still investigating the exact cause of the problem but we now believe it is not related to problematic registry entries but potentially a low level GroupWise code change which has impacted our Third Party Handler DLLs.

To help verify our initial problem tracing results within your environment, on a workstation with the problem, could you please try the following steps, which will unregister the Formativ TPH Dlls. Formativ will still continue to operate normally but any custom applets using low level token integration features will not (most solutions do not normally use this feature).

• Close the GroupWise Client.
• Open the Formativ Control Panel Applet.
• Select the General Tab (it should be showing by default).
• Under the Enable/Disable group, if selected, unselect both Applet Recorder and Command Blocker (for Formativ Runtime, only Command Blocker is relevant).
• Press OK.
• Restart the GroupWise client and test the Forward/Reply functions on an embedded message.

Once we receive your results we will review the next course of action.

Thank you in advance for your assistance.

Kind Regards,

Advansys Support

Thanks for your reply, which is interesting. If you unregister or uninstall Formativ, presumably the problem does not occur?

Regards,

Advansys Support

Thanks for the confirmation. We will write to you direct via email to continue troubleshooting and report back the results to this thread.

Kind Regards,

Advansys Support

Just prior to the end of the year we managed to track down and reproduce this error with a basic test C3PO. Our research confirms it is a GroupWise C3PO issue and not specific to Formativ. The D107 error will occur when forwarding or replying to an embedded message with any C3PO which traps the Forward or Reply events.

We provided the test code and results to the GroupWise engineering team, who have documented this issue as GroupWise bug #461686.

At this stage we do not know when a resolution will be available, although hopefully it will be addressed in the next GroupWise service pack for 7.x and 8.x.

Unfortunately, for technical reasons, we are cannot provide a work-around.

Kind Regards,

Advansys Support

[This message was edited by Support 2 on January 05, 2009 at 06:23 PM.]