I have seen this one before. I would recommend to go into Configuration Center on the Web Server and find the Framework configuration and click Upgrade to run MDM. Then perform and IISReset. This seems to be the fix all for issues similar to this.
Just had this one reported to us today.
Haven't given the Framework upgrade followed by an IIS Reset a go yet, will try this on DEV in the morning but in the meantime if anyone reads this and has managed to fix it, how did you go about it?
This is happening on the same query across DEV, UAT and PROD for us so it's potentially something that is transferred via TTL...it wasn't picked up in our UAT though so can't be sure until we've fixed it in DEV and test TTL to UAT.