NM: Unable to migrate Rooms and Resources, File does not exist (4311939)

Issue

When migrating the Rooms and Resources the log states:
! Error: Unable to open mail file roomX.nsf for <Value> on server , roomX.nsf (roomX.nsf) - File does not exist

Solution

This is caused by an incorrect configuration of Notes Migrator, 'Rooms & Resources' tab.
When NM imports an R&R, it creates a brand new database, containing all calendar entries related to a specific room or resource.
Depending on where you placed the database could be the problem.
Open the Notes Migrator Settings document to the 'Rooms & Resources' tab. The issue is probably due to the either the 'Target Server' and/or 'Target Path' fields being blank. This will result in the R&R dbs being created on the Migration Control Center's (MCC) local hard drive (c:\).  The migration workstations cannot access another machine's local drive, since the path is set to c:\, the migration workstation will look in the root of it's own c:\ drive, and not find the file.

Add the Domino server name to the Target Server field
Add the folder name to the Path (Rooms)
Save the Settings document

For 4.x versions
Change to the Advanced Migration view
Select the users to clear their back-end SQL user records
Click 'Clear or Reset user(s) - Remove backend user record" view action

For 3.8.x:
Open SQL Management Studio
Open the NM database
Open the 'CMT_User' table
Delete all the user entries that had the issue.
Close SQL management studio

For 3.7.x and older versions of NM
Open the CMT_Universal.MDB, file (located: C:\Program Files\BinaryTree\CMT Universal\CMT_XMLServer\App_Data ).  MS Access must be installed to view file.
Open the 'CMT_User' table,
Delete all the user entries that had the issue.
Run Compact & Repair
Save and Close the mdb
---------------------------------------------------

Restart IIS on the Migration Control Center (MCC), via iisreset command prompt
Return to the NM Rooms & Resource view, and delete the existing NM entries
Import the the Rooms/Resources to recreate them in the proper location on the Domino server.  
Follow the same steps as before, and migrate the database.