Support 2

[Support 2]

quote:

---

Restoring the association doesn´t help very long.

---

Do all users have the “Disable the VBS/VBE association everytime I start GroupWise” disabled?

As this feature is a user specific registry entry, you may have the situation where some users have the feature enabled and others have it disabled. This could cause the symptoms you describe.

As long as it is disabled for all users of the machine, it should work correctly.

Please let us know if this information does not help solve the problem.

Regards,

Advansys Support

[Support 2]

Thanks for the feedback Simon, great news.

Regards,

Advansys Support

[Support 2]

Thanks for the update. We thought it may have been an issue with the Message Saver Pack installer, although now it appears that it won’t install the Formativ Framework for .NET 1.0 for the same reason as you have discovered.

We are not sure how (or if) we’ll solve this issue. It will require further research and development.

Thanks again for bringing it to our attention.

Regards,

Advansys Support

[Support 2]

As this applet was user-contributed, Advansys does not provide support for it.

If you are seeking a more robust solution, you may wish to look at our Advansys Message Saver Pack 2.0, which offers a free 30-day trial.

Regards,

Advansys Support

[Support 2]

As this applet was user-contributed, Advansys does not provide support for it.

If you are seeking a more robust solution, you may wish to look at our Advansys Message Saver Pack 2.0, which offers a free 30-day trial.

Regards,

Advansys Support

[Support 2]

Sorry, it is not possible to extend GroupWise WebAccess with a Formativ Applet, which will work only with the full Windows GroupWise Client.

The technology is completely different for a WebAccess style implementation of Formativ. We are monitoring developments in this area and should it become commercially viable, we will review the options.

Regards,

Advansys Support

[Support 2]

Hi Andy,

Thanks for the update and good news.

And I hope you get some well-earned rest.

Regards,

Advansys Support

[Support 2]

It certainly appears the problem is related to the fact you cannot see an object class for the Global Applets object, which I assume is a Formativ Applet Library or the class called advansysFvScriptLib.

Unfortunately, we do not have other reports of a similar nature which may offer an explanation.

Perhaps the schema did not extend successfully or there is a problem with the Formativ snapin? Were there any errors when you ran the schema extension Wizard?

I have updated from 1.3.6 to 1.3.6e and all seems to work fine here with respect to the Formativ snapin.

I presume you have been following the information in the Formativ Studio guide with respect to eDirectory integration?

When running in Formativ Administration mode, when you start Formativ Studio, you should see in the status bar (left hand side bottom) of the dialog, the text:

Administrator Mode (your email address)

In addition, you can see the Formativ Configration information in the Formativ About dialog. This may provide some clues, although I suspect you need to identify why the object class for the Formativ Applet Library is not visible.

If you cannot determine the cause and rectify the missing class issue, we will need to consider the next step in troubleshooting.

Regards,

Advansys Support

[Support 2]

Thank you for the additional information. We will keep a look out for similar issues and, if required, notify Novell.

Regards,

Advansys Support

[Support 2]

Thank you, we are reviewing the information.

Regards,

Advansys Support

[Support 2]

At this stage we are not aware of any issues with respect to mixed post office versions during an upgrade to 7.0.1.

Could it be a synchronization/propagation issue?

What Archive To Go Creator errors do you experience when you attempt to archive a mailbox on a 6.5 Post Office?

Regards,

Advansys Support

[Support 2]

Thanks for the statistics. It is clear that you have a large system to administer. As we don’t have any known problems which would explain the symptoms you describe, we will start a troubleshooting process to try and identify the cause. This will be handled via direct email.

Regards,

Advansys Support

[Support 2]

Thanks for the report. Can you send us the Archive To Go Creator and Archive To Go Indexer log files for analysis? Please zip them and send them to support@advansyscorp.com.

Could you please clarify what you mean by the archive directory being 26GB? Do you mean the Archive To Go portable archive including the index or do you mean the user’s GroupWise archive folder?

While you mention there are errors during the index creation, does the index get created? For example, can you use Archive To Go Finder?

Regards,

Advansys Support

[Support 2]

How many mailboxes do you have across the 10 post offices you need to administer?

Regards,

Advansys Support

[Support 2]

The exact format is:

formativruntime /s /r-ABC123ABC123

where ABC123ABC123 is the registration code, exactly as you received it. The only difference between your syntax and the one above is that you are using and equals sign ‘=’ rather than a dash ‘-‘ character.

If for some reason the approach does not work, you may wish to try the one below. We have checked your customer record and you did receive a license file.

Licence Files and Installation Programs

Licence 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 licence 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 licence files in the same folder as the installer. If found, the licence files are copied automatically to the Formativ System directory. When the GroupWise client next starts, Formativ processes licence files found in the System directory automatically.

For example, suppose you are supplied with a licence file called formativ.lic, which happens to contain 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 executed upon GroupWise startup, both Runtime and the Presentation Pack are registered automatically.

I hope this helps.

Regards,

Advansys Support

[Author]

Replies