Spam Filter ISP Support Forum

  New Posts New Posts RSS Feed - table ’tblMsgs’ is full - solved
  FAQ FAQ  Forum Search   Register Register  Login Login

table ’tblMsgs’ is full - solved

 Post Reply Post Reply
Author
aaron View Drop Down
Newbie
Newbie


Joined: 20 September 2006
Status: Offline
Points: 8
Post Options Post Options   Thanks (0) Thanks(0)   Quote aaron Quote  Post ReplyReply Direct Link To This Post Topic: table ’tblMsgs’ is full - solved
    Posted: 07 October 2006 at 9:27am
Hmmm on the settings tab, under quarantine db, the interval in minutes for when expired emails are deleted from the database was set at 0.  I know it wasn't always set to that.  Well anyway, that seems to have fixed it for now.
Back to Top
aaron View Drop Down
Newbie
Newbie


Joined: 20 September 2006
Status: Offline
Points: 8
Post Options Post Options   Thanks (0) Thanks(0)   Quote aaron Quote  Post ReplyReply Direct Link To This Post Posted: 06 October 2006 at 7:04pm
Upon further examination, my tblMsgs had rows with august dates, even though my quarantine should be deleting them after 18 days...  I removed some of those and now it is quarantinely properly again... I wonder what could be causing this table to not have entries automatically removed?
Back to Top
aaron View Drop Down
Newbie
Newbie


Joined: 20 September 2006
Status: Offline
Points: 8
Post Options Post Options   Thanks (0) Thanks(0)   Quote aaron Quote  Post ReplyReply Direct Link To This Post Posted: 06 October 2006 at 6:12pm

I have had SF v3.1.3.597 running on Windows 2000 and a MySQL v4.0.23-nt database running on a different machine (also win2k) for some time without any problems.  Both machines utilize NTFS.

Since last night I have been getting the following error when trying to quarantine messages:
(1924) Error occurred during TAddToQuarantineThread when accessing the quarantine database: [MySQL][ODBC 3.51 Driver][mysqld-4.0.23-nt]The table 'tblMsgs' is full ( 83 84 85 86 86a 86b 86c 87 88 89 90 91)

There is available disk space on the machine hosting the MySQL server and I have tried running REPAIR statements that completed successfully, but have not fixed my problem.  I also did an ALTER TABLE statement which completed successfully, yet did not help either. 

Any ideas on how to solve my problem?



Edited by aaron
Back to Top
 Post Reply Post Reply
  Share Topic   

Forum Jump Forum Permissions View Drop Down



This page was generated in 0.062 seconds.

Copyright © 2002-2016 LogSat Software LLC - Sales: sales@LogSat.com
Contact Us