Would you know what file controls the “Open” list menu? I’m using Notes 8.0.2 and getting below error messages with any option that I select under the Open list.
Selecting Open > Replication gives the error
"notes:///ClientBookmark?OpenReplication
The parameter is incorrect."
Open > Applications > Workspace gives below error
"notes:///ClientBookmark?OpenWorkspace
The parameter is incorrect."
etc.
It used to work before, but for some reason the issue started to occur after I have modified the replication settings (it shouldn’t, but that’s the last thing I did before the issue came up). It doesn’t seem to be the bookmark.nsf file as I’ve tried to rename it (and it was re-created), but did not solve the issue. Appreciate any help.
One of our staff is experiencing precisely the same issue with 8.0.2. We’ve also tried deleting bookmark.nsf and cache.ndk but to no avail. I’d appreciate it if you keep us updated if you are able to resolve this and I will do the same. I am assuming if you start the client in basic mode as a temporary solution this will go away. I haven’t tried that yet but if you’re not sure how to do this just add -sa to the end of your notes program shortcut.
I had the same issue after having changed the install path of my Lotus Notes client. I have moved all the files and directories from c:\program files\ibm\lotus\notes to c:\program files\lotus\notes. But a lot of keys in my registry were false. So the Notes://… url were not working on my system.
The solution has been to remove the install and make a new install on c:\program files\ibm\lotus\notes. Now the workspace opens without any error.
I have experienced the same problem for some clients. In these cases the end user had installed Windows Desktop Search: Add-in for Lotus Notes. After we removed this sw, it worked again. Windows Desktop Search is only supported in version 5.x through version 7.x
Our one staff member that had this problem had just had IE7 deployed to his machine that morning. Perhaps this is related or perhaps not. However, he rebooted his PC in the early afternoon, and the problem went away.