There has been a lot of conversation here about various errors that were attributable to the Workspace folder being corrupted or other wise compromised.
The simple “delete the workspace folder” suggestion is usually a good one, but at one customer we found there was an issue with getting it to rebuild.
This customer has executables locally, but data lives on a network drive (which is a supported configuration).
However, the directory= line in the users’ notes.ini used a UNC rather than a drive mapping, so the line read something like directory=server01\notesdata\username.
Turns out, Notes was NOT happy rebuilding the \workspace directory with a UNC, but was completely happy to do it if we replaced it with a mapped drive.
So, my instructions to the support desk were as follows:
-
Through TaskManager, make sure that none of the Notes executables are still running: nlnotes.exe, notes.exe, notes2.exe, nsd,exe. If they are, close them
-
Through Windows Explorer, map the user’s “X” drive to their NotesData directory (\server01\notesdata<username>). Check “Reconnect at logon.”
-
Navigate to their NotesData directory and:
a) Delete the Workspace folder
b) Edit Notes.ini. Change the line that says “Directory=\server01\notesdata<username>” to "Directory=X:" Save and close Notes.ini.
-
Close Windows Explorer.
-
Launch Notes.
It should launch without a problem. Total time: <10 minutes.
Not sure why the UNC versus mapped drive should matter at all, but in our case, it made all the difference - and allowed us to avoid spending 90 minutes with a full uninstall and re-install each time …
Just wanted to pass that along …
- Rob