Raiser's Edge Error: 512 (Query too complex)

Options
Carrie Miller 8
Carrie Miller 8 ✭
Fifth Anniversary First Reply
in Blackbaud Raiser's Edge NXT®: General Discussion
Hi! I have several saved queries that I use on a monthly basis to generate email lists of our members. Today, I went to use the queries and all of them returned with an error message of "Query too complex. SQL returned more than 1 value.  This is not permitted. Error 512."  I've been using these queries for almost 3 years and now they're not working. So I started from scratch and rebuilt the queries and I'm still receiving the same error message. Has anyone else encountered this error message and if so, how was it resolved? I have a support ticket submitted with Blackbaud, but I was curious if the community members have had a similar experience. 


Thanks!
Tagged:

Comments

  • Isaac Comer
    Isaac Comer ✭
    Tenth Anniversary Facilitator 1 Name Dropper Photogenic
    I haven't ever had that error, but it sure sounds interesting.


    Is it doing it for any/all queries or just these ones you've tried to rebuild?


    A troubleshooting step to try: for one of those queries, try rebuilding it yet again, only try first rebuilding just the criteria (but with no output) one piece at a time.  Each time you add a new piece of criteria, try running it again.  I'm not sure from your description whether these queries have output or whether you use Export for that.  But if you use these for Output, then repeat this process for the output fields trying to add one piece at a time, and running after each time.


    If you are able to narrow down the problem to a single field in criteria or output, it should be easier to figure out what's going on.
  • Dennis Ladnier
    Dennis Ladnier ✭
    Eighth Anniversary Facilitator 1 Name Dropper Photogenic
    I have seen this before however it has been a while - turned out the search criteria did, in fact, return more than one result for a single line item - we had an import which caused some incorrect data on one record.


    My suggestion would be to break down each criteria to determine where the exact issue may be - would think there is a single record that may be causing this.


    Thanks, Dennis
  • Margaret Doran
    Margaret Doran ✭
    Fifth Anniversary First Reply
    I am having the precise same issue. Even the simplest possible queries involving any membership data return the "Query too complex" 512 error. I chatted with support and they told me that we should run the Membership Sequence Utility. We have not done this yet, so I cannot report whether or not it solved the problem.
  • Katherine Manniion
    Katherine Manniion ✭
    Fifth Anniversary Facilitator 1 Name Dropper Photogenic
    Margaret Doran‍ , I just ran the Membership Sequence Utility for one of my clients, and it did the problem.  Also, it only took about 5 minutes to run.  Hopefully it helps you too.


    Katherine

Categories