LogSat Software

Message Topic Search Topic Options Post Reply Create New Topic Printable Version Translate Topic

   I tried to upgrade to 2005 this early morning and started getting these errors on the new database;

09/03/07 05:50:04:859 -- (6568) Error occurred during TAddToQuarantineThread when accessing the quarantine database: Cannot insert the value NULL into column 'MsgID', table 'spamfilter.dbo.tblMsgs'; column does not allow nulls. INSERT fails ( 83 84 85 86 86a 86b 86c 87 88 89 90 91)

I stopped all the SFE's and then used the 2005 wizard to copy the db from MS 2000 where it works fine. I set the compatability mode to 2000 but not sure if its dynamic or not since I changed that option while it was running.

Put everything back for now. Is there a recommened best practice for upgrading SFE to MS SQL 2005?

Thanks!!

Author	Message Topic Search Topic Options Post Reply Create New Topic Printable Version Translate Topic
WebGuyz Members Profile Send Private Message Find Members Posts Add to Buddy List Senior Member Joined: 09 May 2005 Location: United States Status: Offline Points: 348	Post Options Post Reply Quote WebGuyz Report Post Thanks(0) Quote Reply Topic: Best way to move from MS 2000 to 2005 Posted: 03 September 2007 at 7:41am
	I tried to upgrade to 2005 this early morning and started getting these errors on the new database; 09/03/07 05:50:04:859 -- (6568) Error occurred during TAddToQuarantineThread when accessing the quarantine database: Cannot insert the value NULL into column 'MsgID', table 'spamfilter.dbo.tblMsgs'; column does not allow nulls. INSERT fails ( 83 84 85 86 86a 86b 86c 87 88 89 90 91) I stopped all the SFE's and then used the 2005 wizard to copy the db from MS 2000 where it works fine. I set the compatability mode to 2000 but not sure if its dynamic or not since I changed that option while it was running. Put everything back for now. Is there a recommened best practice for upgrading SFE to MS SQL 2005? Thanks!!
	http://www.webguyz.net

LogSat Members Profile Send Private Message Find Members Posts Add to Buddy List Admin Group Joined: 25 January 2005 Location: United States Status: Offline Points: 4104	Post Options Post Reply Quote LogSat Report Post Thanks(0) Quote Reply Posted: 04 September 2007 at 11:43pm
	The compatibility mode should not be an issue, SpamFilter will work in 2005 compatibility mode. Could you instead please verify and ensure that when you migrated the database, on the new database the column "msgid" in the table tblMsgs has still been configured to be an "Identity" column, meaning that SQL Server will assigning the values for that column? If that column was not of the "Identity" type, something has gone wrong in your migration, and you'll want to re-check everything as other problems may have occurred.
	Roberto Franceschetti LogSat Software Spam Filter ISP

WebGuyz Members Profile Send Private Message Find Members Posts Add to Buddy List Senior Member Joined: 09 May 2005 Location: United States Status: Offline Points: 348	Post Options Post Reply Quote WebGuyz Report Post Thanks(0) Quote Reply Posted: 05 September 2007 at 1:25am
	I used the 2005 Copy Wizard to create the database and move the data, but in retrospect I should have done a detach/attach. Will try that this weekend. Thanks!
	http://www.webguyz.net

LogSat Software

Site Navigation[Skip]

Spam Filter ISP Support Forum

Best way to move from MS 2000 to 2005