Support 2

[Support 2]

No, sorry, not at this stage. We are working with cross-platform compatible technology which can offer rich functionality.

When the non-Windows clients evolve further it may become practical to offer a similar solution.

Regards,

Advansys Support

[Support 2]

The message which asks you to press F5 is included because sometimes the underlying GroupWise APIs fail to access the currently open message’s ID. Usually pressing F5 successfully forces the GroupWise Client to obtain the necessary Message ID information from the Post Office. The problem is not related to Stationery.

Unfortunately we do not have control over this GW API and it appears to be more of a problem in specific GroupWise environments. A continued problem, where the F5 key does not solve the issue (as you are experiencing), is rare. We need to gather more information to discover why it remains a problem within your environment.

Are you able to save and close the draft message, reopen it from the Work In Progress folder and try again?

To assist us troubleshoot the problem further, please send us the Formativ configuration information by selecting the GroupWise client’s Help menu, select About Formativ, select the Configuration tab and use the Copy to Clipboard button, then paste the config info into an email to support@REMOVE-THISadvansyscorp.com.

Regards,

Advansys Support

[Support 2]

Thank you for the additional feedback and we fully appreciate the reasons for your need. While we cannot disclose specifics in this public forum, we have already touched base with another of your colleagues today and we will be able to provide further background information by telephone.

Regards,

Advansys Support

[Support 2]

We have now sent you the license files via direct email. As you purchased online, while registration keys are provided, the license files are not automatically sent by the system. I will include below some additional information below about registration options, manifest and license files, which was sent in our last Advansys newsletter. If you are not signed up for our newsletter service, you can add your address at http://www.advansyscorp.com/contactus.htm#mailinglist.

At this stage it is not possible to license our software via Novell eDirectory. You will need to ensure that both the Formativ Runtime and Multiple Signatures are registered. You can tell the end-user’s exact registration status via the GroupWise Help | About Formativ | Configuration Tab or by running the Formativ Registration Utility (GroupWise Help | Formativ Registration Utility…).

Hopefully the license files will assist solve your current need. We are always striving to improve our products and services and we appreciate the feedback you have provided.

Please let us know if you would like further information or assistance.

Regards,

Advansys Support

+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

To facilitate easier product registration and solution pack support, a number of architectural changes were introduced in Formativ 1.6 which are now used more widely due the expanded Formativ 2.0 solutions range. Key changes are the use of Manifest files and the availability of License files, which are described below. This information is also available in the Formativ help files.

Manifest Files

A manifest file is a special file that defines the solutions that appear in a solution pack. Manifest files are necessary because the same applet can appear in more than one solution pack. Normally you don’t need to concern yourself with the operation of manifest files because they are installed automatically by the product’s installation program.

However, if you are installing Formativ solution packs in an Enterprise and use eDirectory to distribute the solutions, you need to ensure the manifest files associated with each pack are available to your users.

Default Manifest File Location

When you install a solution or solution pack, any manifest file is installed to the Formativ System folder. The Formativ system folder location is normally dynamically determined. Its default location is:

C:Documents and SettingsAll UsersApplication DataAdvansysFormativ1.0System

Making Manifest Files Available when using eDirectory

Formativ currently does not support the distribution of manifest files via eDirectory. If you are using eDirectory to distribute solutions within your enterprise, you need to ensure any associated manifest files are made available to your users. You have several options:

Defined a Shared Formativ System Folder – when you install Formativ you can optionally specify the location for the System folder through the user of the installer config.ini configuration file. You could use this technique to set the location of the system folder to a shared location on a network. As an Administrator, you would then install the appropriate solution pack(s), then copy the manifest file to the shared system folder.

See the Installation topic in the Users Guide for information regarding changing the location of the System folder.

Distribute Manifest Files to All Users – you are also free to manually (or via a distribution tool such as ZENWorks) copy manifest files to each workstation. You need to ensure that you copy the manifest files to the appropriate location (see above).

License Files

License files may be used in conjunction with Formativ setup programs to register both Formativ and supported solutions automatically during installation. To use this facility, ensure your license file(s) is/are located in the same folder as the setup program you are executing.

When you execute a Formativ setup program, which supports automatic license copying (currently all version 2.0 product and solution pack installations supplied by Advansys), the setup program checks for the existence of license files in the same folder as the installer. If found, the license files are copied automatically to the Formativ System directory (see Manifest File section above for location). When the GroupWise client starts, Formativ processes license files found in the System directory automatically.

For example, suppose you are supplied with a license file called formativ.lic. This license file contains licensing information for both Formativ Runtime and the Formativ Presentation Pack. By ensuring formativ.lic is in the same folder as the Formativ Runtime setup program, it would be copied to the Formativ System directory automatically when the installation runs. When Formativ Runtime is first executed, both Runtime and the Presentation Pack is registered automatically.

Please Note: Introduced in Formativ 2.0.0.16, License and Manifest files will also load from the main Formativ program folder, usually C:Program FilesAdvansysFormativ.

+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

Registration Utility (from the Registration Utility Guide)

The Registration Utility can be run in Command Line Mode by running the program with the /r- or /l- parameters. The /r- option takes a registration filename and the /l- option takes a license filename as the parameter data. No user interface is displayed in command line mode.

The file format of the registration file is shown below.

Command line mode allows batch registration of multiple Formativ products and solutions, either by placing the registration or license file(s) in a shared network location, or by using a program such as Novell ZENworks.

Running in Command Line Mode

To run the Registration Utility in Command Line Mode, use the following syntax at the command line:

frmrmg10.exe /r- or

frmrmg10.exe /l-

where:

• ‘registration filename’ is the name of the registration file, a text file which should conform to the format shown in the Registration Utility Guide (if this approach is desired, the product codes would need to be provided via direct email); or
• ‘license filename’ is a special license file which may be provided by your Formativ reseller or by Advansys.

Note: If you place the registration or license file(s) in the same location as the Registration Utility, you do not need to provide a fully qualified path to the registration/license file, just supply the filename as the command line parameter.

Note: Before you can register a Formativ product or solution using this utility, the product(s) to be registered must be already installed on the target workstation.

+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

[Support 2]

Great news, thanks for letting us know.

Regards,

Advansys Support

[Support 2]

Did you copy your product license file to the same location as the manifest file? This will ensure your solution is registered automatically upon GroupWise client startup.

More information on this can be found in the Introduction and How To Register sections of the users Guide (GroupWise Help | Formativ Help | …. Guide)

Please let us know if you have any other questions and feel free to write directly to support@REM0VE-THISadvansyscorp.com.

Regards,

Advansys Support

[Support 2]

quote:

---

…but don’t click on this button to restore.

---

Do you mean that you can’t see the [Restore Association] button or you click the [Restore Association] but it doesn’t restore your VBS association?

Regards,

Advansys Support

[Support 2]

Hello,

The /allusers switch is valid for Formativ Solution Installers but not the Framework products, such as Formativ Runtime.

As we have not yet had similar problem reports, there is no obvious reason why your settings in the formativconfig.txt are not working. I presume your formativconfig.txt file is in the same folder as the Runtime installer? Are any settings being changed by the config file?

Are you able to send a copy of the formativconfig.txt to support@advansyscorp.com?

I suspect that the default Registry settings for Formativ Runtime should meet your requirements. The default setting should be the NetWare Client as the primary choice and if it is not available (it will be available in your case) it would default to LDAP.

Regards,

Advansys Support

[Support 2]

Hi Tech11,

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]

Hi Andrew,

We have researched ways to work-around this behavior of the Spell Checker cursor relocation. Before inserting the signature text, the key is to relocate the cursor to a known anchor point in the message.

There are various pros and cons to every approach. As such, your request is probably best addressed via direct email, so I’ll ask one of the developers to respond with how we may be able to assist.

Regards,

Greg
Advansys Support

[Support 2]

Thank you for your post. Yes, you are correct, Formativ Studio is the product which contains the applet publishing capability.

You may have seen that Formativ Studio is sold separately or in both Formativ Small Business and Formativ Enterprise.

Please let us know if you have any further questions.

Regards,

Advansys Support

[Support 2]

Sorry, it was fixed in Build 2.0.0.17, which can be downloaded here:

http://www.advansyscorp.com/formativ_download.htm

Regards,

Advansys Support

[Support 2]

Hi John,

Yes, this is a known issue which was introduced with 8.0i. Another post offers the solution (link to post). I have also quoted the post below.

Let us know if their fix does not solve the problem.

Kind Regards,

Advansys Support

quote:

---

I got the same problem (access violation with scriptproxy.dll) with McAfee 8.0i. It is a new “feature” from McAfee that javascript and vbscripts are scanned, e.g. they redirect the scripts to their own engine.
You can disable this by modifying the registry with the following info from NAI.

Q: I’m getting errors when executing
JavaScript/VBScript. How does ScriptScan work?

A: There are two registry entries, one for
JSCRIPT.DLL and one for VBSCRIPT.DLL that are
redirecting calls to the VirusScan Enterprise
ScriptScan DLL called SCRIPTPROXY.DLL.
ScriptScan is an optional component; you can
remove it from your computer to see if errors
subside. The registry keys to check are;

HKCRCLSID{f414c260-6ac0-11cf-b6d1-00aa00bbbb58}InprocServer32

– Default value should be:
c:windows foldersystem32jscript.dll
(The path is operating system specific.)

– VSE sets:
c:program filesnetwork associatesvirusscanscriptproxy.dll

HKCRCLSID{B54F3741-5B07-11cf-A4B0-00AA004A55E8}InprocServer32

– Default value should be:
c:windows foldersystem32vbscript.dll
(The path is operating system specific.)

– VSE sets:
c:program filesnetwork associatesvirusscanscriptproxy.dll

---

[Support 2]

This is an unusual problem and one which we have not come across previously. According to the GroupWise documentation, the D11B error relates to Too many items in mailbox and it is most strange that it only arises when Formativ is installed. I don’t know yet to what the other error refers, DAX Error: Could not find the folder object.

quote:

---

Even when we use the same workstation, with the same formative eDirectory configuration but we use another eDirectory user object, every thing works fine (No errors and the applets are running correct).

---

When it works, are you logging into another NetWare user and then starting the GroupWise client?

When the problem occurs, can you still access the About Formativ dialog under GroupWise Help? If so, could you please send us the Formativ configuration information from the Configuration Tab (About Formativ):

• for the case where the error occurs; and
• for the case where all appears to work correctly.

If the configuration information is not accessible when the D11B error occurs, please still send the configuration information for the case where it does work. Please send the information direct to support@advansyscorp.com.

If you use the Formativ Control Panel Applet to disable eDirectory integration, for example, select Use local applets only on the Protocols tab, does the error still arise when starting the GroupWise client?

Regards,

Advansys Support

[This message was edited by Support 3 on August 02, 2004 at 04:16 PM.]

[Support 2]

Sorry about the delay. The engineer who would normally address Citrix installation issues is currently on Jury Duty and will be back next week.

In the mean time, we will write to you directly about this issue. From the information you have provided it is likely we already know what you require to resolve the problem.

Regards,

Advansys Support

[Author]

Replies