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"
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:
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.
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.
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.
