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: SFTP deploy hangs when loggin in SFTP client: Attempting initial login 0 to host: sftp://10.31.12.36:22
MVR: SFTP deploy hangs when loggin in SFTP client : Attempting initial login 0 to host: sftp://10.31.12.36:22
CMS-XML MVR 2.3.0.6: Mover Web Client - improper warning message "Password must be more than 4 characters"
MVR 2.3.0.6: Mover Web Client - improper warning message "Password must be more than 4 characters"
CMS-XML Mover to VM integration deploy does not report errors when accessing files in VM
Client has setup a VM source using a user in VM that is NOT a super user and just has permissions to log in and get copies of files. However, some files have access lists in VM and this user being used can't access it. The solution is to use a VM user that is a 'superuser'.
CMS-XML MVR: Exit value 3 path not found when moving files. The system cannot find the path specified
The client install path setting for the deploy source is most likely wrong. 1. Go to the Deploy | Setup | Source screen and edit the Source you're trying to use 2. Look at the Client Install Path setting and make sure it's set to the following.
CMS-XML MVR: Does Dimensions server need to be installed on the Mover server machine?
Before Mover 2..0.1, the Dimensions server was required to be installed on the same server as Mover. After Mover 2.0.1+, this is not required, you only need to install the Dimensions client on the Mover server. Since there isn't currently a version of Mover for AIX and Dimensions will run on AIX you would have to install Mover on a supported platform along with the corresponding Dimensions client.
CMS-XML MVR: How to install Mover to another server and move the existing projects.
Try to install any clients that Mover uses in its sources to the same path and location as on the previous install including drive letter. For example if you have Version Manager or Dimensions sources try to install the clients to the same path and location. If you don't install Mover or any clients to the same location then look at the steps below for "Post Install Tasks".
CMS-XML MVR: The command indicates that an error occurred during execution. Exit value: 255 How to setup Version Manager source. VM
This example assumes the default install directory for Version Manager and is given just as an example of the default settings to get a basic Version Manager move to work. Client Install Path = One folder above the vm folder in the install directory.
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 2.0.0 - 2.2.1: Getting Mover ready for the new USA 2007 Daylight Saving Time rules.
Mover uses Java technology on the server as well as on the clients . To successfully support the 2007 DST changes, the Java software will need to be upgraded (see http://java.sun.com/developer/technicalArticles/Intl/USDST/ ) on the client machines and the Mover server.
MS-EXCEL Mover_2.3.0_Supported_Platform_Matrix.xls
The "Server OS" worksheet describes the Server operating systems are supported on a per release basis The " Client OS" worksheet describes the Client operating systems are supported on a per release basis The "Database Management Systems" worksheet describes which DBMS versions are supported on which operating systems for each release.
Pages [Next]

Welcome kb sso

My Recent Searches

Search Feedback

Are we answering your questions?

Additional Assistance

  • Submit a Case Online
  • FAQs