Data extraction failed during upgrade to Umbraco 7.10.0
Hi all, my upgrade from dev to live is failing because of a collision.
What's the best way to address this?
Error report below:
Exception:
Umbraco.Deploy.Exceptions.ArtifactCollisionException: Some artifacts collide on unique identifiers.
This means that they have different Udis, yet
they refer to the same unique Umbraco object
and therefore cannot be processed.
---------------------------------------------
Collisions for entity type "data-type":
Collisions for unique identifier "Doctor - ShortSummary - Textarea":
UdaFile: ~/data/revision/data-type__95d40b98086e46f484c68a3c539d79db.uda
UdaFile: ~/data/revision/data-type__e6127040db2f4da38a0433294cede015.uda
at Umbraco.Deploy.WorkItems.DiskReadWorkItem.<ExecuteAsyncSub>d__13.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Umbraco.Deploy.WorkItems.DiskReadWorkItem.<ExecuteAsync>d__12.MoveNext()
In the example its with a document type, but you can use the same method for data types.
The main cause of this problem is when a Document Type (or Media Type, Data Type, etc) is manually created in two environments using the same alias.
If you have two or more Cloud environments, we recommend that you never create or make schema changes directly on the Live or Staging environments. You should work with schema only in your Development environment or even better, your local clone of the project.
Data extraction failed during upgrade to Umbraco 7.10.0
Hi all, my upgrade from dev to live is failing because of a collision.
What's the best way to address this?
Error report below:
Hi Colm,
First of all sorry to hear that you have hit into data extraction failed during upgrade to Umbraco 7.10.0
To solve the data extraction failed have a look at this documentation
https://our.umbraco.org/documentation/Umbraco-Cloud/Troubleshooting/Structure-Error/#troubleshooting-structure-deploymentrestore-errors
In the example its with a document type, but you can use the same method for data types.
The main cause of this problem is when a Document Type (or Media Type, Data Type, etc) is manually created in two environments using the same alias.
If you have two or more Cloud environments, we recommend that you never create or make schema changes directly on the Live or Staging environments. You should work with schema only in your Development environment or even better, your local clone of the project.
Hope this helps,
/Dennis
is working on a reply...