First SQL Query as text for the next poor fellow who finds this post :D
SELECT spm.class_desc, spm.permission_name, spm.state_desc, spr.name,
spr.type_desc, spr.is_disabled, ep.name AS EndpointName,
ep.protocol_desc AS EndPointDescription, ep.state_desc AS EndPointState,
ep.type_desc AS EndpointType...
This is a Windows defect.If memory allocation calls are going to fail
due to a lack of resident available memory then Windows should be
setting the memory pressure state so that applications can voluntarily
release memory rather than just crashing.
I am here because I got this error and hoped I would find a clue, but no
dice. In your case it might be explained by nvarchar(max), however I got
it on a postgreSQL boolean column which is bit on SQL server. Makes no
sense. Discard this. I found my solution, naturally outside Microsoft
Tech Communit...
Also in some case this error maybe occurre because of "Common Criteria
Compliance" feature was enabled on the server.To resolve this error you
should:1-Disable "Common Criteria Compliance":sp_configure 'show
advanced options', 1; GO RECONFIGURE; GO sp_configure 'common criteria
compliance enabled', ...
Latest Comments