Answer
This has been resolved in at least one case by creating a specific Resource Attribute record that the page's metadata generation apparently expects to exist — under Application Base Setup → Enterprise → Resource → Basic Data → Resource Attribute Manager, create a new attribute with Attribute Type "Resource", Attribute ID RESOURCE_ROLE, Data Type Text (length 100), and an LoV View referencing the resource-attribute-value view; after saving that record, the affected pages loaded normally. If you hit this exact error signature on these pages, check for that missing attribute record before assuming a broader metadata corruption issue.