atrapp

[atrapp]

I’ve send you an EMail with the details you asked for.

Thanks!
André

[atrapp]

Thank you for the quick response.

yes, after the access violation the Groupwise Client crashes (we have to stop it using the taskmanager) and there is no other process with an access violation.

all the other information you’ve asked for, i will send you via EMail.

thanks, regards,
André

[atrapp]

Thanks for your quick response,

this is exactly what I’m trying, but unfortunately i get the following error:

Object doesn’t support this property or method: ‘Groupwise.ItemAddMimeXField’ at line 14, column 6

Is it possible that this token is not implemented in Formativ yet? I can´t find anything about it in the Language Guide too.

Here is my Code:

Dim oMsgItem
Set oMsgItem = Groupwise.ComposingItem
Dim iMsgID
if oMsgItem is Nothing then
call Groupwise.NewMail
iMsgID = Groupwise.ItemMessageIDfromView
call GroupWise.ItemAddMimeXField(iMsgID, “X-WDRCrypt”, “yes”)
else
iMsgID = Groupwise.ItemMessageIDfromView
call GroupWise.ItemAddMimeXField(iMsgID, “X-WDRCrypt”, “yes”)
end if
set oMsgItem = Nothing

[atrapp]

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.

Regards,

André

[atrapp]

Hi,

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 !?

Regards
André

[atrapp]

Hi there,

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é

[atrapp]

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é

[atrapp]

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?

[atrapp]

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é

[atrapp]

I will do this!

Thank you for the quick response !

André

[atrapp]

Thank you for the fast response ! With coded User i mean, i would be very happy, if there is a posibility to make the Connection with a User Account defined in the applet. So that our Users do not need rights to the WPDOMAIN.DB.
Do you think there is a way ?

Regards from Germany !
André

[Author]

Replies