One of the guys over at the Warsong Records Forum was posting a rather lengthy response in one particular topic. He called me up because he was getting this error. Unfortunately, as I'm trying to troubleshoot - and after I told him not to post anything (I quote verbatim "I'm not going to do anything until you tell me to." -> one minute of silence later "It's letting me post it in quarters. What am I doing wrong?") - he continued to try and post it in smaller and smaller chunks....
He was able to make smaller posts, but not the whole one in its entirety.
Microsoft JET Database Engine error '80004005'
Not enough space on disk.
/post_info.asp, line 907
(A link to the post_info.asp in question.)
As the error would indicate, this is still on an Access back-end. Its a heavily modified SB2 forum roughly equivalent to 3.4.05 + security updates.
Now, last I checked there shouldn't be a problem posting large chunks of text to a Memo field. His whole post amounts to about 6,673 characters (including spaces, so says Word). I've seen longer in a Snitz forum before.
What really makes this interesting is that the code indicated has nothing to do with inserting the post.
For context lines 903-910: strSql = "SELECT Max(TOPIC_ID) as NewTopicID "
strSql = strSql & " FROM " & strActivePrefix & "TOPICS "
strSql = strSql & " WHERE FORUM_ID = " & Forum_ID
strSql = strSql & " and T_AUTHOR = " & rs("MEMBER_ID")
set rs9 = my_Conn.Execute (strSql)
NewTopicID = rs9("NewTopicId")
rs9.close
set rs9 = nothing
After checking the space I've used on the server vs. what I'm allotted and finding no problems there, I did a Compact and Repair and the problem seems to have gone away.
Any thoughts as to the cause? And if it might return in the future?