October 30, 2008 at 11:21 pm #3807
we run Windows XP with the 7.0.2 HP2 Groupwise Client. Our Customers reporting the following error when they try to forward an embedded email attachment:Error D107 contact your system administrator. We find out, that if the runtime is disabled everything is woorking fine.
Does somebody know about this issue ?
November 2, 2008 at 4:33 pm #6273
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 (email@example.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.
Advansys SupportNovember 4, 2008 at 8:03 am #6263
Thanks for your reply !
Yes, you are right, there is an applet associated with the forward event.
A few tests later we find out, that if the applet is pulled by a new user, a reg key will be writen called GW#C#FORWARD under [HKEY_LOCAL_MACHINESOFTWARENovellGroupWise5.0C3PODataTypesGW.MESSAGE.MAILAdvansys.formativEvents].
If we remove the event from the Applet and manually delete the Reg Key, everything is fine. Unfortunately the key is not deleted only by the adjustment of the applet. So, for our concerned customers, the error will be there till the key is manually deteted. 🙁
Let me know if you have a helpfull idea !
Thx AndréNovember 4, 2008 at 4:19 pm #6267
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.
Advansys SupportNovember 7, 2008 at 4:14 am #6269
We can reproduce the error on every machine and even if the latest GW Client Version is installed. The only thing we need to do, is to associete the forward event Applet once, so that the reg key is written. After that we remove any applet associeted with the user and the error still occurs. Should I send you our Applet?November 9, 2008 at 1:01 pm #6272
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.
Advansys SupportNovember 10, 2008 at 1:21 am #6265
It is the same result.Ok, here is what I did:
I associated the new Testapplet with the Forward Event in the Mailitem (Before Forward) then I started the GW Client and the Keg Key is written. I started the GW Client a second time and I opened a Mailitem that is attached to another Mailitem. Next step is clicking the Forward Button and I get the D107 Error. If I click OK the Messagebox comes up and after that the new Mailform is created.
Greetings AndréNovember 10, 2008 at 3:35 pm #6276
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.
Advansys SupportDecember 3, 2008 at 12:53 am #6271
I’m still waiting for a fix for the behaviour. We have over 4000 Clients with this buggy Reg Entries. Are there new realizations to the problem?
Thx AndréDecember 3, 2008 at 2:52 pm #6266
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.
Advansys SupportDecember 4, 2008 at 1:33 am #6277
thanks for reply! These Options are not selected in our Runtime environment. But it does not makes a difference if the Options are marked or not.
I’m going to make a call with our Novell PSE to hear what Novell thinks about this Problem.
Maybe we can try to fix the problem together !?
AndréDecember 4, 2008 at 2:22 am #6270
Thanks for your reply, which is interesting. If you unregister or uninstall Formativ, presumably the problem does not occur?
Advansys SupportDecember 5, 2008 at 12:03 am #6264
Yes, that´s right! If Formativ is uninstalled the Error is gone. And even if I import the old REGISTRATION KEYS under C3po, the error does not arise.
AndréDecember 5, 2008 at 1:15 pm #6268
Thanks for the confirmation. We will write to you direct via email to continue troubleshooting and report back the results to this thread.
Advansys SupportJanuary 5, 2009 at 7:17 am #6278dhschryerParticipant
I ready this thread this morning and though I might have wrote it, as we are having this exact same problem.
Are there any updates on it yet?
DavidJanuary 5, 2009 at 5:59 pm #6275
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.
[This message was edited by Support 2 on January 05, 2009 at 06:23 PM.]
- You must be logged in to reply to this topic.