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 How to resolve Tomcat port conflicts when VM I-Net and/or Dimensions I-Net and/or Collage and/or Mover are installed on the same server
General Information Mover 1.0 is pre-configured to use these ports:
CMS-XML MVR: Setting the timezone environment variable for Tomcat
MVR: Setting the timezone environment variable for Tomcat
CMS-XML MVR: How to install or remove the Tomcat service for Serena Mover.
MVR: How to install or remove the Tomcat service for Serena Mover.
CMS-XML MVR 2.3.0.9: Mover to run on Tomcat 6
MVR 2.3.0.9: Mover to run on Tomcat 6
CMS-XML MVR: Deploy activity log is empty and Tocat log says: "Activity: TaskWriter.flushBuffer: Error while flushing log buffer to file"
Deploy activity log is empty and the Tomcat log ( cmlog.txt or mover.log ) shows this error: "Activity: TaskWriter.flushBuffer: Error while flushing log buffer to file"
CMS-XML MVR: After deploy, log gives error; ''Storage.TaskCompletionStatus-SQLState(JZ006),SQLException:JZ006''
When a deploy runs for a long time, typically longer than 4 hours (240 minutes), although all the assets have deployed correctly, the following error messages may appear in the Tomcat log and in the various Mover logs: EXP 2003/06/26 22:16:14 CEST-- Storage: Storage.TaskCompletionStatus-SQLState(JZ006),SQLException:JZ006:
CMS-XML MVR: How to run Mover as a service and be able to deploy to UNC file shares.
The Mover Tomcat service by default runs as the local system account which needs to be changed to run as a named NT account if you want to deploy to a UNC share on the network. The following steps show how to do that.
CMS-XML MVR: Where are the Mover server logs located?
Mover Log File: <Mover Install Directory>\servlet\WEB-INF\mover.log Tomcat Log File: <Mover Install Directory>\ tomcat \logs\stdout.log UNIX:
CMS-XML MVR: How does the VM login source affect Mover?
Mover attempts to login to the VM project as the same user that the Mover tomcat service runs as. That user must exist in the VM project. The username specified in the VM source in mover needs to match the username that the Mover tomcat service runs as and the password specified in VM for that user must match the password entered in the VM source in Mover.
CMS-XML MVR: You cannot access this project because your login account, system, is invalid error in mover activity log
This error usually means the Mover Tomcat services is running as the default (local System account) and the VM project is using HostID as its login source. See below for steps to change the account used to run Mover to run as a different user.
Pages [Next]

Welcome kb sso

My Recent Searches

Search Feedback

Are we answering your questions?

Additional Assistance

  • Submit a Case Online
  • FAQs