Forum Replies Created
-
AuthorReplies
-
Thanks MA.
Advansys Support.
I believe this a known bug in the GroupWise client – specifically with the ItemSetText() token. You don’t even have to proxy to another account to see this bug.
I recall this was reported to Novell some time back, but I’ll report it again just in case.
Advansys Support
Is your copy of Runtime registered? If the 30 day trial period expires no applets will be loaded.
You may want to send a copy of your configuration information to support@advansyscorp.com – from the main GroupWise menu select Help | About Formativ. When the about box appears, select the configuration tab and press the ‘copy to clipboard’ button. Paste the contents of the clipboard into a message to the abovementioed address and we’ll take a look.
Regards,
Advansys Support
This is a very general error message, so we’ll need more information to assist.
GWCMA1.DLL is the GroupWise Object API file – part of the GroupWise client. It sounds like the user may have an applet installed that is causing a problem on send.
If you disable Runtime via the Formativ Windows Control Panel Applet and try to send a message, does the error still occur? If it does the problem is not being caused by Formativ.
If not, re-enable Formativ, rename the local applets folder, restart GroupWise, then send a message. If the error does not occur an applet is causing the problem.
You would then need to go through a process of elimination to see which applet is the culprit. The easiest way to do this would be to remove an applet at a time, then try to send a message. When the error no longer appears you have located the culprit.
Please let me know how you proceed.
Regards,
Advansys Support
Thanks MA!
I seem to recall you needed to be using GW6.5.1 or higher, and that you had to use the account MultiLoginAddressBookSupport property in order to access the Birthday field (something to do with MAPI?).
As this is really a GroupWise Object API question, you could probably obtain the definitive answer in Novell’s Object API Usenet forum – head to developernet.novell.com as a starting point.
Regards,
Advansys Support
We’ll respond to this via direct email.
Advansys Support
In versions prior to 2.0.1 (currently in Field Test mode), the Formativ installer would disable the association between VBS/VBE files and the Windows Script Host. It would reassign the association to an application that displays the message you mentioned.
I’m not sure why you would start to see this message now, other then whatever has been done during the upgrade has caused a VBS or VBE script to be automatically executed. The message box you mention above will contain the name of the VBS file some process is trying to activate.
You can re-assign the association from the Formativ Windows Control Panel applet – press the ‘restore association’ button under the additional security section (and ensure the ‘disable association…’ option is unchecked).
I hope this helps.
Advansys Support
If you have installed the GroupWise client onto a Windows machine, I don’t know the Admin API would not be registered.
I’ll need to see your machine config information. From the main GroupWise menu, select 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 a message addressed to support@advansyscorp.com.
Regards,
Advansys Support
The fact other applets appear to run fine on these machine is very peculiar. Stationery makes heavy use of Microsoft Internet Explorer (as does GroupWise in terms of it’s HTML support). It might be worthwhile re-installing the latest version of IE, then re-install the GroupWise client to ensure the workstation is properly configured.
Which version of Windows are you running? I’m assuming it’s not 95/98/NT?
I look forward to hearing from you.
Advansys Support
Yes. 2.0.1 is primarily a GW7 maintenance release. It works with Novell GroupWise 5.5, 5.5 EP, 6.0.1, 6.5 and 7.0 Windows client or above. (See the documentation for a full list of system requirements).
Regards,
Advansys Support
Thanks tech11.
Embru – did the response from tech11 solve your problem?
Regards,
Advansys Support
As you discovered, you need to use Studio or Creator to change applet properties.
In addition, Runtime only ‘sees’ Flexalock or encoded applets.
Regards,
Advansys Support
Thanks LP!
Advansys Support
Thank you for your posting. A couple of initial questions:
1) Are you able to run any other applets on one of these machines? We need to determine if this is a stationery applet-specific problem, or if it affects all applets;
2) If only the stationery applet is affected, are you able to use another item of stationery (i.e one that does’nt include the inclusion of address book fields)?
Kind regards,
Advansys Support
-
AuthorReplies