This error was triggered by having this configuration setting in your {{exception.EnvironmentName}} environment,
and deploying a content item with a name ending with <value>
:
<settings> <deploy kabum="<value>" /> </settings>
This is used for debugging exceptions & errors and should normally not appear unless you are debugging something. You can disable it by removing the "kabum" attribute from the UmbracoDeploy.settings.config file in ~/config of your site.
The following artifacts might be involved:
The content type of a document or media you are trying to transfer, has changed. This means that the item exists on both sites, but with a different content type. Deploying content type changes is currently not supported by Umbraco Deploy.
If you want to transfer this document, you need to delete the existing document in the destination site and redeploy it from the source site using the new document type.
The following artifacts might be involved:
{{exception.Message}}
This situation must be fixed before deploy can work.
Another content transfer has already been started, by {{exception.UserName}} ({{exception.UserEmail}}). Please try your content transfer again later.
Deploy was unable to open a session to the remote environment due to a problem with chunked transfer encoding.
Chunked transfer encoding is incompatible with Deploy and is usually caused by using an upgraded version of the System.Net.Http assembly in your project.
Please ensure that your assembly redirect bindings for System.Net.Http are set to version 4.0.0.0 in the Web.config of all of your environments.
{{innerException.Message}}
During the deploy process, an invalid path was found in the database. This can be fixed by updating the paths in umbracoNode to be correct. Please contact support for instructions on how to solve this issue.
The following artifacts might be involved:
The following file found contains the merge conflict that needs to be fixed with your Git merge tool of choice:
/data/revisions/{{exception.FileName}}
A common merge conflict happens when yourself or another developer adds a new property to a document type directly on the Cloud site and you forget to pull down the latest changes from the Git repository and decide to work on the same document type locally.
Unsure how to fix a merge conflict, then GitHub has a great guide on this
The {{exception.EnvironmentName || 'source'}} environment has thrown a {{exception.ExceptionType || uiException.ClassName || 'unknown exception'}} with message: {{exception.ExceptionMessage || exception.Message || '(empty)'}} It might have been caused by an inner {{innerException.ExceptionType}} with message: {{innerException.ExceptionMessage || innerException.Message || '(empty)'}}
The following artifacts might be involved:
The technical details may contain more information.
The task was cancelled during execution.
The task timed out.
Time: {{ timestamp }}
Server Time: {{ serverTimestamp }}