Find Answers

Filter Search Results
All Operating Systems:
All Products:
All Solution Types:
Source:
 
Ask a Question
Example: "Database could not be verified"  
Tips | Start Over | Solutions | Alerts | Patches | Defects  
Pages [Next]
  Results
CMS-XML MVR: Deploy log gives error "Successfully executing command: "/runvmcm.bat" -v /NASTask1/32.xml. The system cannot find the path specified."
Check the "Client Install Path" field . This path should point to the folder where Version Manger was installed on the Mover server ( for example, C:/Program Files/Serena ). This should be the folder above the VM folder in the install tree.
CMS-XML MVR: Failed to open project tree: in deploy activity log of Mover. Exit value: 1
... Source that is specified in the Mover ... Verify the User id specified in the VM Authentication box is a member of the Version Manager project database and the User id has permissions to log into the project database and to get files. ... In the Project Database field in the Mover VM source verify the path looks like it does when you log into the Version Manager GUI on the Mover box. For example the path that is in parenthesis in the Version Manager application for the project database should match the path specified in the Mover source.
CMS-XML MVR: Exit value 3 path not found when moving files. The system cannot find the path specified
MVR: Exit value 3 path not found when moving files. The system cannot find the path specified
CMS-XML How to change the log level in Mover and where to find the log file ?
When your Mover system is having problems, you may need to change the system default log level in order to get more detailed log information for analysis and troubleshooting.
CMS-XML MVR: Mover 2.3 new feature requirements to integate with Dimensions and Version Manager.
The following document describes the version requirements for Dimensions and Version Manager in order to take advantage of some of the new features available in Mover 2.3
CMS-XML Mover shows errors reported in activity log even if pcli command executes successfully.
Mover will always report an error if the command reported output. In order to get around it with pcli you can try using the -nb parameter like below.
CMS-XML MVR: VM: How to get Mover to fetch archives based on a promotion group, and force it to travel up the promotion model
In Version Manager, there are two ways to get archives by promotion group. VM can get all of the archives that contain the exact promotion group specified (like the command line and PCLI -r option), or it can travel up the promotion model tree (like the command line and PCLI -g option).
CMS-XML MVR: How does the VM login source affect Mover?
Login Dialog Mover will authenticate using the username and password specified on the Mover VM source screen. Host ID
CMS-XML MVR: java.lang.NoClassDefFoundError: pvcs/vmcm/VmCm Exception in thread "main" in mover deploy log.
Look in the installation directory of VM and make sure you see a folder called CM. The error is the result of this folder not existing. You have to install the IDE Tools option during the VM install in order for Mover to work with VM
CMS-XML MVR: Pre or Post deployment command returns error "SessionThread.run: Peer bailed out suddenly"
Edit the deploy server being used Check the context path definition field and ensure the location defined already exists on the server running the Deploy Agent and the correct permissions are allocated based on the user that the Deploy Agent runs as. Another thing to check is to enter the call to the script in the deploy setup as:
Pages [Next]

Welcome kb sso

My Recent Searches

Search Feedback

Are we answering your questions?

Additional Assistance

  • Submit a Case Online
  • FAQs