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  
  Results
CMS-XML MVR: Post deploy command gives "Non zero return value returned for source"
MVR: Post deploy command gives "Non zero return value returned for source"
CMS-XML MVR: Pre or Post deployment command returns error "SessionThread.run: Peer bailed out suddenly"
MVR: Pre or Post deployment command returns error "SessionThread.run: Peer bailed out suddenly"
CMS-XML MVR: MCLG: An input/output error occurred while executing command Non zero return value returned for source Local: 255
This error occurs in the deploy log if the path to the script defined for the pre deploy or post deploy commands in the deploy agent aren't valid for the deploy agent to run. It's important that if the script is set to run on the target server via the deploy agent then that script actually lives on the target server and not the Mover or Collage server. The script then needs to be called as the path exists on the computer where the agent is running.
CMS-XML MVR 2.0: When deploy a VM sub-project, Mover automatically creates folders for the VM parent project
A post -transfer command will need to be setup to remove the unwanted parent folder tree. This example is for Mover on Windows, but could be modified for other platforms.
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 2.0+: How to use Mover to pull source code, build the code, and then deploy only the resulting binaries
Second, you will need to setup the post -transfer command in the Mover Source (Deploy | Setup | Source) to run the batch/script you created. Don't forget to pass in any parameters needed by the script. In the example above, the batch file is expecting the name of the deploy Source. In this situation, if the source was called "Move EAR File", and the post-transfer command will look something like this:
CMS-XML Get "The syntax of the command is incorrect." error after upgrade.
echo %Return% to Package ID %id% to %status% 4. Open the package you created and in the #7 field " Post deployment command" put the following. cmd /c C:\MoverCommand\SetPackagestatus.bat 37 MyStatus moverbox admin admin sample 81
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 the Post Deployment Command

Welcome kb sso

My Recent Searches

Search Feedback

Are we answering your questions?

Additional Assistance

  • Submit a Case Online
  • FAQs