I upgraded all our Notes clients to 8.5.1 last week and have had 3 staff experience Notes freeze on sending emails after the automatic spell check has run. Restarting Windows (or ending all Notes processes) is the only way to get out.
Today I showed a someone how to turn off the automatic spell check and how to run them manually - and it froze. So, as far as I can see it is the actual spell check that is doing this.
I haven’t been able to see any similarity of email content so far but it has happened when using stationery, replies with history, forwarding and when pasting content into the body.
Our servers are on 8.5.1 FP1. FP1 for the client hasn’t fixed this. Our mail design is 7.0.3
Has anyone else had this problem - any ideas how to fix or what to check for?
Hi,Same here. However, we have noticed this not to happen on all emails but only some. The difference being some of those email have had html content. There is also another factor to consider: everything was working fine until we installed Citrx metaframe on the client’s computer. Furthermore, there was a technote on the IBM site to remove ndgts.dll nslsccstr.dll. However, this prevented the client from starting up.
Same thing happening here, and it is always in conjunction with html in the email. Specifically, it has been with web content copied and pasted into an email. I’ve had to instruct the users to “paste special” and paste text only.
Our experience has been that the client freezes with clicking the “Send” button right when the spell check should appear. The spell check interface never does appear, and you have to forcibly terminate the client (ver 8.5.1 with 8.5.1 mail template).
Most recently, user upgraded to 8.5.1 from 7.0.3. Prior to her upgrade, she had no problem. Afterwards, when she sent certain emails, her client froze (if she had spell check enabled). We were able to work around this by having her use the in-line spell check and then, when she sent her email, clicking the Send as is button in the spell check dialog box.
Subject: Notes 8.5.2 FP4 - 50 Plus users with the same issue
Besides a work-around of turning off spell check when sending emails. Does anyone have any other suggestions. We have completed a fresh install of Notes and replaced the template and are still having the issue. Along with this issue the users are also experiencing performance issue when opening the Local Copy of the database.
Subject: had same issue for weeks, just found a fix
We currently have 8.5.2 and had a few users that were experiencing crashing. It would happen when both the inline spell check and spell check before sending options were on. If the inline was on, it would crash as the person was typing a message. If only the spell check before sending was on, it would crash as Notes attempted to check the spelling.
It was a strange issue. It would happen on a few different workstations while on some everything seemed fine. We originally thought it had to do with the users, dictionary files or data files but we could never pinpoint it.
A fix we found today was to change the environment variables within the operating system (Win XP in our case). Go to Control Panel, System, Advanced tab, Environment Variables button. You should see two variables, TEMP and TMP. We changed those to another folder with a much shorter path, such as C:\Temp (if the folder isn’t there it will create itself). Once that’s done, it appears that the user can utilize both spell checks with no issues. The issue must be tied to the length of the variable value.
Our user has a very long name so it was causing that path to be extremely long. If you happen to have the right setting on in the registry, the system should automatically change your value to a short name however ours was turned off which is why we saw inconsistent results among workstations that had it on and those that didn’t.
Thanks, I rolled out the ini fix listed in the link you provided. We’ll see how it goes.
BTW, I don’t think the mail template version will affect this spell checker bug. The bug appears to be in the spell checker itself, which is common to any db, not just email.