I cannot explain the behaviour you describe, but I suspect it may be related to roaming profiles. When Formativ is installed it writes a value to the following key in the registry:
The value is the path to the tokenblocker.dll file referenced in the error. When GroupWise loads, it attempts to load any files referenced under this key.
Are you using roaming profiles? If so, it could be that the user’s ‘HKEY_CURRENT_USERSoftwareNovellGroupWiseClientThird Party’ key is being replicated to every machine they access. This would tell GroupWise that it should attempt to load the DLL, when in fact it can’t because the file doesn’t exist on the machine. Unfortunately, we can’t suppress this warning message as is eminates from GroupWise.
Should roaming be the problem, the only solution I can think of would be to install Runtime on the offending machine (it wouldn’t need to be registered), or to configure this registry key as an exception to roaming (if possible).
I hope this helps.