|
Results |
|
Mover cannot deploy from VM File Server based Project Database when VM 8.2+ is installed on the Mover system
Mover cannot deploy from VM File Server based Project Database when VM 8.2+ is installed on the Mover system
|
|
|
Mover 2.x / is it possible to export users project permissions in "batch" mode ?
There is no way to do this easily. This is nothing to do with the admin db, as project permissions are stored inside each project db. There is no guarantee that base permission definitions in the tables would be the same in each project , so there's no guarantee that even if you could export enough from one db it is highly likely that loading those into another db would give completely different results (if it worked at all ).
|
|
|
MVR: VM: How to get Mover to fetch archives based on a promotion group, and force it to travel up the promotion model
The entity path to the VM project . For example, in the PDB above, to move Project1, enter /Project1.
|
|
|
MVR: How to delete a Mover project so it can be re-created
MVR: How to delete a Mover project so it can be re-created
|
|
|
MVR: How to install Mover to another server and move the existing projects.
MVR: How to install Mover to another server and move the existing projects .
|
|
|
MVR: You cannot access this project because your login account, system, is invalid error in mover activity log
MVR: You cannot access this project because your login account, system, is invalid error in mover activity log
|
|
|
MVR 1.0: When deploy a VM sub-project, Mover automatically creates folders for the VM parent project
MVR 1.0: When deploy a VM sub- project , Mover automatically creates folders for the VM parent project
|
|
|
MVR: Error ''This server is not connected to the administration database encoded in the license key. You cannot open any projects unless the admin database host and the host encoded in the license key match exactly.''
MVR: Error ''This server is not connected to the administration database encoded in the license key. You cannot open any projects unless the admin database host and the host encoded in the license key match exactly.''
|
|
|
MVR 2.3.0.1 Fixed issue with moving extra files when multiple maps were in one package. Added ability to copy project, change multiple Dimensions source passwords at one time.
This patch has the following fixes for Mover: You can now copy a Mover project . You can now change passwords for multiple Dimensions sources at one time.
|
|
|
MVR: How to rebuild the admin and project databases
Enter the following command for each project that you will rebuild: Windows: mover.bat sybase-rebuildproject dba sql <database name
|
|
|