CAUSE
This problem occurs when you use a reserved word, such as "area" or "relationship," in the schema name of a custom entity. Additionally, this problem occurs only when the schema name follows this pattern:
Prefix_ReservedWordAdditionalCharacters
For example, the problem occurs if the schema name is "new_areas" or "new_areasOfInterest."