we ran into this same situation and it actually had to do with the way our
query was written. I had a cfloop running around an insert statement, inserting
multiple records into a detail table. Since there was the possibility of many
many records being inserted I removed as many line breaks and extra spaces from
the loop as possible so as not to overrun the maximum line limit of a query
being sent to SQL. Turns out I did not have space between the end of one
insert and the beginning of the next so it looked like this:
.....Values(1,1,33,34,0,1)INSERT INTO blah_tbl.....

This did not throw the error everytime I edited an object (in this case
records pertaining to suppliers for a job), but everytime I edited a particular
job it did. I simply added a space between the end of one statement and the
beginning of the next and it fixed the problem. Seems like this error message
can be generated by a number of different problems that can occur, not just
connection limits.