-
Title
RUM (Resource Updating Manager) generates an error "No accounts detected in mapping file" -
Description
The following error is encountered in the log file upon resource updating completion:
\\WORKSTATION Initialization 0 (Error) No accounts detected in mapping file 'C:\WINDOWS\System32\Vmover.ini'.
or
\\WORKSTATION Initialization 0 (Error) No accounts detected in mapping file '<path>\AppData\Local\Temp\<hex name>.tmp'.
When generating a new Vmover.ini file or checking the one on the workstation it only contains the header and no actual objects are present.
-
Cause
This can be a result of the following:1. No accounts were migrated yet within the current ADAM project.2. The filter limits Vmover.ini file population. -
Resolution
For cause 1, the accounts need to be migrated prior to running RUM.
For cause 2, go to RUM console Actions | "Delete Custom Map". Then open Actions | "Specify Custom Map" window and verify there are migrated objects listed there. If there are, agentless processing from the RUM Console may be a workaround for affected workstations. Rebooting workstations and processing them without users logged in may avoid the issue.