We have a laptop running Windows 2000 and Notes 6.02cf2, and the user is getting the message “Notes encountered an error opening a window.” Normally of course we see this after Notes or the laptop crashes, and normally it is resolved by restarting the machine.
In this case, the process nlnotes.exe was still running and could not be killed. The wierd part is that even when the machine was rebooted, the nlnotes.exe process would be there again in the task list, and nothing could kill it. We tried deleting files like ~notes.lck and cache.ndk, but they were locked; and we tried zapNotes, but nothing worked. We searched the registry for entries which might indicate the process should automatically begin on startup. We even tried re-installing Notes, which worked for about a week, but then the ghost process returned. We have now re-imaged the laptop’s hard drive, and are awaiting a third appearence of the ghost process.
Has anyone else seen this? Does anyone have any thoughts?
KillNotes is available in the Sandbox here and works much better and a LOT faster than Zap Notes. I don’t know the exact cause of the lockups, but KillNotes has always worked for me in terminating stray Notes and Domino instances which I couldn’t clear any other way.
I’ve used KillNotes on NT4, Win2K, and XP, and it’s worked like a champ on all those platforms. While it doesn’t hold your hand like KillNotes does, it’s also much faster.
