I am trying to project some data, Chicago census tracts with 801 rows. The data appears to be fine when I download it and add it to the map as a shapefile (table opens fine), but when I try to transform the data in any way (export features, project, import to geodatabase, etc.) I get this error when opening the table: Failed to load data. Failed to retrieve a page of rows. When looking at other posts, I saw that some people had an issue when the primary key was not unique, but that is not an issue for me- the OID looks fine.
I used this data for a recent project with no issue (on an older version of Pro). For this current project, I completely redownloaded the data from the same location but now it is not working.
I'm using version 3.1.2.
Any help would be appreciated!
Solved! Go to Solution.
So I'm wondering if it's the Google Drive connection in the VM. Can you copy the data local the C: drive in the VM and try your workflow again?
So one thing to try is to recalculate the Spatial Grid Index for the shapefile/feature class. To do this, go to the Catalog Pane, Properties, Indexes, Spatial Index and Recalculate. Does the error message persist?
Unfortunately, this did not work! I tried recalculating for both the original file and the projected file, neither changed the ability to open the table.
Hmmmm...okay - a few questions then...
1. Are there any subtypes, domains, query layers, and/or any GDB behaviors on the FC?
2. Is the fGDB local on your C: drive or a shared network drive?
3. Is your geodatabase a file GDB or an enterprise GDB?
This is a sample dataset that I am practicing a couple things on, so it's totally disconnected from any other files in a GDB.
1. I don't think it has any subtypes, domains, or query layers.
2. I'm using a network drive (a personal Google drive) to store the data, as I'm working on a virtual machine that belongs to my university.
3. It's a file GDB.
So I'm wondering if it's the Google Drive connection in the VM. Can you copy the data local the C: drive in the VM and try your workflow again?
Just did it- that worked! The attribute table opens fine after exporting the features from the shapefile that came from the Google drive to the geodatabase for this project. Thanks for your help.
GREAT! I'm glad it worked out for you! If you feel my answer was correct, please mark my answer with the Accept as Solution to close out this thread. Have a great day!