I was trying to enable roaming for myself as well as some other users.
Once I sorted out that you have to use a multi-user install to achieve this, I was still getting the following message in my adminp log:
Title: journal File name: roaming\UserName\C:\Documents and Settings<OS Profile Name>\Local Settings\Application Data\Lotus\Notes\Data\journal.nsf; Error: Invalid directory or device not ready.
well, I contact IBM and there is an internal document they have about this very topic (full copy to follow), but I didn’t like the solution they offered, so I got on the phone with the server and client support teams there, and we ironed it out.
Turns out, that if you picked your “Personal Journal” using the browse button, you aren’t going to get very far.
Basically, I had to enable the checkbox for “show in open database dialog” in the properties of my journal, and pick it from the list, specifically not via the “browse” button.
Once I did that, a downgrade, and re-roam setup and I was almost there.
So, the trick is - how do you get the client to prompt for the journal name again once it has been set. Well, it is just a profile doc in the bookmark.nsf that holds the info, that the roaming upgrade procedure reads, and then uses to populate the notes.ini.
So, in the configuration frameset of the basic welcome pages, there is a hotlink to “set journal database”. Use that link or create button to run the same code and as long as you don’t use the browse button to select it, roaming wil work.
IBM’s solution was to recreate the bookmark.nsf which I wasn’t about to do since I have tons of stuff in there.
Anyway, here is that unpublished (now published) tech note from IBM:
Problem
Administrator is in the process of upgrading a user to roaming user. However, the upgrade process does not complete, and the following error is found in the Administration Request to “Monitor Roaming User’s replica stubs”:
“Title: journal File name: roaming\UserName\C:\Documents and Settings<OS Profile Name>\Local Settings\Application Data\Lotus\Notes\Data\journal.nsf; Error: Invalid directory or device not ready.”
Cause
This error “Invalid directory or device not ready” was caused by the path generated by the roaming upgrade process, to add the user’s journal.nsf database:
“roaming\UserName\C:\Documents and Settings<OS Profile Name>\Local Settings\Application Data\Lotus\Notes\Data\journal.nsf”.
This path is not valid because of the C drive included in the user’s journal.nsf path.
The bookmark.nsf database can be configured to point to the user’s journal.nsf. In this case, the user followed these steps to create a link to the journal.nsf database in Welcome Page (bookmark.nsf):
-
Access the Welcome Page and click on “Personal Journal”.
-
When the dialog box appears, choose “I have a Personal Journal”
-
Click on “Select journal database” button.
-
When the “Choose database” dialog box appears, do not choose the journal from the list. Click on “Browse”.
-
When Window Explorer opens, navigate to the user’s journal.nsf database.
-
Once you have completed this step, you will see the full path to the user’s journal.nsf database starting from the C:\ drive.
Once the user was upgraded to roaming, the “Error: Invalid directory or device not ready” error can be found in Administration Request to monitor the user’s journal.nsf replica stub.
The notes.ini parameter also contained the full path to the user’s journal.nsf: RoamingJournal=C:\Documents and Settings<OS Profile Name>\Local Settings\Application Data\Lotus\Notes\Data\journal.nsf.
Solution:
-
Downgrade the user from roaming to non-roaming.
-
Recreate the bookmark.nsf database.
-
Choose one of the following options:
-
Create a new “pointer” to the journal.nsf database in the Welcome Page (bookmark.nsf).
-
Or, if the name of the Journal database is journal.nsf, allow the roaming user code to automatically locate the file, and include it in the user’s roaming profile.
When adding a journal.nsf in the Welcome Page (bookmark.nsf), the database should be selected in the “Choose Database” dialog box. Using this procedure will not include the full path to the user’s journal.nsf, and will only include the path relative to the data folder. The following path will be found in the Administrative request to add the journal.nsf: “roaming\UserName\journal.nsf”. Also, the RoamingJournal notes.ini parameter will only include the relative path: RoamingJounal=journal.nsf