Mail Rules Not Working

A client had an issue where one or two of his mail rules in Notes 8.5 (Notes 8 template, Domino 8.0.1 server) stopped working. He played around several times with disabling rules, deleting them, etc. We even disabled & deleted all his rules, ran some script to recompile his rules, and I even deleted the calendar profile. When he re-created 2 of the rules, still no luck. Then I looked more closely at the 2 rules he had re-created. To my surprise, the OrderNum fields of the 2 rules were numbered "1" and "3"....but no "2". On a whim, I decided to use my "Edit Any Field" SmartIcon to change that "3" to a "2". Surprise, surprise: after that, the rules worked fine! I'm not sure if Notes was seeing a rule numbered "2" that was disabled, and therefore was not applying the other rules, or what. All I know is it seems to be fixed!

Single sign-on error with Lotus Sametime 8.0.2 Standard client

At my workplace, we recently deployed the Sametime 8.0.2 client throughout our company and had several instances of the following issue:


















(Text reads: Single sign-on account is invalid, the possible reason is your operating system account has been changed. You can try to recover your operating system's password to the old one, or inform the administrator.)

After seeing this error, the Login button stays grayed out, and normally we have to kill the process (if ST doesn't crash). Well I contacted Lotus support and finally got the following resolution:

The Sametime UIM client stores the hashed Sametime password in the following keystore file;
\Application Data\Lotus\Sametime\.metadata\.plugins\com.ibm.rcp.security.auth\.keystore.jks.J9

Can you please delete or remove the keystore file, restart the client and save the password/auto-login options. Please let me know if this does not resolve your issue.

This seems to have resolved the issue. I'm still waiting to hear back from support to see why this happens and if there's a way to resolve it.

(We also saw this issue at one site where ST 8.0.2 was installed, working ok, and then due to a transition project the domains of the PCs were changed, which caused the error to come up again. By the way, we don't use single sign-on, so not really sure where the error is coming from!)