I am experiencing a similar SQL error, which I reported here.
I am on RC1 and have not yet tried moving to RC3. I have a client-side log file I could share if it’s useful. I resolved the issue in the short term by disabling client-side logging. I was going to wait for the 1.8 production release and see if the problem went away.
If I can help at all with problem determination on this, please let me know!