Thanks for your replys, and sorry for my late response. I have found my problem. My source ArcSDE was originally only an SQL database, and I was enabled geodatabase, when it was full loaded. In SQL, geometry was valid for all objects, but in ArcSDE, it finds geometry errors (the number of points is less than required..) and when FME find this object, finished the table.. (arcpy search cursor finished as well..) So i have to find theese arcmap geometry errors (it's difficult, because in file geodb it was not an error...). After I deleted theese rows in SQL server management studio, FME works well!
Thanks for your replys, and sorry for my late response. I have found my problem. My source ArcSDE was originally only an SQL database, and I was enabled geodatabase, when it was full loaded. In SQL, geometry was valid for all objects, but in ArcSDE, it finds geometry errors (the number of points is less than required..) and when FME find this object, finished the table.. (arcpy search cursor finished as well..) So i have to find theese arcmap geometry errors (it's difficult, because in file geodb it was not an error...). After I deleted theese rows in SQL server management studio, FME works well!
We use 3 different kinds of cookies. You can choose which cookies you want to accept. We need basic cookies to make this site work, therefore these are the minimum you can select. Learn more about our cookies.