Failed to retrieve a page of rows. The event class for this subscription is in an invalid partition.

[JamesS1]

Received the following when trying to view the attributes of a view in ArcGIS Pro. Other similar views work fine. No idea what this error means. Any thoughts?

[MVieng]

Something that worked for me is review the data type for columns I wanted to display in my query. Turns out one of my columns was a double and not able to be read in ArcGIS Pro's query layer as a double. Used the function CAST as Varchar(100) and that seemed to do the job. There were multiple columns that needed to be converted from the original data type to Varchar(100), eg - one other column as data type of Big Int which also wasn't coming across. Hopefully this helps others in the future.

[DavidLineberry]

I encountered the same error while working in Pro. The layer triggering the error was as feature class added from a file geodatabase outside of the project geodatabase. I imported it into the project.gdb and now the table loads without error.

I hope this work around helps.

[WAC_GIScoordinator]

Not a full solution, but If the 'Load All' button is present at the bottom of the table, click it. I stopped getting the error. So Far.....

[JohnGuilfoyle]

I tried this workaround. The table closed again.  This time, I deleted the point by selecting it with the rectangle and using the Delete key on the keyboard.  Maybe by deleting from the table it's more stable?

[WAC_GIScoordinator]

Possibly. In my situation, I was deleting rows. After each, delete, table would close. I would save edits, reopen table and start again. Then I noticed not all rows had loaded. Once loaded, table wouldn't close after a row delete. 

I'm offering up what I'm experiencing. May not be applicable in all instances, but hopefully worth a try.

[TravisColeHC]

I was encountering this issue when trying to copy to or create a feature layer in our SDE database. I was using Pro 3.3. I tried our server that had Pro 3.5 installed after several variations of trying to copy or create the layer on my desktop with Pro 3.3 installed and the server didn't experience the issue. I went back and updated the Pro version on my desktop to 3.5 and tried it worked as should with no error now.