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!
This post is closed to further activity.
It may be an old question, an answered question, an implemented idea, or a notification-only post.
Please check post dates before relying on any information in a question or answer.
For follow-up or related questions, please post a new question or idea.
If there is a genuine update to be made, please contact us and request that the post is reopened.
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!