Problem Loading Solutions after creating fields on the target server

As usual, this si a Microsoft thing. We the developers, agree that the name of a field in a table
is its identification. We expect it to be the same in an Entity of a CRM.
Well, Some of Microsoft CRM Developers  disagree. They have an Guid as the key to the attribute from the Attribute table holding the Metadata.
If you create a field at two organizations by the same name, usually because you wanted to do a quick deployment of code and did not want or had pressure to provide a "solution" (your solution) to a problem, you have been hacked.
You can no longer load the solution because the solution loader will identify the original field and the one created manually as different fields and give an error.
You can find from the error the id of the field on the target organization and delete it.