Find Answers

Filter Search Results
All Operating Systems:
All Unix (1)
All Windows (2)
All Products:
Mover (5)
All Solution Types:
Error Message (2)
Installation & Customization (1)
Product Tips & Advice (2)
Source:
Defects (1)
Solutions (4)
 
Ask a Question
Example: "Database could not be verified"  
Tips | Start Over | Solutions | Alerts | Patches | Defects  
  Results
CMS-XML Mover shows errors reported in activity log even if pcli command executes successfully.
Mover shows errors reported in activity log even if pcli command executes successfully.
CMS-XML MVR: How does the VM login source affect Mover?
When Mover transfers files from Version Manager, it actually runs a PCLI command to get the files out of VM. One tricky area is how the Version Manager login sources are used by Mover.
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 Mover cannot deploy from VM File Server based Project Database when VM 8.2+ is installed on the Mover system
PCLI and the desktop client GUI installed on the Mover system have no problems using the same path. (Should either of those fail, the problem is related to the File Server configuration.)
CMS-XML MVR: Error ''Login Failed. Merant:login failed.'' for all users other than Admin
On the Mover server, verify that PCLI 8.0 is first in the system PATH. To verify this, go to a DOS prompt and type PCLI. This will give the version number.

Welcome kb sso

My Recent Searches

Search Feedback

Are we answering your questions?

Additional Assistance

  • Submit a Case Online
  • FAQs