Revision history [back]

You're having a typo in database name - constraints msg.
As it's explained in database-loading-and-usage:

For planning just initialize the constraints message as always and set the messages name to the exact name that was used to construct the database.

Likely changing moveit_msgs.msg.OrientationConstraint() name to orientation_constraints would fix it? Let me know if it didn't,

Br,
Artemii

You're having a typo in database name - constraints msg.
As it's explained in database-loading-and-usage:

For planning just initialize the constraints message as always and set the messages name to the exact name that was used to construct the database.

Likely changing moveit_msgs.msg.OrientationConstraint() name to orientation_constraints would fix it? Let me know if it didn't,

Br,
Artemii

You're having a typo in database name - constraints msg.
As it's explained in database-loading-and-usage:

For planning just initialize the constraints message as always and set the messages name to the exact name that was used to construct the database.

Likely changing moveit_msgs.msg.OrientationConstraint() name to orientation_constraints would fix it? Let me know if it didn't,

Br,
Artemiifixed the problem.

[EDIT]
Also check your Moveit! logs if database is actually loaded.