This is a tough one. It used to happen all the time to me, and it's a tough spot to be in because there is no help in that error message.
Here is a python script I use frequently along with the sparx geodatabase validation.
'''
Created on Jun 22, 2016
use this when you have an issue importing from Sparx EA
first pass validation
next, see if you can do this.
You might have to use it a lot it you are learning sparx.
things to look for:
domain values have the correct field type for the values
SmallInteger domains have code values less than about 30000
dont be tempted to go changing all the xml around in one session without frequently using this script
@author: kyleg
'''
if __name__ == '__main__':
pass
def ValidatetoFileGDB():
from arcpy import ImportXMLWorkspaceDocument_management, Exists, CreateFileGDB_management, Delete_management
xmlIn = r"C:\temp\ValidateThis.xml"
gdbname = "Validate5"
GDB_In = r"C:/temp/"+gdbname
gdbin = GDB_In+".gdb"
if Exists(gdbin):
Delete_management(gdbin, "Workspace")
CreateFileGDB_management(r"C:/temp", gdbname, "CURRENT")
print("new geodatabase created")
else:
CreateFileGDB_management(r"C:/temp", gdbname, "CURRENT")
ImportXMLWorkspaceDocument_management(gdbin, xmlIn, import_type="SCHEMA_ONLY")
ValidatetoFileGDB()
print("validated")
Thats the end of the script. When facing this situation, you can either retrace your steps back to when you had it working, or you can start a new sparx project and step-copy from the broken project into the new project.
One other tip I can offer is to attempt importing to file geodatabases. I've run into issues where I can NOT successfully import a model to a SQL Server/enterprise geodatabase, but can import to file geodatabase, then copy the file geodatabase to enterprise gdb.